From: Junio C Hamano <gitster@pobox.com>
To: Denton Liu <liu.denton@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH 2/3] Doc: add more detail for git-format-patch
Date: Tue, 20 Aug 2019 12:01:21 -0700 [thread overview]
Message-ID: <xmqq1rxfveym.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <7619da962d1fc804392e3552fbd56bf4bc68ac38.1566182184.git.liu.denton@gmail.com> (Denton Liu's message of "Sun, 18 Aug 2019 22:37:37 -0400")
Denton Liu <liu.denton@gmail.com> writes:
> Next, while we're at it, surround option arguments with <>.
> ...
> [--start-number <n>] [--numbered-files]
> - [--in-reply-to=Message-Id] [--suffix=.<sfx>]
> + [--in-reply-to=<Message-Id>] [--suffix=.<sfx>]
> [--ignore-if-in-upstream]
> - [--rfc] [--subject-prefix=Subject-Prefix]
> + [--rfc] [--subject-prefix=<Subject-Prefix>]
> ...
> ---in-reply-to=Message-Id::
> +--in-reply-to=<Message-Id>::
That is a good change, but if we are making this change while are at
it, I think we should fix it to read <message id>. "Message-Id" is
a good spelling iff we are talking about the label on the left hand
side of colon in e-mail header, but in this context, we are talking
about the value to be placed on that header.
All the other multi-word placeholders in the SYNOPSIS section spell
the words as normal multiple words separated with whitespace in
lower case. You'd also want to fix the spelling of Subject-Prefix
to <subject prefix> for consistency.
Thanks.
next prev parent reply other threads:[~2019-08-20 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 2:37 [PATCH 0/3] format-patch: teach --infer-cover-subject option Denton Liu
2019-08-19 2:37 ` [PATCH 1/3] t4014: clean up style Denton Liu
2019-08-19 16:02 ` Eric Sunshine
2019-08-19 2:37 ` [PATCH 2/3] Doc: add more detail for git-format-patch Denton Liu
2019-08-19 17:09 ` Eric Sunshine
2019-08-19 23:16 ` Denton Liu
2019-08-20 19:01 ` Junio C Hamano [this message]
2019-08-19 2:37 ` [PATCH 3/3] format-patch: infer cover letter from branch description Denton Liu
2019-08-19 17:29 ` Eric Sunshine
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1rxfveym.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).