On Tue, 3 Mar 2020, Junio C Hamano wrote: > Damien Robert <damien.olivier.robert@xxxxxxxxx> writes: > > > diff --git a/Documentation/config/fetch.txt b/Documentation/config/fetch.txt > > index f11940280f..8f716809f9 100644 > > --- a/Documentation/config/fetch.txt > > +++ b/Documentation/config/fetch.txt > > @@ -2,10 +2,12 @@ fetch.recurseSubmodules:: > > This option can be either set to a boolean value or to 'on-demand'. > > Setting it to a boolean changes the behavior of fetch and pull to > > unconditionally recurse into submodules when set to true or to not > > - recurse at all when set to false. When set to 'on-demand' (the default > > - value), fetch and pull will only recurse into a populated submodule > > + recurse at all when set to false. When set to 'on-demand', > > + fetch and pull will only recurse into a populated submodule > > when its superproject retrieves a commit that updates the submodule's > > reference. > > + If not set, it fallbacks to the value of `submodule.recurse`, and > > + if both are not set the default value is 'on-demand'. missed earlier post ... "either set" should be "set either." also, adverbs technically *follow* what they qualify, so "unconditionally recusrse" should be "recurse unconditionally" and so on. it has always been thus. rday p.s. avoid use of the word "it" if it's potentially unclear what it refers to. in the above, one reads, "If not set, it falls back ..." *what* falls back?
