From: Jeff King <peff@peff.net>
To: Will Palmer <wmpalmer@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH/RFC resend] diff-options: make --patch a synonym for -p
Date: Thu, 13 May 2010 07:45:54 -0400 [thread overview]
Message-ID: <20100513114554.GA10963@coredump.intra.peff.net> (raw)
In-Reply-To: <1273741140.2516.15.camel@wpalmer.simply-domain>
On Thu, May 13, 2010 at 09:59:00AM +0100, Will Palmer wrote:
> Here we simply make --patch a synonym for -p, whose mnemonic was "patch"
> all along.
Yeah, makes sense to me. We already have --patch-with-stat and
--patch-with-raw (even though they are just historical), so clearly
--patch is the obvious choice.
> Re-sending, as this seems to have slipped under the radar last time.
Junio is incommunicado for a bit. I don't know how able he'll be to comb
through the list once he gets back, so you may need to an eye out and
resend again in a week or so. :)
-Peff
prev parent reply other threads:[~2010-05-13 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 8:59 [PATCH/RFC resend] diff-options: make --patch a synonym for -p Will Palmer
2010-05-13 11:39 ` Matthieu Moy
2010-05-13 11:45 ` Jeff King [this message]
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=20100513114554.GA10963@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=wmpalmer@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 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).