From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] docs/website: contribute.txt update with useful tips on patch versioning and patch submission
Date: Sat, 19 Sep 2015 15:57:52 +0200 [thread overview]
Message-ID: <20150919155752.01f7a2d5@free-electrons.com> (raw)
In-Reply-To: <1441727239-17284-1-git-send-email-francesco.nwokeka@gmail.com>
Dear Francesco Nwokeka,
On Tue, 8 Sep 2015 17:47:19 +0200, 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
> v2 -> v3: Replaced "the patchwork website" with a link to the project website
Applied after doing some minor tweaks (commit title too long, and minor
rewording about in-reply-to).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-09-19 13:57 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
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 [this message]
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=20150919155752.01f7a2d5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.