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

Re: git submodules

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 17, 2009, 17:27 UTC
Message-ID
<m3tyxydj8f.fsf@localhost.localdomain>
In-Reply-To
<f488382f0910171015j1a6d4d9fg690867154334c514@mail.gmail.com>
Steven Noonan <steven@uplinklabs.net> writes:
Show 10 quoted lines
> 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'?

Because you might want not to use most current version of submodule, so git-pull shouldn't update submodules by default. And because git-pull didn't learn --recursive option yet.

-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Steven NoonanNext: Nanako Shiraishi
Message 2 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.