Commit 59fa7b7f authored by Francesco Nwokeka's avatar Francesco Nwokeka Committed by Thomas Petazzoni
Browse files

docs/manual: add useful tips on patch versioning and patch submission 



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

[Thomas: minor tweaks.]

Signed-off-by: default avatarFrancesco Nwokeka <francesco.nwokeka@gmail.com>
Acked-by: default avatarArnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
parent 2d6a1575

docs/manual/contribute.txt

+14 −0
Original line number Diff line number Diff line
@@ -298,6 +298,13 @@ $ git format-patch --subject-prefix "PATCH v4" \ 
    -M -s -o outgoing origin/master

---------------------



Since git version 1.8.1, you can also use +-v <n>+ (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 +313,13 @@ 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.



You can also add the +--in-reply-to <message-id>+ option when

submitting a patch to the mailing list. The id of the mail to reply to

can be found under the "Message Id" tag on

http://patchwork.buildroot.org[patchwork].  The advantage of

*in-reply-to* is that patchwork will automatically mark the previous

version of the patch as superseded.



[[reporting-bugs]]

=== Reporting issues/bugs or getting help