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

Submodules with feature branches

From
RDRobert Dailey <rcdailey.lists@gmail.com>
Date
Jun 5, 2014, 14:03 UTC
Message-ID
<CAHd499Bn7CCVy=vhFzpLYXCssxR0oGxm3Vdgou_Yk5zSt1gfmA@mail.gmail.com>

I have a question regarding submodules and their applicability given our workflow at the place I work.

When I work on a feature, I normally create a feature branch. If I happen to make changes to the submodule that only work with the changes introduced in my feature branch, that seems to complicate things. For the purposes of the feature branch, do I need to create a corresponding feature branch in the submodule and temporarily update the submodule URL to point to it? When I merge my feature branch, I'd have to swap it back?

What is a recommended workflow for this? Thanks in advance.
Next: W. Trevor King
Message 1 of 7 in “Submodules with feature branches”
  1. Robert DaileyJun 5, 2014
  2. W. Trevor KingJun 5, 2014
  3. Robert DaileyJun 5, 2014
  4. W. Trevor KingJun 5, 2014
  5. Robert DaileyJun 5, 2014
  6. W. Trevor KingJun 5, 2014
  7. W. Trevor KingJun 5, 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.