From d09bc51428274bbb03669e4fb33f74b4edbe40dd Mon Sep 17 00:00:00 2001 From: Damien Robert Date: Mon, 6 Apr 2020 15:57:07 +0200 Subject: [PATCH] doc: explain how to deactivate submodule.recurse completely Signed-off-by: Damien Robert Signed-off-by: Junio C Hamano --- 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.