Re: sourceware and git

["Joseph S. Myers" <joseph@codesourcery.com>]

On Tue, 29 Jul 2014, Christopher Faylor wrote:

> I've been trying to convince Jeff and Corinna that the top-level stuff
> isn't really needed for newlib.

It's needed as the way that newlib gets configured for the right set of 
multilibs, to be installed in the right directories!

> Since cygwin needs newlib, I think that this means that cygwin could
> import newlib as a submodule if it needed it.  The other proposal is to
> keep newlib and cygwin in one git project.  That more or less keeps the
> status quo for newlib and cygwin but it means that people who use newlib
> without cygwin will have extra Windows-specific code that they don't
> care about.  And, I think it would be nice to use the power of git to
> allow a logical separation between the two projects.

I think having them in one git project (that includes libgloss and the 
relevant toplevel) would be fine.  I'm generally dubious of things such as 
submodules; I think basic requirements include: checking out with git:// 
gets a git:// checkout of everything; checking out with git+ssh:// gets a 
git+ssh:// checkout of everything; pulling automatically pulls changes to 
everything; branching, tagging etc. (and pushing those branches or tags) 
automatically branches, tags etc. everything.

-- 
Joseph S. Myers
joseph@codesourcery.com