From: Junio C Hamano <gitster@pobox.com>
To: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
Cc: Josh Triplett <josh@joshtriplett.org>,
git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH v2] format-patch: Add --rfc for the common case of [RFC PATCH]
Date: Mon, 19 Sep 2016 10:49:17 -0700 [thread overview]
Message-ID: <xmqqa8f3g4pu.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <3df15bbb-7eac-86ec-2ccb-74a973482e8c@au1.ibm.com> (Andrew Donnellan's message of "Mon, 19 Sep 2016 19:17:28 +1000")
Andrew Donnellan <andrew.donnellan@au1.ibm.com> writes:
> Sounds good to me. Agreed that "RFC" is essentially the only prefix
> other than "PATCH" that I see, at least in the kernel.
Around here I think we saw WIP too, and that makes me lean towards
Peff's earlier suggestion to allow an end-user supplied string in
front of PATCH, i.e. "-P RFC" => "--subject-prefix='RFC PATCH'",
even though I understand that those who _ONLY_ care about RFC would
prefer --rfc (5 keystrokes) over "-P RFC" (6 keystrokes).
>> +--rfc::
>> + Alias for `--subject-prefix="RFC PATCH"`. Use this when
>> + sending an experimental patch for discussion rather than
>> + application.
>
> Perhaps mention the phrase "Request For Comment" for the benefit of
> those who aren't familiar ...
Good point.
next prev parent reply other threads:[~2016-09-19 17:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 7:21 [PATCH v2] format-patch: Add --rfc for the common case of [RFC PATCH] Josh Triplett
2016-09-17 18:43 ` Jeff King
2016-09-19 9:17 ` Andrew Donnellan
2016-09-19 17:49 ` Junio C Hamano [this message]
2016-09-19 20:44 ` Josh Triplett
2016-09-19 23:34 ` Jeff King
2016-09-19 23:40 ` Josh Triplett
2016-09-19 23:46 ` Jacob Keller
2016-09-19 23:55 ` Josh Triplett
2016-09-19 23:57 ` Jacob Keller
2016-09-20 1:37 ` Jeff King
2016-09-20 1:37 ` Jeff King
2016-09-20 6:50 ` Jacob Keller
2016-09-19 23:44 ` Jacob Keller
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=xmqqa8f3g4pu.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=git@vger.kernel.org \
--cc=josh@joshtriplett.org \
--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 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.