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
Nazri Ramliy <ayiehere@gmail.com>
Date
Oct 28, 2015, 07:36 UTC
Message-ID
<CAEY4ZpNrvF3-aLYpoN1+Qi-ZcFUqh_t8QrVpWqqgnEHqF4_cOQ@mail.gmail.com>
In-Reply-To
<562E5B41.9090801@web.de>
On Tue, Oct 27, 2015 at 12:56 AM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
> Which seems a bit error prone as you could forget to update the submodules
> and build incorrect rpms from them, or am I missing something?

For my case I'm not building the rpms directly after merging in the fixes done in the octopus branch, so I don't care much about the state of the submodules after the merge since I know that the octopus branch does not modify any submodules. The rpms are built later on, possibly on another machine where the submodules are updated w.r.t to each branch in a release commit.

> I understand why you don't need to update the submodules every time, but
> would it hurt your workflow if they did (but don't get me wrong, that will
> always be configurable).

I'd say it depends - for the times when all I want to do is work on plain files in the superproject (on an octopus branch for example) I don't want git to automatically update the submodules everytime I switch branches - it would hurt my productivity as there will be more disk activities due to files being checked out unnecessarily for updating the submodules.

The submodule states are not committed that often into the superproject, they are done normally when we're cutting a new release. During day-to-day development each developer runs a script that pulls in the latest commits for "hot" submodules.

git not updating the submodule state automatically is actually a convenient for my particular use case here.

nazri
Previous: Jens LehmannNext: Nick
Message 7 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.