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

Re: Force git submodule update --remote for some branches

From
Jens Lehmann <jens.lehmann@web.de>
Date
Nov 30, 2014, 14:52 UTC
Message-ID
<547B2F30.8090003@web.de>
In-Reply-To
<5478B6F1.6070200@gmail.com>
Am 28.11.2014 um 18:54 schrieb Timothy M. Redaelli:
Show 6 quoted lines
> I have a repository with a submodule and I'd like to force git to
> checkout the LAST version of the submodule and not the stored one (like
> git submodule update --remote), but only on some branches and without
> the need to remember to add --remote every time you are on this branch.
>
> Is there any way to do it? Maybe using .gitmodules?
Not yet.

But yes, .gitmodules would be the right place to put such a configuration as then it would be per submodule and also per (superproject-)branch.

By the way, what do you think the output of git status and git diff should look like when you updated a submodule to its branch tip which differs from the commit recorded in the superproject? Should these changes be displayed or not? And only if the new tip is a fast-forward of the old or always?

Previous: Timothy M. Redaelli
Message 2 of 2 in “Force git submodule update --remote for some branches”
  1. Timothy M. RedaelliNov 28, 2014
  2. Jens LehmannNov 30, 2014

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.