From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/7] format-patch --reroll-count
Date: Sat, 22 Dec 2012 00:33:25 -0800 [thread overview]
Message-ID: <1356165212-5611-1-git-send-email-gitster@pobox.com> (raw)
The --reroll-count=$N option, when given a positive integer:
- Adds " v$N" to the subject prefix specified. As the default
subject prefix string is "PATCH", --reroll-count=2 makes it
"PATCH v2".
- Prefixes "v$N-" to the names used for output files. The cover
letter, whose name is usually 0000-cover-letter.patch, becomes
v2-0000-cover-letter.patch when given --reroll-count=2.
This allows users to use the same --output-directory for multiple
iterations of the same series, without letting the output for a
newer round overwrite output files from the earlier rounds. The
user can incorporate materials from earlier rounds to update the
newly minted iteration, and use "send-email v2-*.patch" to send out
the patches belonging to the second iteration easily.
The early patches of this series are all preparatory clean-ups. I
think reopen_stdout() also can be cleaned up, but I'll leave it to
a future reroll.
Junio C Hamano (7):
builtin/log.c: drop unused "numbered" parameter from
make_cover_letter()
builtin/log.c: drop redundant "numbered_files" parameter from
make_cover_letter()
builtin/log.c: stop using global patch_suffix
get_patch_filename(): simplify function signature
get_patch_filename(): drop "just-numbers" hack
get_patch_filename(): split into two functions
format-patch: add --reroll-count=$N option
builtin/log.c | 33 ++++++++++++++++++++++++---------
log-tree.c | 52 +++++++++++++++++++++++++++++++---------------------
log-tree.h | 4 ++--
revision.h | 1 +
4 files changed, 58 insertions(+), 32 deletions(-)
--
1.8.0.6.gd28b5d4.dirty
next reply other threads:[~2012-12-22 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 8:33 Junio C Hamano [this message]
2012-12-22 8:33 ` [PATCH 1/7] builtin/log.c: drop unused "numbered" parameter from make_cover_letter() Junio C Hamano
2012-12-22 8:33 ` [PATCH 2/7] builtin/log.c: drop redundant "numbered_files" " Junio C Hamano
2012-12-22 8:33 ` [PATCH 3/7] builtin/log.c: stop using global patch_suffix Junio C Hamano
2012-12-22 8:33 ` [PATCH 4/7] get_patch_filename(): simplify function signature Junio C Hamano
2012-12-22 8:33 ` [PATCH 5/7] get_patch_filename(): drop "just-numbers" hack Junio C Hamano
2012-12-22 8:33 ` [PATCH 6/7] get_patch_filename(): split into two functions Junio C Hamano
2012-12-22 8:33 ` [PATCH 7/7] format-patch: add --reroll-count=$N option Junio C Hamano
2013-01-01 3:04 ` [PATCH 0/7] format-patch --reroll-count Duy Nguyen
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=1356165212-5611-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.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).