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

Re: Changing branches in supermodule does not affect submodule?

From
Jens Lehmann <jens.lehmann@web.de>
Date
Oct 14, 2009, 15:39 UTC
Message-ID
<4AD5F0B1.4000507@web.de>
In-Reply-To
<alpine.DEB.2.00.0910140728420.16100@ds9.cixit.se>
Peter Krefting schrieb:
Show 7 quoted lines
> Jens Lehmann:
> 
>> just calling "git submodule update" every time you want the submodule
>> to be updated according to the state committed in the superproject
>> will do the trick (but keep in mind that all referenced commits have
>> to be accessible in the local clone of your submodule, so you might
>> have to do a fetch there once in a while).
BTW: unless you use the -N or --no-fetch option, git submodule update
will do the fetch for you.
> Is it possible to automate this from a hook or something else?

Yep, you can use the post-checkout hook for that, just put a "git submodule update" in it.

*But*: If you do a checkout in the superproject while the submodule has new commits not contained in any branch (remember submodules often have a detached head) you'll silently lose these commits! Then only the reflog can help you ...

Previous: Peter KreftingNext: Heiko Voigt
Message 4 of 6 in “Changing branches in supermodule does not affect submodule?”
  1. Peter KreftingOct 13, 2009
  2. Jens LehmannOct 13, 2009
  3. Peter KreftingOct 14, 2009
  4. Jens LehmannOct 14, 2009
  5. implement sample post-checkout hook to checkout new/unchanged submodulesHeiko Voigt, Oct 14, 2009
  6. Junio C HamanoOct 14, 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.