From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] docs/website: contribute.txt update with useful tips on patch versioning and patch submission
Date: Tue, 8 Sep 2015 17:32:26 +0200 [thread overview]
Message-ID: <55EEFF8A.3050704@mind.be> (raw)
In-Reply-To: <1441726084-15422-1-git-send-email-francesco.nwokeka@gmail.com>
On 08-09-15 17:28, Francesco Nwokeka wrote:
> 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@gmail.com>
>
> ---
> v1 -> v2: adjusted previous patch with observations from mailing list
>
> Signed-off-by: Francesco Nwokeka <francesco.nwokeka@gmail.com>
> ---
> docs/manual/contribute.txt | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
> index 40579f9..e8707cc 100644
> --- a/docs/manual/contribute.txt
> +++ b/docs/manual/contribute.txt
> @@ -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,12 @@ 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>+ flag 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 the patchwork website.
Minor nit: in other places we always use
http://patchwork.buildroot.org[patchwork] instead of 'the patchwork website'.
Otherwise, looks good to me:
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> +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
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-09-08 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 13:22 [Buildroot] [PATCH 1/1] docs/website: contribute.txt update with useful tips on patch versioning and patch submission Francesco Nwokeka
2015-09-08 13:46 ` Arnout Vandecappelle
2015-09-08 14:57 ` Francesco Nwokeka
2015-09-08 15:03 ` Arnout Vandecappelle
2015-09-08 15:28 ` [Buildroot] [PATCH v2 " Francesco Nwokeka
2015-09-08 15:32 ` Arnout Vandecappelle [this message]
2015-09-08 15:47 ` [Buildroot] [PATCH v3 " Francesco Nwokeka
2015-09-15 14:03 ` Fabio Porcedda
2015-09-15 20:35 ` Arnout Vandecappelle
2015-09-19 13:57 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55EEFF8A.3050704@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.