From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] docs/manual/contribute.txt: add formatting patches section
Date: Wed, 24 Feb 2016 00:08:03 +0100 [thread overview]
Message-ID: <20160224000803.3c13a1b9@free-electrons.com> (raw)
In-Reply-To: <1454348717-4711-5-git-send-email-arnout@mind.be>
Dear Arnout Vandecappelle (Essensium/Mind),
On Mon, 1 Feb 2016 18:45:17 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> Thomas P. has sent a few big feedback mails recently that explain how a
> patch should be formatted. Indeed, this was not explained much in the
> manual, so add a section that explains how patches should be formatted.
> This is based heavily on the feedback that Thomas P. gave. Also,
> specific examples for new packages and version bumps are added.
>
> This will allow us to refer to
> https://buildroot.org/manual.html#submitting-patches
> in the future instead of composing long mails.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> docs/manual/contribute.txt | 81 ++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 81 insertions(+)
Applied to master, thanks. Same as PATCH 3/4 in terms of formatting,
I've changed it back to our normal practice.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-02-23 23:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 17:45 [Buildroot] [PATCH 0/4] docs: improve submitting patches Arnout Vandecappelle
2016-02-01 17:45 ` [Buildroot] [PATCH 1/4] README: add reference to submitting-patches Arnout Vandecappelle
2016-02-01 18:20 ` Thomas Petazzoni
2016-02-01 17:45 ` [Buildroot] [PATCH 2/4] website: add reference to submitting-patches to Contribute tab Arnout Vandecappelle
2016-02-01 18:20 ` Thomas Petazzoni
2016-02-01 17:45 ` [Buildroot] [PATCH 3/4] docs/manual/contribute.txt: add section for preparing patch series Arnout Vandecappelle
2016-02-22 14:23 ` Yegor Yefremov
2016-02-23 23:07 ` Thomas Petazzoni
2016-02-01 17:45 ` [Buildroot] [PATCH 4/4] docs/manual/contribute.txt: add formatting patches section Arnout Vandecappelle
2016-02-08 10:48 ` Yegor Yefremov
2016-02-08 14:33 ` Arnout Vandecappelle
2016-02-22 14:24 ` Yegor Yefremov
2016-02-23 23:08 ` 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=20160224000803.3c13a1b9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox