From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/11] package: remove trailing whitespace
Date: Thu, 6 Apr 2017 22:45:40 +0200 [thread overview]
Message-ID: <20170406224540.33d0f056@free-electrons.com> (raw)
In-Reply-To: <20170404225019.27916-1-ricardo.martincoski@gmail.com>
Hello,
On Tue, 4 Apr 2017 19:50:09 -0300, Ricardo Martincoski wrote:
> Occurrences were searched using [1]:
> check-package --include-only TrailingSpace $(find * -type f)
> and manually removed.
>
> [1] http://patchwork.ozlabs.org/patch/729666/
>
> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
> ---
> build-tested with:
> $ echo BR2_GOOGLE_BREAKPAD_ENABLE=y > host-google-breakpad.config
> $ support/scripts/test-pkg -c host-google-breakpad.config \
> -d /home/builds/test-pkg -p host-google-breakpad
> 49 builds, 29 skipped, 0 failed
> ---
> package/google-breakpad/google-breakpad.mk | 2 +-
> package/leafnode2/leafnode2.mk | 2 +-
> package/mbedtls/Config.in | 2 +-
> package/protobuf/Config.in | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
I've applied patches 1 to 10, but left patch 11 unapplied for now. I'll
reply to patch 11 to explain why.
Thanks a lot for doing this great cleanup series, much appreciated!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-04-06 20:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 22:50 [Buildroot] [PATCH 01/11] package: remove trailing whitespace Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 02/11] package: remove empty line at end of file Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 03/11] package: remove consecutive empty lines Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 04/11] package: normalize separator size to 80 Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 05/11] package: add missing empty line after header Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 06/11] package: remove trailing backslash Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 07/11] python-pylibftdi: check hash Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 08/11] python-pylibftdi: use package name for .mk file Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 09/11] tesseract-ocr: fix typo in variable name Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 10/11] gst1-plugins-base: remove legacy freetype handling Ricardo Martincoski
2017-04-04 22:50 ` [Buildroot] [PATCH 11/11] gst-plugins-base: fix handling of freetype Ricardo Martincoski
2017-04-06 20:46 ` Thomas Petazzoni
2017-04-11 22:59 ` [Buildroot] [PATCH v2] " Ricardo Martincoski
2017-04-12 12:41 ` Arnout Vandecappelle
2017-04-12 19:06 ` Thomas Petazzoni
2017-04-24 19:20 ` Peter Korsgaard
2017-04-06 20:45 ` 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=20170406224540.33d0f056@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