[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: branch-2-0

From: Gary V . Vaughan
Subject: Re: branch-2-0
Date: Mon, 4 Oct 2004 00:28:11 +0100

Hash: SHA1

Hi Bob!

On 4 Oct 2004, at 00:00, Bob Friesenhahn wrote:

On Sun, 3 Oct 2004, Gary V. Vaughan wrote:
If you have time and inclination, I highly recommend publishing an arch archive of your own...

Alas, I have very little available time. That is one of the reasons why I am such a terrible libtool maintainer. :-(

Not in the least, you've caught a zillion little things that would've slipped through the cracks were you not here! :-)

I wanted to help (myself mainly) avoid the temptation to commit `cleanups' to the branch that 2.0 will be released from. Having a branch for 2.0 now means I can commit cleanups to HEAD (rather than waiting and then forgetting them) and put only fixes on the release branch.

Hmmm ... the true reason is revealed! :-)

If it is so easy for you to do, then please merge across the updates I committed today.

No probs.  Done.

In the hope of persuading you that the short term pain of learning a new SCM tool is worth the gain in productivity when you have climbed the learning curve, this is how I did the merge (and synch with CVS on HEAD and branch-2-0, along with commit and patch notification posts to relevant lists):

  $ cd ~/devel/libtool--devo--1.0
  $ tla-cvs-sync
  CVS revision 1.1668 committed as patch-232
  $ cd ~/devel/libtool--release--2.0
  $ tla replay libtool--devo--1.0--patch-232
  $ tlaapply -vgcr -p 's,XSED,Xsed, and support VERBOSE=debug'
  $ cd -
  $ tla-cvs-sync
  CVS revision 1.1669 committed as patch-233
  $ cd -
  $ tla replay libtool--devo--1.0--patch-233
  $ tlaapply -vgcr -p 'update notes regarding VERBOSE testing'
  $ cd -
  $ tla-cvs-sync
  1.1669 is latest revision

Took me longer to write this reply than it did to do the merges :-)

Arch also knows that these changesets are now in both trees, so when I
star-merge branch-2-0 back onto HEAD, it will automatically skip them.

Provided that libtool starts working for MinGW and Solaris (MinGW is much improved now), I would like to start using development libtool for the development version of GraphicsMagick in order to gain more real-world experience with it and flush out any remaining bugs which keep me from using it for production use.

Excellent. Thanks. It should be easier now we have a tarball at to download and test too.

- --
Gary V. Vaughan      ())_.  address@hidden,}
Research Scientist   ( '/
GNU Hacker           / )=
Technical Author   `(_~)_

Version: GnuPG v1.2.4 (Darwin)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]