Re: [PATCH v3 2/5] doc: document --recurse-submodules for reset and restore
- From
- Damien Robert <damien.olivier.robert@gmail.com>
- Date
- Mar 25, 2020, 21:05 UTC
- Message-ID
- <20200325210503.bhkwj5v2xdpjtnvp@doriath>
- In-Reply-To
- <298AFA4F-3D0D-46C7-872A-9B0A0F38E770@gmail.com>
From Philippe Blain, Sun 22 Mar 2020 at 18:36:23 (-0400) :
Show 5 quoted lines
> > +--[no-]recurse-submodules:: > > + When the working tree is updated, using --recurse-submodules will > > + also recursively reset the working tree of all active submodules > > + according to the commit recorded in the superproject, also setting > > + the submodules HEAD to be detached at that commit.
> I *think* that should be "the submodules' HEADs" but I'd prefer that a native speaker confirm.
This was copied from read-tree. So I'll update it too in my next reroll.
Show 5 quoted lines
> > + the working tree, the submodule will only be updated if this option > > + is given, in which case its working tree will be restored to the > > + commit recorded in the superproject, and any local modifications > > + overwritten. If nothing (or `--no-recurse-submodules`) is used, > > + the work trees of submodules will not be updated. Just like
> For consistency I'd use "working trees" here also, as in the first sentence. > In fact I think it would read better as "submodules working trees will not be updated".
Likewise, this was copied from checkout (and switch). I'll update all of them.
-- Damien Robert http://www.normalesup.org/~robert/pro