git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pieter-Jan Busschaert <pieterjan.busschaert@gmail.com>
To: git@vger.kernel.org
Subject: Question related to submodule and different recurse config options
Date: Thu, 8 Sep 2022 17:01:19 +0200	[thread overview]
Message-ID: <CABxXVRS-9unw-8_N8w2bdj4E5Ch780tMetJyD+++ixdWsBv90A@mail.gmail.com> (raw)

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

             reply	other threads:[~2022-09-08 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 15:01 Pieter-Jan Busschaert [this message]
2022-09-18 14:36 ` Question related to submodule and different recurse config options Philippe Blain
2022-09-19 18:43   ` Glen Choo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABxXVRS-9unw-8_N8w2bdj4E5Ch780tMetJyD+++ixdWsBv90A@mail.gmail.com \
    --to=pieterjan.busschaert@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).