-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Gary V. Vaughan on 2/25/2007 2:22 PM: > > My problem is that I don't know how to pick a snapshot date that > will include recent fixes to modules M4 cares about, but not > destabilizing changes that occured in the same timeframe. > > I'm thinking about making an effectively local branch of gnulib as > M4 releases approach so that I can manually apply just the gnulib > patches that matter to M4 without accidentally picking up one > of the module reorganizations patches that occur in gnulib > relatively often.
Eventually, when the move to git is complete, doing this will be easy - you just make a branch in your local git copy of gnulib, and base your m4 release off of that branch. But so far, it has not been too much of an issue - I have been actively tracking gnulib often enough that when I have made releases (1.4.5 through 1.4.8b), the gnulib snapshot on the date of my release has been stable enough for the purpose of a release. > Is there perhaps some way to cleverly tag the CVS tree of gnulib to > avoid this problem? In CVS, not really, In git, yes. Which is why I am still anxious for the git transition to complete. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF4hiW84KuGfSFAYARAmZXAJ9uszbIGsKk1DBo2ihd0i8l+ocpYACgnF8W 8Ft6x7eUqZDq9Xh/B33bLaA= =j6Ym -----END PGP SIGNATURE-----
