Re: [PATCH 4/8] Doc/gitsubmodules: avoid abbreviations
- From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
- Date
- Jan 9, 2018, 16:06 UTC
- Message-ID
- <b59bd56a-f88b-a65a-263f-2b6d2f57dd99@gmail.com>
- In-Reply-To
- <CAGZ79kZZf=zSfqFr9EV_Q408mG4cHTEQSOAMC7n_35oKgHJp2A@mail.gmail.com>
On Tuesday 09 January 2018 12:15 AM, Stefan Beller wrote:
Show 10 quoted lines
>> >> - * The command line for those commands that support taking submodule specs. > > ++ The command line for those commands that support taking submodules > as part of their pathspecs[1]. > ++ > ++[1] pathspec is an official term according to `man gitglossary`. > > Maybe? >
Yeah, I actually did think 'specification' wasn't a the best fit for this (should have mentioned that somewhere) Now, the real term came out :)
Just to be sure, that "[1] pathspec ..." part goes to the end of the document doesn't it?
Show 11 quoted lines
>> - Most commands have a boolean flag '--recurse-submodules' whether to >> - recurse into submodules. Examples are `ls-files` or `checkout`. >> + * The command line for those commands that support taking submodule >> + specifications. Most commands have a boolean flag '--recurse-submodules >> + whether to recurse into submodules. Examples are `ls-files` or `checkout`. >> Some commands take enums, such as `fetch` and `push`, where you can >> specify how submodules are affected. >> >> -- >> 2.16.0.rc0.223.g4a4ac8367 >>