@@ -110,7 +110,8 @@ Any changes in progress, staged or unstaged, will remain intact.
To start working on the branch again, use \fBgit series checkout\fR.
.TP
-\fBgit series format\fR [\fB--in-reply-to=\fR\fIMessage-Id\fR] [\fB--stdout\fR]
+\fBgit series format\fR [\fB--in-reply-to=\fR\fIMessage-Id\fR] \
+[\fB-v\fR \fIN\fR | \fB--reroll-count=\fR\fIN\fR] [\fB--stdout\fR]
Prepare the patch series to send via email.
This creates one file per patch in the series, plus one additional file for the
cover letter if any.
@@ -129,6 +130,10 @@ Make the first mail a reply to the specified Message-Id.
The Message-Id may include or omit the surrounding angle brackets; git-series
will add them if not present.
.TP
+\fB-v\fR \fIN\fR | \fB--reroll-count=\fB\fIN\fR
+Mark the patch series as PATCH v\fIN\fR.
+The patch filenames and mail subjects will include the version number.
+.TP
.B --stdout
Write the entire patch series to stdout rather than to separate patch files.
.RE