Re: Please review wip/bzr* and wip/qbzr

In bzr, patch-ab was renamed.  This isn't ok, because it makes more
churn.  When I put it back to the original name, then even the distinfo
line was unchanged.

I had a quick look via:

  diff -u -N --exclude CVS /usr/pkgsrc/devel/bzr /usr/pkgsrc/wip/bzr

etc. and they look basically ok.

We don't have a convention, but it would be nice to have a file
COMMIT_MSG in each package that can be used when commiting to pkgsrc,
summarizing the changes since the pkgsrc version.  (For use with "cvs -F
COMMIT_MSG commit", so the person doing the commit doesn't have to write
the message.)

It is unclear to me whether these can be updated individually, or only
as a group.   Is it ok to commit them in the order you listed, with it
being the case that pausing at any time doesn't leave anything broken?

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d

_______________________________________________
pkgsrc-wip-review mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-review

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (NetBSD)

iEYEARECAAYFAk7Ls/UACgkQ+vesoDJhHiXeSACgsO5IaJ7aycsP0Cr+AqDwtLl1
/PgAniIQVpuhpxN18NaujErhJsTbzc7Q
=L2UZ
-----END PGP SIGNATURE-----