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

Question related to submodule and different recurse config options

From
PBPieter-Jan Busschaert <pieterjan.busschaert@gmail.com>
Date
Sep 8, 2022, 15:01 UTC
Message-ID
<CABxXVRS-9unw-8_N8w2bdj4E5Ch780tMetJyD+++ixdWsBv90A@mail.gmail.com>
Hello,

I'm trying to set my git config like this (fetch.recurseSubmodules = on-demand) and (submodule.recurse = true). The goal is to do fetch & submodule update if-and-only-if the pointed-to commit changes.

However, it seems with this config a git pull will act as if fetch.recurseSubmodules was set to true (instead of on-demand) and do a fetch on all of the submodules. For me this does not correspond to the documentation (which says the value of submodule.recurse will only be used if fetch.recurseSubmodules is NOT set). I would have thought that this recent commit: https://github.com/git/git/commit/ed54e1b31ad1a9a35ef6c23024d325a2c4d85221 describes this scenario and fixed it, but I still have that behaviour (git 2.37.3). Maybe that patch only covered true/false settings for fetch.recurseSubmodules and doesn't properly handle the on-demand setting?

Is what I see the intended behaviour? Is it possible in any way to configure git to only fetch & update submodules if the pointed-to commit changes?

Kind regards,
Pieter-Jan
Next: Philippe Blain
Message 1 of 3 in “Question related to submodule and different recurse config options”
  1. Pieter-Jan BusschaertSep 8, 2022
  2. Philippe BlainSep 18, 2022
  3. Glen ChooSep 19, 2022

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.