Re: sourceware and git

[Hans-Peter Nilsson <hp@bitrange.com>]

On Wed, 30 Jul 2014, Christopher Faylor wrote:
> On Wed, Jul 30, 2014 at 09:47:58AM +0200, Corinna Vinschen wrote:
> >  git clone http://sourceware.org/cygwin.git
> >
> >should check out cygwin + newlib (as submodule?) and
> >
> >  git clone http://sourceware.org/newlib.git
> >
> >should check out newlib + libgloss (as submodule?).
> >
> >Is that possible with git?

(A subsequent command is needed with git submodules, which I see
have no supporters here, so I'll refrain from saying "git
submodule update --init --recursive" ...oops. :)

> If git can't automatically check out newlib as a submodule then we could
> just include a 'tag' script somewhere in cygwin.  You're going to have
> to learn a new command to tag things anyway so if it's "git tag" or
> "./tag-cygwin-newlib" it shouldn't be that big a deal.

It seems natural to amend the top-level src-release makefile
with targets newlib.tar.bz2 and cygwin.tar.bz2, similar to sim,
binutils and gdb that were at one time CVS modules (with the
obvious caveat of no-longer-shared toplevel files).

You'd have the git-checkout containing everything, but at least
you can create official-release-type and snapshot tar-balls with
the expected contents.

brgds, H-P