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

Submodules implementation

From
CBChristoph Bartoschek <bartoschek@gmx.de>
Date
Feb 23, 2010, 23:50 UTC
Message-ID
<k76e57-g67.ln1@burns.bruehl.pontohonk.de>
Hi,

what is the main reason that submodules are their own repositories linked into the enclosing one and not just additional pointers in the main repository?

My impression is that submodules as pointers to existing tree objects would make a design more easier to understand and more user friendly. Especially I see no need for most of the submodule commands. Maybe "git submodule add" but the other commands are already covered by existing ones.

Or is there a tool that uses such additional pointers for submodule management?

Thanks Christoph

Next: Avery Pennarun
Message 1 of 4 in “Submodules implementation”
  1. Christoph BartoschekFeb 23, 2010
  2. Avery PennarunFeb 23, 2010
  3. Christoph BartoschekFeb 24, 2010
  4. Junio C HamanoFeb 24, 2010

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.