From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Jeff Johnston <jjohnstn@redhat.com>,
overseers@sourceware.org,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: sourceware and git
Date: Wed, 30 Jul 2014 15:18:00 -0000 [thread overview]
Message-ID: <20140730151807.GA3806@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20140730074758.GA9483@calimero.vinschen.de>
On Wed, Jul 30, 2014 at 09:47:58AM +0200, Corinna Vinschen wrote:
>On Jul 29 21:13, Christopher Faylor wrote:
>> And, I think it would be nice to use the power of git to
>> allow a logical separation between the two projects.
>
>I don't really care for the toplevel stuff, but what I would like to see
>is that both projects, newlib as well as Cygwin, can be checked out,
>updated, branched, tagged, etc, in a single operation, just as before.
>So
>
> 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?
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.
cgf
next prev parent reply other threads:[~2014-07-30 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <239280260.18333755.1406652387203.JavaMail.zimbra@redhat.com>
2014-07-29 16:57 ` Jeff Johnston
2014-07-29 18:14 ` Joseph S. Myers
2014-07-30 1:13 ` Christopher Faylor
2014-07-30 7:48 ` Corinna Vinschen
2014-07-30 15:18 ` Christopher Faylor [this message]
2014-07-30 15:39 ` Corinna Vinschen
2014-07-30 17:06 ` Joseph S. Myers
2014-07-30 17:27 ` Hans-Peter Nilsson
2014-07-30 17:02 ` Joseph S. Myers
2014-07-30 18:45 ` Christopher Faylor
2014-07-30 20:57 ` Joseph S. Myers
2014-07-30 21:33 ` Christopher Faylor
2014-07-30 21:47 ` Joseph S. Myers
2014-07-30 23:41 ` Yaakov Selkowitz
2014-07-31 2:22 ` Christopher Faylor
2014-08-01 11:05 ` Corinna Vinschen
2014-08-01 22:54 ` Frank Ch. Eigler
2014-08-02 0:12 ` Yaakov Selkowitz
2014-07-29 18:28 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140730151807.GA3806@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=jjohnstn@redhat.com \
--cc=joseph@codesourcery.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).