From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] docs/manual/contribute.txt: add section for preparing patch series
Date: Wed, 24 Feb 2016 00:07:47 +0100 [thread overview]
Message-ID: <20160224000747.1e558ce8@free-electrons.com> (raw)
In-Reply-To: <1454348717-4711-4-git-send-email-arnout@mind.be>
Dear Arnout Vandecappelle (Essensium/Mind),
On Mon, 1 Feb 2016 18:45:16 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> In subsequent patches, we will add more explanation about how to
> prepare patches, so it will be worthwhile to have a separate section
> for the series preparation.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> Note: for this patch, I started using
> http://dustycloud.org/blog/vcs-friendly-patchable-document-line-wrapping/
> If nobody opposes, I propose to require this formatting for the manual
> from now on. It will be weird for a while, but in the end I think it
> would be A Good Thing (TM). If that formatting had been followed, this
> patch, for example, would have a diffstat of +3 instead of the current
> +7-4.
> ---
> docs/manual/contribute.txt | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
Applied to master, after rewrapping to our normal standards, as
discussed on IRC. I don't really like the proposed new formatting (but
I can get convinced), but mainly I didn't like the fact that it was
only applied to one part of the manual.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-23 23:07 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 [this message]
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
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=20160224000747.1e558ce8@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.