From: "Frédéric Delanoy" <frederic.delanoy@gmail.com>
To: git@vger.kernel.org
Subject: Using really empty start prefixes for git-format-patch numbered patches?
Date: Sat, 28 May 2011 23:57:01 +0200 [thread overview]
Message-ID: <BANLkTikVQWN2kZ4gc8kd-kJWZhLXgkvTAA@mail.gmail.com> (raw)
Hi,
I'm trying to generate numbered patches using git-format-patch such
that I get e.g. [1/2] instead of [PATCH 1/2]
However, if I use an empty string as prefix, for instance in
git-format-patch --subject-prefix="" -2
an extraneous space is inserted, and I get [ 1/2] instead of desired
[1/2] in the Subject line
(I also tried using a single backspace char as prefix, but that didn't
change anything, as might have been expected)
Is there a way to get rid of this space? IMO the space should only be
added if the prefix is non-empty
Frédéric Delanoy
next reply other threads:[~2011-05-28 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 21:57 Frédéric Delanoy [this message]
2011-05-30 13:04 ` Using really empty start prefixes for git-format-patch numbered patches? Frédéric Delanoy
2011-05-30 14:19 ` Jeff King
2011-05-30 19:19 ` Junio C Hamano
2011-05-30 20:23 ` Jeff King
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=BANLkTikVQWN2kZ4gc8kd-kJWZhLXgkvTAA@mail.gmail.com \
--to=frederic.delanoy@gmail.com \
--cc=git@vger.kernel.org \
/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).