Re: another gnulib update

[Jim Meyering]

Eric Blake <address@hidden> 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.

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.