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

Re: Why are submodules not automatically handled by default or at least configurable to do so?

From
NNick <oinksocket@letterboxes.org>
Date
Oct 27, 2015, 10:50 UTC
Message-ID
<562F5704.5070405@letterboxes.org>
In-Reply-To
<D4E5E890658.000004DCjohsmi9933@inbox.com>

I too am interested in finding ways to automate working with submodules, as it's a particular pain point with my colleagues. They frequently shoot themselves in the foot trying to branch and merge a project with submodules, resulting in a broken build and grumpy comments about git (or possibly about me, as the "Git Advocate"). And they're right, it is awkward.

Whether or not any sensible default configuration exists, users do need a way to avoid excessively complicated workflows, or people are just going to avoid using submodules, or perhaps Git. Hand-rolled solutions might be better than nothing, but I would expect that this is a common issue which would benefit from a built-in solution. For instance, so that one can branch and merge the whole project without duplicating the work for each submodule.

Am I correct in thinking there isn't anything which does these kind of things yet?

Thanks!
Nick
Previous: Nazri RamliyNext: Davide Fiorentino
Message 8 of 11 in “Why are submodules not automatically handled by default or at least configurable to do so?”
  1. John SmithOct 25, 2015
  2. Chris PackhamOct 26, 2015
  3. Stefan BellerOct 26, 2015
  4. Junio C HamanoOct 26, 2015
  5. Nazri RamliyOct 26, 2015
  6. Jens LehmannOct 26, 2015
  7. Nazri RamliyOct 28, 2015
  8. NickOct 27, 2015
  9. Davide FiorentinoOct 27, 2015
  10. NickOct 27, 2015
  11. Konstantin KhomoutovOct 27, 2015

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.