From: A Large Angry SCM <gitzilla@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Notes on Using Git with Subprojects
Date: Tue, 26 Sep 2006 15:45:51 -0700 [thread overview]
Message-ID: <4519AD9F.7020303@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0609270009400.25371@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Tue, 26 Sep 2006, A Large Angry SCM wrote:
>
>> How the state (subproject list, branch names, etc.) is recorded in a
>> parent project is only important to the parent project. The parent
>> project must also know how to interact with with each of its
>> subprojects.
>
> Granted, if you mix VCSes, this is most pragmatic.
>
> But it is also wrong: The whole point in bundling the subprojects together
> is (IMHO) to get the benefits of a VCS for the root project, i.e. for the
> combined states of the subprojects. After all, you want to say "I know
> that this collection of projects at these states compiled and worked
> fine."
>
> And if you let a build system handle the stitching of the subprojects, you
> completely lose these benefits.
Bundling and subproject support are two different things. Bundling is
for convenience. Subprojects are usually the result of a dependency on a
project managed or controlled by some other entity or on some part of
the larger project with radically different development requirements.
Recording which version of a subproject to use is important and my note
failed to discuss it. That I'll remedy over the next several days.
next prev parent reply other threads:[~2006-09-26 22:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 17:40 Notes on Using Git with Subprojects A Large Angry SCM
2006-09-26 20:25 ` Johannes Schindelin
2006-09-26 22:01 ` A Large Angry SCM
2006-09-26 22:13 ` Johannes Schindelin
2006-09-26 22:45 ` A Large Angry SCM [this message]
2006-09-26 21:23 ` Daniel Barkalow
2006-09-26 21:30 ` Shawn Pearce
2006-09-26 22:33 ` A Large Angry SCM
2006-09-27 8:06 ` Martin Waitz
2006-09-27 9:55 ` Johannes Schindelin
2006-09-27 11:38 ` Martin Waitz
2006-09-27 12:01 ` Johannes Schindelin
2006-09-27 12:44 ` Sven Verdoolaege
2006-09-27 21:05 ` Junio C Hamano
2006-09-28 15:02 ` Michael S. Tsirkin
2006-09-28 20:16 ` Jeff King
2006-09-27 12:46 ` Martin Waitz
2006-09-27 13:13 ` Johannes Schindelin
2006-09-27 17:13 ` A Large Angry SCM
2006-09-27 23:14 ` Johannes Schindelin
2006-09-27 23:36 ` Shawn Pearce
2006-09-27 23:55 ` Rogan Dawes
2006-09-28 0:36 ` Shawn Pearce
2006-09-28 5:02 ` A Large Angry SCM
2006-09-28 4:48 ` A Large Angry SCM
2006-09-27 16:58 ` A Large Angry SCM
2006-09-27 17:33 ` Jeff King
2006-09-28 3:47 ` A Large Angry SCM
2006-09-28 3:52 ` Jeff King
2006-09-28 3:58 ` Shawn Pearce
2006-09-28 4:00 ` Jeff King
2006-09-28 4:09 ` Shawn Pearce
2006-09-28 3:52 ` Shawn Pearce
2006-09-28 15:39 ` Johannes Schindelin
2006-09-28 7:37 ` Martin Waitz
2006-09-28 20:30 ` A Large Angry SCM
2006-09-29 7:04 ` Martin Waitz
2006-09-26 22:07 ` A Large Angry SCM
2006-10-01 5:19 ` A Large Angry SCM
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=4519AD9F.7020303@gmail.com \
--to=gitzilla@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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).