From: Raimund Bauer <ray007@gmx•net>
To: Junio C Hamano <junkio@cox•net>
Cc: Johan Herland <johan@herland•net>,
git@vger•kernel.org, Martin Waitz <tali@admingilde•org>
Subject: Re: RFC: submodule terminology
Date: Mon, 21 May 2007 08:44:46 +0200 [thread overview]
Message-ID: <1179729886.6187.15.camel@localhost> (raw)
In-Reply-To: <7v3b1rje45.fsf@assigned-by-dhcp.cox.net>
On Sun, 2007-05-20 at 15:59 -0700, Junio C Hamano wrote:
> I was wondering if we can get away by just calling them
> "projects", "projects containd in the superproject", etc., as I
> tend to agree with Linus, who used the term "superproject
> support" in his talk, that this is not really about creating
> "subproject" which are somehow different from ordinary projects,
> but more about supporting superprojects that can contain/point
> at other projects, which we did not have before 1.5.2 happened.
The "super" or "sub" only comes from where in a hierarchy it is used.
Somewhere in the middle of the hierarchy it would be both?
I'd have said a repository can have many "modules" or "projects", and
each of those can have several branches. A module can hold other
modules, but from its POV also be part of a super-module (or
superproject), we just have to take care to not build loops.
Is my view of the world correct so far?
--
best regards
Ray
next prev parent reply other threads:[~2007-05-21 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 21:44 RFC: submodule terminology Martin Waitz
2007-05-20 22:06 ` Johan Herland
2007-05-20 22:59 ` Junio C Hamano
2007-05-20 23:10 ` Johan Herland
2007-05-21 6:44 ` Raimund Bauer [this message]
2007-05-21 6:52 ` Shawn O. Pearce
2007-05-20 23:03 ` Martin Waitz
2007-05-20 23:16 ` Johan Herland
2007-05-20 23:39 ` Martin Waitz
2007-05-21 0:32 ` Eric Lesh
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=1179729886.6187.15.camel@localhost \
--to=ray007@gmx$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=johan@herland$(echo .)net \
--cc=junkio@cox$(echo .)net \
--cc=tali@admingilde$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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