| Message ID | 20200303170740.1879432-4-damien.olivier.robert+git@gmail.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | doc: --recurse-submodules | expand |
Damien Robert <damien.olivier.robert@gmail.com> writes: > Signed-off-by: Damien Robert <damien.olivier.robert+git@gmail.com> > --- > 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 ;-).
From Damien Robert, Tue 03 Mar 2020 at 18:07:38 (+0100) : > + 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 ^^^^^^^^^^^^^^^^^^^^^^^^^^ Sorry this is a leftover from a previous formulation, I'll clean that up. > + change the configuration value by using `git -c submodule.recurse=0`.
On Tue, 3 Mar 2020, Junio C Hamano wrote: > Damien Robert <damien.olivier.robert@gmail.com> writes: > > > Signed-off-by: Damien Robert <damien.olivier.robert+git@gmail.com> > > --- > > 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." nooooooo ... my biggest gripe with documentation is the unnecessary use of superfluous words. :-) simply, "can be deactivated via the '--no-recurse-submodules' option." no one here's getting paid by the word. rday
> Le 3 mars 2020 à 17:04, Damien Robert <damien.olivier.robert@gmail.com> a écrit : > >> + since `submodule.recurse`. In this case a solution is to temporary > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > Sorry this is a leftover from a previous formulation, I'll clean that up. Also, the commit title still has the option name reversed: s/recurse.submodule/submodule.recurse/
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.
Signed-off-by: Damien Robert <damien.olivier.robert+git@gmail.com> --- Documentation/config/submodule.txt | 7 +++++++ 1 file changed, 7 insertions(+)