From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: <overseers@sourceware.org>
Subject: Re: sourceware and git
Date: Wed, 30 Jul 2014 20:57:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1407302052140.3490@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20140730184538.GA1043@ednor.casa.cgf.cx>
On Wed, 30 Jul 2014, Christopher Faylor wrote:
> On Wed, Jul 30, 2014 at 05:02:47PM +0000, Joseph S. Myers wrote:
> >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;
>
> Your dubiousity doesn't have any bearing if it isn't backed up by facts.
It's backed up by the list of requirements I gave for git to work smoothly
in the presence of submodules as if there were a single repository, none
of which (according to the git-submodule manpage) git submodules meet.
We have many years' experience of the src repository being problematic
because of the use of a special feature of CVS (modules files for partial
checkouts of a directory in the repository) that doesn't work well with
other features of CVS (cvs update -d; the interaction of modules file
changes with tagging and branching). That also provides a basis for
caution about such features in other version control systems, and for
preferring an ordinary git repository whose clones work with ordinary git
commands just like those commands work with clones of any other random git
repository.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-07-30 20:57 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
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 [this message]
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=Pine.LNX.4.64.1407302052140.3490@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=jjohnstn@redhat.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).