From: Andry <andry@inbox.ru>
To: Git <git@vger.kernel.org>
Subject: [ISSUE] `git submodule update --init --recursive` does ignore `fetchRecurseSubmodules` flag in `.gitmodules` and in `.git/config`
Date: Mon, 10 Jun 2024 04:19:10 +0300 [thread overview]
Message-ID: <153002248.20240610041910@inbox.ru> (raw)
Hello Git,
First discovered here: https://github.com/gitextensions/gitextensions/issues/11783
Another discussion: https://stackoverflow.com/questions/58403616/does-git-submodule-update-recursive-override-fetchrecursesubmodules
Manual: https://git-scm.com/docs/gitmodules#Documentation/gitmodules.txt-submoduleltnamegtfetchRecurseSubmodules
---
If use a recursive submodule, for example:
A->B->A->...
And call submodules Update on A, then the Update does ignore the flag and keeps fetch recursively with the error at the end:
> fatal: Failed to recurse into submodule path ...
Is that supposed to work this way or is an bug?
next reply other threads:[~2024-06-10 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 1:19 Andry [this message]
2024-06-10 22:02 ` [ISSUE] `git submodule update --init --recursive` does ignore `fetchRecurseSubmodules` flag in `.gitmodules` and in `.git/config` brian m. carlson
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=153002248.20240610041910@inbox.ru \
--to=andry@inbox.ru \
--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).