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

RFC: have a config option for running submodule update after checkout <revision>

From
Stefan Beller <sbeller@google.com>
Date
Jun 3, 2016, 22:53 UTC
Message-ID
<CAGZ79kb9xHNYysb6gS9nPWvFW3cgcW-ey+5qyfTHTPGkT0fNfw@mail.gmail.com>

When checking out a new revision in a repo with submodules, one of the first commands after checkout is `git submodule update` to make sure the submodules are updated.

I propose to have a switch which when turned on automatically runs `git submodule update` for you instead of implementing proper submodule support in checkout for example.

advantages:
* users are already used to the quirks of `submodule update`
* a lot of config options exist for the behavior of `submodule update`
disadvantages:
* it's not `done right`, i.e. dealing with gitlinks in read-tree/unpack-tree
   but just another command chained after checkout, so we would do that
   for pull too eventually?
What do you think?

Thanks, Stefan

Next: Stefan Beller
Message 1 of 2 in “RFC: have a config option for running submodule update after checkout <revision>”
  1. Stefan BellerJun 3, 2016
  2. Stefan BellerJun 3, 2016

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.