From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] usage: do not insist that standard input must come from a file
Date: Fri, 16 Oct 2015 13:08:37 -0700 [thread overview]
Message-ID: <xmqqk2qmefui.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20151016200452.GA1901@google.com> (Jonathan Nieder's message of "Fri, 16 Oct 2015 13:04:52 -0700")
Jonathan Nieder <jrnieder@gmail.com> writes:
>> --stdin::
>> - Read file names from stdin instead of from the command-line.
>> + Read pathnames from stdin instead of from the command-line.
>
> Here I have to read the description of "-z" to understand that pathnames
> come one per line. How about
>
> Read pathnames from stdin, one per line, instead of from the command
> line.
Thanks, that would be better (and for all the other one-per-line
type of stuff).
next prev parent reply other threads:[~2015-10-16 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 18:27 [PATCH] usage: do not insist that standard input must come from a file Junio C Hamano
2015-10-16 20:04 ` Jonathan Nieder
2015-10-16 20:08 ` Junio C Hamano [this message]
2015-10-16 22:26 ` Junio C Hamano
2015-10-16 22:58 ` Jonathan Nieder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqk2qmefui.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).