[Buildroot] [PATCH 1/1] docs/website: contribute.txt update with useful tips on patch versioning and patch submission

[Francesco Nwokeka]

Added an alternative on patch versioning (the -v option) and added a tip on how to automatically mark a previous commit as superseded

Signed-off-by: Francesco Nwokeka <francesco.nwokeka at gmail.com>
---
 docs/manual/contribute.txt | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
index 40579f9..1ab8ef8 100644
--- a/docs/manual/contribute.txt
+++ b/docs/manual/contribute.txt
@@ -298,6 +298,12 @@ $ git format-patch --subject-prefix "PATCH v4" \
     -M -s -o outgoing origin/master
 ---------------------
 
+or the +-v <n>+ flag (where <n> is the version number):
+
+---------------------
+$ git format-patch -v4 -M -s -o outgoing origin/master
+---------------------
+
 When you provide a new version of a patch, please mark the old one as
 superseded in http://patchwork.buildroot.org[patchwork]. You need to
 create an account on http://patchwork.buildroot.org[patchwork] to be
@@ -306,6 +312,9 @@ the status of patches you submitted yourself, which means the email
 address you register in http://patchwork.buildroot.org[patchwork] should
 match the one you use for sending patches to the mailing list.
 
+[NOTE]
+_You can also add the +--in-reply-to "<previous-version-id>"+ flag when submitting a patch to the mailing list (via git sendmail). The id of the mail to reply to can be found under the "Message Id" tag on the patchwork website. The advantage of *in-reply-to* is that patchwork will automatically mark the previous patch as superseded_
+
 [[reporting-bugs]]
 === Reporting issues/bugs or getting help
 
-- 
2.5.1