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

Re: Why do git submodules require manual checkouts and commits?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 16, 2008, 10:17 UTC
Message-ID
<alpine.DEB.1.00.0805161055540.30431@racer>
In-Reply-To
<2729632a0805152116o3c998324xb401674207dd2e1e@mail.gmail.com>
Hi,
On Thu, 15 May 2008, skillzero@gmail.com wrote:
> Why do git submodules require manually committing the submodule itself
> to each super repository after something in the submodule repository
> changes?
Submodules are special.

You cannot recreate the exact state from a commit in the superproject, for one, and often not even from the commit itself, since the submodule can contain more than just the tracked files.

Also, no submodule _has_ to be checked out. If you are working inside a superproject, chances are that you are uninterested in most of the submodules.

So no, there is nothing to change here, please move along.

Ciao, Dscho

Previous: skillzero@gmail.comNext: Avery Pennarun
Message 2 of 9 in “Why do git submodules require manual checkouts and commits?”
  1. skillzero@gmail.comMay 16, 2008
  2. Johannes SchindelinMay 16, 2008
  3. Avery PennarunMay 16, 2008
  4. Johannes SchindelinMay 16, 2008
  5. Avery PennarunMay 16, 2008
  6. Johannes SchindelinMay 16, 2008
  7. Avery PennarunMay 16, 2008
  8. Lars HjemliMay 16, 2008
  9. skillzero@gmail.comMay 19, 2008

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.