Re: [patch 1/28] top-level: Use automake-1.11.6

[Joseph Myers <joseph@codesourcery.com>]

On Tue, 12 May 2015, Michael Haubenwallner wrote:

> On 05/11/2015 07:55 PM, Joseph Myers wrote:
> > On Sat, 9 May 2015, Bernd Edlinger wrote:
> > 
> >> But maybe you would like it better if we update, for instance, to:
> >> automake-1.14  _and_  autoconf-2.69 ?
> > 
> > Updating to current automake and autoconf release versions (but still 
> > using git versions of the toplevel scripts, not those from particular 
> > releases) is a good thing 
> 
> Agreed - but that seems to require additional source changes, which is
> beyond my knowledge (and need). Besides that: wouldn't such commits be
> of better quality when starting from identical old (1.11.6) versions?

I don't see any real difference.  Updating to 1.11.6 is useful in the 
absence of anyone working on the more major update, but if someone's 
working on the more major update, whether there's an update first to 
1.11.6 shouldn't matter much.

> > - remembering that toplevel is shared with the 
> > binutils-gdb and newlib-cygwin repositories
> 
> Just curious: I do remember this from the old CVS days, but given that
> gcc has its own Subversion repository, how is that organized now?

When someone changes a shared directory, they should apply the changes to 
all three repositories.  Simply copying a shared file from one place to 
another isn't safe without checking that all changes in the destination 
repository since the files were last in sync were properly applied to the 
source repository, so that copying the file doesn't lose changes; no one 
repository is the master.

-- 
Joseph S. Myers
joseph@codesourcery.com