Re: [PATCH 0/4] doc: --recurse-submodules
- From
Philippe Blain <levraiphilippeblain@gmail.com>
- Date
- Mar 3, 2020, 05:18 UTC
- Message-ID
- <FF79EA85-4A15-4B4B-B59E-657E0488D4C6@gmail.com>
- In-Reply-To
- <20200228104449.o42twhy34fynalk4@feanor>
Show 7 quoted lines
> Le 28 févr. 2020 à 05:44, Damien Robert <damien.olivier.robert@gmail.com> a écrit : > > Note that git-switch.txt states that > Using `--recurse-submodules` will update the content of all > initialized submodules according to the commit recorded in the > superproject. > but actually only 'active' submodules will be updated.
Technically that’s true, but I’d say that in a "simple" workflow (you clone a superproject then do `git submodule update --init`, then maybe set `submodule.recurse` to true), then being active and being initialized are equivalent. So I don’t think it’s that big of an issue.
In any case, if such a change is made, the doc for all commands that have the flag should be revised, as both "initialized" (grep, checkout, switch, read-tree) and "populated" (fetch, pull) seems to be used currently.
Show 7 quoted lines
> > Should I also update the doc? It is already stated in `gitsubmodules(7)` > that only 'active' submodules are considered for recursion. > > -- > Damien Robert > http://www.normalesup.org/~robert/pro