Re: another gnulib update

Hi Jim, Eric,

On 25 Feb 2007, at 15:45, Jim Meyering wrote:
> Eric Blake <[email protected]> wrote:
> ...
>> 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.

Yes that would certainly make life considerably easier for us.  I  
suppose
that what I'm really pressing for is for gnulib itself to do that  
work once,
rather than have all client projects make transient gnulib forks for  
each of
their own releases.

Right now, all of the major gnulib clients happen to track commits  
closely
enough that it hasn't caused a problem for them yet, but I think it's  
only
a matter of time until someone bootstraps a client release tree just  
after
a gnulib module they use has had untested code committed.

> As you probably know, the cvs gnulib repository is now being mirrored
> to the git one pretty regularly (sync'd every 30 minutes).
> Maybe that is enough for you?
>
> Browse it:
>
>     http://git.sv.gnu.org/gitweb/?p=gnulib.git
>
> Check out a copy (my local copy is 17MB):
>
>     git clone git://git.sv.gnu.org/gnulib
>
> As for converting gnulib development to git, I still have some work  
> to do:
>
> I have to adapt the git hook I'm currently using for coreutils
> (to sync the read-only CVS repository from the master git repo
> with each "push") so that it works even for merges.

Oh, I didn't realise savannah was hosting git repositories now.  I'll  
spend
some time familiarising myself with git then.

Eric, how about moving M4 into git after your next release?  I've  
wanted to
get away from CVS for several years (to the point of mirroring CVS  
into my
own Arch and SVK repositories)...

Cheers,
	Gary
-- 
   ())_.              Email me: [email protected]
   ( '/           Read my blog: http://blog.azazil.net
   / )=         ...and my book: http://sources.redhat.com/autobook
`(_~)_ Join my AGLOCO Network: http://www.agloco.com/r/BBBS7912