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

git submodules

From
Steven Noonan <steven@uplinklabs.net>
Date
Oct 17, 2009, 17:15 UTC
Message-ID
<f488382f0910171015j1a6d4d9fg690867154334c514@mail.gmail.com>

One of the open source projects I work on (CC'd) recently moved to git, but we're having some slight problems, and I believe that it's the fault of git's UI in this case.

We're using git submodules for the contributing libraries. When I commit changes to those contribs, it correctly shows in the parent repository that those folders have different revisions than what's currently committed. However, if someone pulls those changes, it doesn't automatically update the contribs to match the committed version. But doing a pull or merge _should_ update the working tree to match the committed versions. It does with file data, so why not update the submodules? Especially if the submodule revision matched the committed version -before- the pull. Why are we forced into using 'git submodule update'?

- Steven
Next: Jakub Narebski
Message 1 of 4 in “git submodules”
  1. Steven NoonanOct 17, 2009
  2. Jakub NarebskiOct 17, 2009
  3. Nanako ShiraishiOct 17, 2009
  4. Avery PennarunOct 21, 2009

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.