From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Beller <sbeller@google.com>,
Alexander Kuleshov <kuleshovmail@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] format-patch: print format-patch usage if there are no arguments
Date: Tue, 13 Jan 2015 17:45:31 -0500 [thread overview]
Message-ID: <20150113224531.GB3144@peff.net> (raw)
In-Reply-To: <xmqqiogaco3m.fsf@gitster.dls.corp.google.com>
On Tue, Jan 13, 2015 at 02:28:13PM -0800, Junio C Hamano wrote:
> On the other hand, "I am forked from building on this one" done with
> "checkout -t" is an explicit mark the user leaves, so it would serve
> as a better hint to base the default heuristics on, I think.
>
> But nobody is asking for such a feature ;-)
FWIW, I very rarely run format-patch directly, but have a wrapper script
that dumps the patches into a tempfile and runs mutt. I taught it in
2007 to use the upstream branch as the default[1], and was puzzled
reading the start of this thread, thinking we already did that.
So that is perhaps not asking for the feature (I am already happy with
my homegrown wrapper), but is maybe an endorsement of it. :)
-Peff
[1] You may note in 2007 that we did not even have @{upstream}. I
implemented it manually using git-config! Then in 2009, I switched
it to use for-each-ref's "%(upstream)" placeholder. Literally 5 days
later, Dscho introduced @{upstream}, but I never got around to
switching. Maybe now it is time. :)
next prev parent reply other threads:[~2015-01-13 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 17:54 [PATCH] format-patch: print format-patch usage if there are no arguments Alexander Kuleshov
2015-01-13 18:43 ` Junio C Hamano
2015-01-13 18:52 ` Alexander Kuleshov
2015-01-13 19:17 ` Junio C Hamano
2015-01-13 20:00 ` Stefan Beller
2015-01-13 22:28 ` Junio C Hamano
2015-01-13 22:45 ` Jeff King [this message]
2015-01-13 22:48 ` Stefan Beller
2015-01-14 1:28 ` my hacky mutt-specific format-patch workflow Jeff King
2015-01-13 23:41 ` [PATCH] format-patch: print format-patch usage if there are no arguments 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=20150113224531.GB3144@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kuleshovmail@gmail.com \
--cc=sbeller@google.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).