diff options
| author | W. Trevor King <wking@tremily.us> | 2014-02-03 03:36:11 -0800 |
|---|---|---|
| committer | W. Trevor King <wking@tremily.us> | 2014-02-03 04:11:17 -0800 |
| commit | e3355ef27b3593f76acf98d9d4ce8602dd7578ee (patch) | |
| tree | 25c4084e2d99927e22a79dd7d158a509a748b8a5 | |
| parent | ad468ef7beeb19a7e08bf6acdb55629bdcfd8ca0 (diff) | |
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).
| -rw-r--r-- | contributing.mdwn | 15 |
1 files changed, 7 insertions, 8 deletions
diff --git a/contributing.mdwn b/contributing.mdwn index 3729a76..8650e13 100644 --- 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 |