From: Taylor Blau <me@ttaylorr.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>, liu.denton@gmail.com
Subject: Re: [PATCH] ls-files: use imperative mood for -X and -z option description
Date: Mon, 20 Sep 2021 11:08:08 -0400 [thread overview]
Message-ID: <YUij2Aj04B1Q1tRV@nand.local> (raw)
In-Reply-To: <20210920121940.905549-1-bagasdotme@gmail.com>
Hi Bagas,
On Mon, Sep 20, 2021 at 07:19:41PM +0700, Bagas Sanjaya wrote:
> Usage description for -X and -z options use descriptive instead of
> imperative mood. Change it for consistency with other options.
Your patch looks fine to me. I don't think it's urgent to change, but it
looks correct nonetheless.
> Cc: Jeff King <peff@peff.net>
> Cc: <liu.denton@gmail.com>
These Cc trailers can be removed. (They're not entirely unprecedented,
but I can only find ~200 examples in git.git's history).
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> builtin/ls-files.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/builtin/ls-files.c b/builtin/ls-files.c
> index 29a26ad8ae..1f38cd7b17 100644
> --- a/builtin/ls-files.c
> +++ b/builtin/ls-files.c
> @@ -614,7 +614,7 @@ int cmd_ls_files(int argc, const char **argv, const char *cmd_prefix)
> struct option builtin_ls_files_options[] = {
> /* Think twice before adding "--nul" synonym to this */
> OPT_SET_INT('z', NULL, &line_terminator,
> - N_("paths are separated with NUL character"), '\0'),
> + N_("separate paths with NUL character"), '\0'),
The text before your patch should include an article so it reads "with
[the] NUL character" instead of "with NUL character".
So I think the right post-image would be: "separate paths with the NUL
character".
Thanks,
Taylor
next prev parent reply other threads:[~2021-09-20 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 12:19 [PATCH] ls-files: use imperative mood for -X and -z option description Bagas Sanjaya
2021-09-20 15:08 ` Taylor Blau [this message]
2021-09-20 19:30 ` Junio C Hamano
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=YUij2Aj04B1Q1tRV@nand.local \
--to=me@ttaylorr.com \
--cc=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.com \
--cc=peff@peff.net \
/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).