From: Jeff King <peff@peff.net>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH master] expand "<branch>" in format.subjectprefix
Date: Wed, 13 Jan 2010 15:29:31 -0500 [thread overview]
Message-ID: <20100113202930.GC23018@coredump.intra.peff.net> (raw)
In-Reply-To: <1263402988-925-1-git-send-email-rep.dot.nop@gmail.com>
On Wed, Jan 13, 2010 at 06:16:28PM +0100, Bernhard Reutner-Fischer wrote:
> Replace "<branch>" with the current branch name for
> [format]
> subjectprefix = PATCH <branch>
>
> A subject-prefix given on the command-line overrides the one given in
> the config.
I don't have a big opinion on whether this feature is useful (it
wouldn't be to me, but I can see workflows where it could be).
I'm not sure that "current branch" makes sense, though. format-patch is
about showing commits, and the current branch is not a property of that
commit. It is about where you happen to be currently. So doing:
git checkout X
git format-patch Y..Z --subject-prefix "PATCH <branch>"
shows "X" which is not really useful information. Something like git
log's "--source" would be more useful; it shows the command-line ref
that was used to reach a given commit.
Also, please don't introduce a new substitution syntax. We already have
code to do %-expansion. In fact, if you are going to do something like
this, maybe it would be best as two patches:
1. Support '%B' as a user-format expansion for the --source branch.
2. Support user-format expansions in the subject prefix.
But I don't know if people would find any of the other substitutions
useful in the subject line.
-Peff
prev parent reply other threads:[~2010-01-13 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 17:16 [PATCH master] expand "<branch>" in format.subjectprefix Bernhard Reutner-Fischer
2010-01-13 20:29 ` 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=20100113202930.GC23018@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=rep.dot.nop@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).