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, 13:58 UTC
Message-ID
<alpine.DEB.1.00.0805161457250.30431@racer>
In-Reply-To
<32541b130805160643y3bfe609et22b2d00627f98c04@mail.gmail.com>
Hi,
On Fri, 16 May 2008, Avery Pennarun wrote:
Show 7 quoted lines
> So I think it would be very bad if the supermodule automatically
> updated to the latest version of the submodule whenever you commit in
> the submodule.  *However*, the other way around might be fine: if you
> commit in the supermodule, maybe it should commit in the submodule at
> the same time and link to that specific commit.  I'm pretty sure that
> idea doesn't have any *fundamental* flaws, it's just got a lot of
> really tricky details that need to be worked out.

Just the fundamental flaw that you might _not_ want to commit that, just as you can have a dirty Makefile _forever_.

Ciao, Dscho

Previous: Avery PennarunNext: Avery Pennarun
Message 4 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.