From: Damien Robert Date: Tue, 03 Mar 2020 17:07:38 GMT Subject: [PATCH v2 3/5] doc: explain how to deactivate recurse.submodule completely Message-ID: <20200303170740.1879432-4-damien.olivier.robert+git@gmail.com> In-Reply-To: <20200303170740.1879432-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..74e691a487 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 by calling + `--no-recurse-submodules`. Note that some Git commands without 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. + since `submodule.recurse`. In this case a solution is to temporary + 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.25.1-377-g2d2118b814 (git version 2.25.1)