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

Re: How to manage multiple repos using submodules?

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Apr 17, 2011, 06:48 UTC
Message-ID
<20110417064818.GA25344@elie>
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

Previous: Jonathan NiederNext: Andrew Wong
Message 3 of 5 in “How to manage multiple repos using submodules?”
  1. Andrew WongApr 16, 2011
  2. Jonathan NiederApr 16, 2011
  3. Jonathan NiederApr 17, 2011
  4. Andrew WongApr 17, 2011
  5. Phil HordApr 19, 2011

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.