From: Josh Triplett <josh@joshtriplett.org>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
Git mailing list <git@vger.kernel.org>
Subject: Re: [PATCH v2] format-patch: Add --rfc for the common case of [RFC PATCH]
Date: Mon, 19 Sep 2016 16:55:50 -0700 [thread overview]
Message-ID: <20160919235550.GC29421@cloud> (raw)
In-Reply-To: <CA+P7+xp-CupfFwQv+U-KNh4bxG9Mxkbfip5RJebKX9gjffoOsw@mail.gmail.com>
On Mon, Sep 19, 2016 at 04:46:06PM -0700, Jacob Keller wrote:
> On Mon, Sep 19, 2016 at 4:40 PM, Josh Triplett <josh@joshtriplett.org> wrote:
> > On Mon, Sep 19, 2016 at 04:34:35PM -0700, Jeff King wrote:
> >> As far as your patch goes, I'd be OK with defining:
> >>
> >> --rfc::
> >> Pretend as if `--subject-prefix='RFC PATCH'` was given.
> >>
>
> Would:
>
> Shorthand for `--subject-prefix='RFC PATCH'`
>
> be a better reading? I feel like using "pretend" is a bit weird here.
My patch used "Alias for"; if you prefer "Shorthand for" I'm
indifferent. :)
next prev parent reply other threads:[~2016-09-19 23:55 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
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 [this message]
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=20160919235550.GC29421@cloud \
--to=josh@joshtriplett.org \
--cc=andrew.donnellan@au1.ibm.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@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).