[Buildroot] [PATCHv2] docs/manual: add the "mark as superseded" hint
Vicente Olivert Riera
Vincent.Riera at imgtec.com
Mon Sep 7 12:27:30 UTC 2015
Signed-off-by: Vicente Olivert Riera <Vincent.Riera at imgtec.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout at mind.be>
---
Changes v1 -> v2:
- Specify that an account in patchwork is needed (Suggested by Arnout)
docs/manual/contribute.txt | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
index 5f0762f..40579f9 100644
--- a/docs/manual/contribute.txt
+++ b/docs/manual/contribute.txt
@@ -298,6 +298,14 @@ $ git format-patch --subject-prefix "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
+able to modify the status of your patches. Note that you can only change
+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.
+
[[reporting-bugs]]
=== Reporting issues/bugs or getting help
--
1.7.1
More information about the buildroot
mailing list