top-level configure.ac changes lost in sync

[Mike Frysinger]

On Thursday 15 November 2012 16:02:49 Jan-Benedict Glaw 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.

src & gdb are the same repo
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://sourceware.org/pipermail/binutils/attachments/20121117/87601780/attachment.sig>