From: Junio C Hamano <gitster@pobox.com>
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: pclouds@gmail.com, artagnon@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH] standardize usage strings that were missed the first time
Date: Sun, 03 May 2015 16:59:06 -0700 [thread overview]
Message-ID: <xmqq4mntusad.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq383dwpf4.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Sun, 03 May 2015 10:18:07 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Alex Henrie <alexhenrie24@gmail.com> writes:
>
>> This is a follow-up to commit 9c9b4f2f8b7f27f3984e80d053106d5d41cbb03b.
>
> Please do not force the reader to type "git show 9c9b4f2".
Here is my attempt.
commit ce41720cad79d858f09ebfc88cf84a4b152645c7
Author: Alex Henrie <alexhenrie24@gmail.com>
Date: Thu Apr 2 15:26:56 2015 -0600
blame, log: format usage strings similarly to those in documentation
Earlier, 9c9b4f2f (standardize usage info string format, 2015-01-13)
tried to make usage-string in line with the documentation by
- Placing angle brackets around fill-in-the-blank parameters
- Putting dashes in multiword parameter names
- Adding spaces to [-f|--foobar] to make [-f | --foobar]
- Replacing <foobar>* with [<foobar>...]
but it missed a few places.
Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
next prev parent reply other threads:[~2015-05-03 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 3:12 [PATCH] standardize usage strings that were missed the first time Alex Henrie
2015-05-03 17:18 ` Junio C Hamano
2015-05-03 23:59 ` Junio C Hamano [this message]
2015-05-04 17:49 ` Alex Henrie
2015-05-04 19:23 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2015-04-02 21:26 Alex Henrie
2015-04-02 21:56 ` Junio C Hamano
2015-04-03 22:47 ` Alex Henrie
2015-04-03 23:48 ` 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=xmqq4mntusad.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=alexhenrie24@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.