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

submodules and branches

From
SHStephen Hemminger <stephen.hemminger@vyatta.com>
Date
Apr 25, 2008, 00:41 UTC
Message-ID
<20080424174142.5dbb6ae3@speedy>

Our CM team likes to use both submodules and branches and it doesn't always work cleanly. Some examples:

1. The new release on branch "next_release" adds a submodule, but then the
submodule shows up on all branches including the production branch.
2. For next release on branch "next_release" a submodule was renamed by
moving the target directory, but now git submodule update makes two copies.

Git generally does a good job of tracking renames and deletions, so the fact that submodules leave stuff behind is surprising.

Message 1 of 1 in “submodules and branches”
  1. Stephen HemmingerApr 25, 2008

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.