deepcrayon/buildroot
deepcrayon/buildroot
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

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

Browse source 
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: Francesco Nwokeka <francesco.nwokeka@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
This commit is contained in:
Francesco Nwokeka 2015-09-08 17:28:04 +02:00 committed by Thomas Petazzoni
parent 2d6a1575ac
commit 59fa7b7f7c
1 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
docs/manual/contribute.txt
View file

@ -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