top-level configure.ac changes lost in sync

H.J. Lu hjl.tools@gmail.com
Thu Nov 15 21:07:00 GMT 2012


On Thu, Nov 15, 2012 at 1:02 PM, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> On Wed, 2012-11-14 21:05:04 -0500, DJ Delorie <dj@redhat.com> wrote:
>>
>> Checkin rules are documented in the toplevel MAINTAINERS file:
>>
>>     Makefile.*; configure; configure.ac; src-release
>>       Any global maintainer can approve changes to these
> [...]
>> > The patch below restores the wrongly-reverted change.  How do I get this
>> > in so it won't be clobbered again?
>>
>> What you did is correct, but patches should be committed to both src
>> and gcc (preferably by the author ;) to keep them in sync.  There is
>> no automatic process to sync them; any such attempt should review all
>> patches to *both* repos and apply missing patches *as* patches.
>
> I'm auto-building toolchains for some 30 targets on a daily basis, it
> wouldn't be any pain for me to hack a script to check the top-level
> files for differences. I already have commit rights to gcc and src,
> but not IMHO for gdb.
>
> So... I'll prepare a script to spot changes to the toplevel files and
> and merge it to the other repos.  Shall I only *notify* the other
> repo's mailing lists, or wait for separate ACK for each of them?

I think approval from one project is good for toplevel changes.
You should send an email to the other project to inform the
change.

> What about the generated files?
>

They should be kept in sync.

-- 
H.J.



More information about the Binutils mailing list