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 13, 2009, 13:11 UTC
Message-ID
<4AD47C65.5080904@web.de>
In-Reply-To
<alpine.DEB.2.00.0910131115160.14223@ds9.cixit.se>
Peter Krefting schrieb:
> If I have a repository with submodules that is in a clean state, and
> switch branches in the super repository, the submodules are left in the
> state they were in before I switched branches (with 1.6.4, at least). Is
> this the expected behaviour?
Yup, submodules have to be updated separatly.

When they are cloned from a remote with "git submodule add" followed by a "git submodule init", 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).

Jens
Previous: Peter KreftingNext: Peter Krefting
Message 2 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.