contributing: Recommend -vN over --subject-prefix="PATCH vN"

It's a lot easier to type, and it dates back to Git v1.8.2 (added with
98294e9, Merge branch 'jc/format-patch-reroll', 2013-01-11).

diff --git a/contributing.mdwn b/contributing.mdwn
index 3729a766cbbc9948401b3c149a15d8c6131227aa..8650e1311f8338d804fcbce47d9e1a3f539ee7bb 100644 (file)
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -190,14 +190,13 @@ have changed; be sure to rebase your updated changes on top of the
 current master.
 
 Once you have the updated series ready, send it to the mailing list
-again. It will be helpful for others to use the
-`--subject-prefix="PATCH vN"` option of `git format-patch` or
-`git send-email` to add a version number of the patch series to the
-subject (replacing vN with v2, v3, etc.) Use a cover letter (or, in
-the case of a single patch, the notes after a "---" at the end of the
-commit message) to summarize the main changes since the previous
-version of the patch series. Also include the message-id reference of
-the previous version.
+again. It will be helpful for others to use the `-vN` option of `git
+format-patch` or `git send-email` to add a version number of the patch
+series to the subject (replacing vN with v2, v3, etc.) Use a cover
+letter (or, in the case of a single patch, the notes after a "---" at
+the end of the commit message) to summarize the main changes since the
+previous version of the patch series. Also include the message-id
+reference of the previous version.
 
 Using the `--in-reply-to` option of `git format-patch` or
 `git send-email` to send the patch series as a reply to the earlier