From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/4] fix help text wrapping for configs b
Date: Thu, 11 May 2017 23:34:07 +0200 [thread overview]
Message-ID: <20170511233407.0645ecbd@free-electrons.com> (raw)
In-Reply-To: <20170505140808.17696-2-aduskett@codeblue.com>
Hello,
On Fri, 5 May 2017 10:08:06 -0400, Adam Duskett wrote:
> The check-package script when ran gives warnings on text wrapping
> on all of these Config files. This patch cleans up all warnings
> related to the text wrapping for the Config files starting with
> the letter b in the package directory.
>
> The appropriate indentation is: <tab><2 spaces><62 chars>
> See http://nightly.buildroot.org/#writing-rules-config-in for more
> information.
>
> Signed-off-by: Adam Duskett <aduskett@codeblue.com>
> ---
> v1 -> v2:
> - Added patch to series.
I've also applied patches 2, 3 and 4 to our next branch.
Besides the commit title, please also review your patches for trailing
white spaces. Your patches were adding a few of them here and there.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-11 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 14:08 [Buildroot] [PATCH v2 1/4] fix help text wrapping for configs a Adam Duskett
2017-05-05 14:08 ` [Buildroot] [PATCH v2 2/4] fix help text wrapping for configs b Adam Duskett
2017-05-11 21:34 ` Thomas Petazzoni [this message]
2017-05-05 14:08 ` [Buildroot] [PATCH v2 3/4] fix help text wrapping for configs c Adam Duskett
2017-05-05 14:08 ` [Buildroot] [PATCH v2 4/4] fix help text wrapping for configs d Adam Duskett
2017-05-11 21:26 ` [Buildroot] [PATCH v2 1/4] fix help text wrapping for configs a 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=20170511233407.0645ecbd@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