Re: [PATCH 0/4] doc: --recurse-submodules

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Le 28 févr. 2020 à 05:44, Damien Robert <damien.olivier.robert@xxxxxxxxx> 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.

> 
> 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





[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux