[PATCH 1/1] looks a bit silly, and automagically handling this in git-format-patch makes some scripting around it a lot more pleasant. Signed-off-by: Andreas Ericsson <ae@xxxxxx> --- Documentation/git-format-patch.txt | 3 ++- builtin-log.c | 4 ++++ 2 files changed, 6 insertions(+), 1 deletions(-) diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt index c9857a2..9f16951 100644 --- a/Documentation/git-format-patch.txt +++ b/Documentation/git-format-patch.txt @@ -56,7 +56,8 @@ If -o is specified, output files are created in <dir>. Otherwise they are created in the current working directory. If -n is specified, instead of "[PATCH] Subject", the first line -is formatted as "[PATCH n/m] Subject". +is formatted as "[PATCH n/m] Subject" if the revision range to +format contains more than one commit. If given --thread, git-format-patch will generate In-Reply-To and References headers to make the second and subsequent patch mails appear diff --git a/builtin-log.c b/builtin-log.c index e8b982d..5c48f4d 100644 --- a/builtin-log.c +++ b/builtin-log.c @@ -642,6 +642,10 @@ int cmd_format_patch(int argc, const char **argv, const char *prefix) list[nr - 1] = commit; } total = nr; + + /* don't number patches when there's only one */ + if (total == 1) + numbered = 0; if (numbered) rev.total = total + start_number - 1; rev.add_signoff = add_signoff; -- 1.5.3.4.1273.g725c19 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
