m4-patches
[Top][All Lists]
Advanced

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

Re: make gnulib a git submodule


From: Gary V. Vaughan
Subject: Re: make gnulib a git submodule
Date: Fri, 20 Mar 2009 08:41:21 +1300

Hi Eric,

2009/3/20 Eric Blake <address@hidden>:
> According to Eric Blake on 3/19/2009 6:50 AM:
>> According to Eric Blake on 3/16/2009 11:13 AM:
>>> After recent success in bison and coreutils in using gnulib as a
>>> submodule, I've decided to do the same for m4.  This patch is currently
>>> available at
>>> $ git fetch git://repo.or.cz/m4/ericb.git branch-1.4
>
> Still true (although I frequently rewind my personal repo, so you may need
> 'git reset --hard FETCH_HEAD' instead of 'git merge' to avoid dealing with
> conflict resolution as I tweak and rebase the series).

Branch-1.4?  That's so 1980's ;)

>>> but if no one has any complaints, I will go ahead and merge it into all
>>> three branches next week.  It has the advantage that future m4 releases
>>> now record exactly which gnulib version was in effect at the time.
>>
>> What do you think of this follow-on patch?  Since we guarantee gnulib as a
>> git submodule, we can use git symlinks to point into that submodule, and
>> automatically pick up the latest build-aux scripts by merely updating the
>> submodule, rather than having to rerun bootstrap!
>
> For the record, I did verify that with this patch, 'make distcheck' still
> passes, and that the resulting tarball had files, and not symlinks, so the
> end client should see no difference in behavior.  It only affects
> development from a git checkout.

Personally, I think this is totally awesome!  I'm delighted that we can finally
begin to mitigate some of the gnulib non-release craziness. :D

Cheers,
    Gary
-- 
Email me:          address@hidden                        (\(\
Read my blog:      http://blog.azazil.net              ( o.O)
And my other blog: http://www.machaxor.net              (uu )o
...and my book:    http://sources.redhat.com/autobook  ("("_)




reply via email to

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