Re: [PATCH v2 1/1] reset: support the --stdin option
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jan 27, 2017, 17:34 UTC
- Message-ID
- <alpine.DEB.2.20.1701271832270.3469@virtualbox>
- In-Reply-To
- <20170127170422.lvpghp6jdud37zxx@sigill.intra.peff.net>
Hi Peff,
On Fri, 27 Jan 2017, Jeff King wrote:
Show 18 quoted lines
> On Fri, Jan 27, 2017 at 01:38:55PM +0100, Johannes Schindelin wrote: > > A few minor suggestions: > > > +--stdin:: > > + Instead of taking list of paths from the command line, > > + read list of paths from the standard input. Paths are > > + separated by LF (i.e. one path per line) by default. > > + > > +-z:: > > + Only meaningful with `--stdin`; paths are separated with > > + NUL character instead of LF. > > Is it worth clarifying that these are paths, not pathspecs? The word > "paths" is used to refer to the pathspecs on the command-line elsewhere > in the document. > > It might also be worth mentioning the quoting rules for the non-z case.
I think this would be overkill. In reality, --stdin without -z does not make much sense, anyway.
If you feel strongly about it, I encourage you to submit a follow-up patch.
The rest of your suggestions have been implemented in v3.
Ciao, Johannes