Re: including a new gnulib module

[Ben Abbott]

On Jul 31, 2012, at 12:57 PM, Jordi Gutiérrez Hermoso wrote:

> On 31 July 2012 12:48, Ben Abbott <address@hidden> wrote:
>> 
>> On Jul 31, 2012, at 10:10 AM, John W. Eaton wrote:
>> 
>>> On 30-Jul-2012, Ben Abbott wrote:
>>> 
>>> | I did ...
>>> |
>>> |     cd gnulib
>>> |     git pull
>>> |
>>> | ... and a fresh build beginning with autogen finished.
> [snip]
>>> You should not have needed the git pull.  The base64 module was
>>> already in the current version of gnulib that we are using.  Now if
>>> you push a changeset, it will also include an update to gnulib.  Maybe
>>> it is OK to do that, but please don't mix an update to gnulib in with
>>> some other unrelated changeset.
> 
>> After "hg update -C" an "hg diff" is empty.
>> 
>> Is it save to assume I'm ok  now?
> 
> What does "hg summary" say? "hg diff" needs the "--subrepo" flag to
> check up on those too.
> 
> - Jordi G. H.


"hg diff --subrepo" also comes up empty.  See below for "hg summary". Look ok?

$ hg summary
parent: 15057:46b19589b593 tip
 maint: Partition src/ directory with more code in subdirs.
branch: default
commit: 7623 unknown (clean)
update: (current)

Ben