Damien Robert <damien.olivier.robert@xxxxxxxxx> writes: > Signed-off-by: Damien Robert <damien.olivier.robert+git@xxxxxxxxx> > --- > 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 You do not "call" an option [*1*]. Perhaps "... can be overriden by passing the `--no-recurse-submodules` option from the command line." > + 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`. A good piece of advice. [Footnote] *1* ... unless you are in a different business, that is ;-).
