git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RFC: submodule terminology

From
RBRaimund Bauer <ray007@gmx.net>
Date
May 21, 2007, 06:44 UTC
Message-ID
<1179729886.6187.15.camel@localhost>
In-Reply-To
<7v3b1rje45.fsf@assigned-by-dhcp.cox.net>
On Sun, 2007-05-20 at 15:59 -0700, Junio C Hamano wrote:
Show 7 quoted lines
> 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
Previous: Johan HerlandNext: Shawn O. Pearce
Message 5 of 10 in “RFC: submodule terminology”
  1. Martin WaitzMay 20, 2007
  2. Johan HerlandMay 20, 2007
  3. Junio C HamanoMay 20, 2007
  4. Johan HerlandMay 20, 2007
  5. Raimund BauerMay 21, 2007
  6. Shawn O. PearceMay 21, 2007
  7. Martin WaitzMay 20, 2007
  8. Johan HerlandMay 20, 2007
  9. Martin WaitzMay 20, 2007
  10. Eric LeshMay 21, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.