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 16, 2011, 18:20 UTC
Message-ID
<20110416182053.GA11017@elie>
In-Reply-To
<4DA9C7A7.4010503@sohovfx.com>
Hi Andrew,
Andrew Wong wrote:
Show 6 quoted lines
> It seems like submodule isn't meant for this, but many people seems
> to use submodule to link many smaller repos together. With this
> setup, I imagine whenever someone pushed a small repo, they're
> /supposed/ to push the big repo as well. This way, if I simply
> update the big repo and do a "git status", git will tell me that
> which of the smaller repos are out of date.

Yep, if you want to keep track of the state of a bunch of repos over time, submodules are not so bad[*]. In practice, often one instead wants to keep a bunch of repos up-to-date, and all this meta-history tracking is overkill.

I'd suggest using the mr tool. Some projects (e.g., the debian-installer project) are using it to help people keep all their repos up to date.

http://kitenet.net/~joey/code/mr/

Hope that helps, Jonathan

Previous: Andrew WongNext: Jonathan Nieder
Message 2 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.