From: Damien Robert Date: Sun, 05 Apr 2020 20:16:31 GMT Subject: [PATCH v5 3/5] doc: explain how to deactivate submodule.recurse completely Message-ID: <20200405201633.704987-4-damien.olivier.robert+git@gmail.com> In-Reply-To: <20200405201633.704987-1-damien.olivier.robert+git@gmail.com> Signed-off-by: Damien Robert --- Documentation/config/submodule.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/config/submodule.txt b/Documentation/config/submodule.txt index 5962f41ead..d7a63c8c12 100644 --- a/Documentation/config/submodule.txt +++ b/Documentation/config/submodule.txt @@ -63,6 +63,13 @@ submodule.recurse:: (`checkout`, `fetch`, `grep`, `pull`, `push`, `read-tree`, `reset`, `restore` and `switch`) except `clone` and `ls-files`. Defaults to false. + When set to true, it can be deactivated via the + `--no-recurse-submodules` option. Note that some Git commands + lacking this option may call some of the above commands affected by + `submodule.recurse`; for instance `git remote update` will call + `git fetch` but does not have a `--no-recurse-submodules` option. + For these commands a workaround is to temporarily change the + configuration value by using `git -c submodule.recurse=0`. submodule.fetchJobs:: Specifies how many submodules are fetched/cloned at the same time. -- Patched on top of v2.26.0-106-g9fadedd637 (git version 2.26.0)