From: Jonathan Nieder <jrnieder@gmail.com>
To: Andrew Wong <andrew.w@sohovfx.com>
Cc: git@vger.kernel.org, Jens Lehmann <Jens.Lehmann@web.de>
Subject: Re: How to manage multiple repos using submodules?
Date: Sun, 17 Apr 2011 01:48:19 -0500 [thread overview]
Message-ID: <20110417064818.GA25344@elie> (raw)
In-Reply-To: <20110416182053.GA11017@elie>
Hi,
Jonathan Nieder wrote:
> Yep, if you want to keep track of the state of a bunch of repos over
> time, submodules are not so bad[*].
A kind person pointed out that I left out a footnote. I think all I
had been planning to say is that, roughly speaking, submodules are
about[1] saying that a specific commit is known to work well with the
rest of the code. A supermodule like the one discussed in [2] is only
likely to be useful if you are interested in what historical
combinations of repositories were published and meant to work well
together.
Ciao,
Jonathan
[1] e.g., http://thread.gmane.org/gmane.comp.version-control.git/27803/focus=27830
[2] http://lists.x.org/archives/xorg-devel/2009-September/001966.html
next prev parent reply other threads:[~2011-04-17 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 16:45 How to manage multiple repos using submodules? Andrew Wong
2011-04-16 18:20 ` Jonathan Nieder
2011-04-17 6:48 ` Jonathan Nieder [this message]
2011-04-17 18:42 ` Andrew Wong
2011-04-19 13:18 ` Phil Hord
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=20110417064818.GA25344@elie \
--to=jrnieder@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=andrew.w@sohovfx.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).