From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/scripts: drop xorg-release script
Date: Fri, 27 Apr 2018 22:50:45 +0200 [thread overview]
Message-ID: <20180427225045.68c9983c@windsurf> (raw)
In-Reply-To: <20180425192402.12995-1-thomas.petazzoni@bootlin.com>
Hello,
On Wed, 25 Apr 2018 21:24:02 +0200, Thomas Petazzoni wrote:
> This script causes a large number of flake8 warnings, is rarely used
> (but even never used), and is going to be replaced at some point by
> the improved pkg-stats that will give details about the upstream
> version available for all packages, not just X.org packages.
>
> Therefore, let's drop the xorg-release script in order to silence all
> those flake8 warnings:
>
> support/scripts/xorg-release:36:1: E302 expected 2 blank lines, found 1
> support/scripts/xorg-release:58:27: E201 whitespace after '{'
> support/scripts/xorg-release:58:44: E203 whitespace before ':'
> support/scripts/xorg-release:58:54: E202 whitespace before '}'
> support/scripts/xorg-release:63:1: E305 expected 2 blank lines after class or function definition, found 1
> support/scripts/xorg-release:64:15: E261 at least two spaces before inline comment
> support/scripts/xorg-release:67:32: E261 at least two spaces before inline comment
> support/scripts/xorg-release:86:1: E302 expected 2 blank lines, found 1
> support/scripts/xorg-release:95:1: E302 expected 2 blank lines, found 1
> support/scripts/xorg-release:107:1: E302 expected 2 blank lines, found 1
> support/scripts/xorg-release:115:20: W601 .has_key() is deprecated, use 'in'
> support/scripts/xorg-release:123:34: E201 whitespace after '{'
> support/scripts/xorg-release:124:46: E203 whitespace before ':'
> support/scripts/xorg-release:124:50: E202 whitespace before '}'
> support/scripts/xorg-release:127:1: E302 expected 2 blank lines, found 1
> support/scripts/xorg-release:141:15: W601 .has_key() is deprecated, use 'in'
> support/scripts/xorg-release:146:21: W601 .has_key() is deprecated, use 'in'
> support/scripts/xorg-release:176:1: E305 expected 2 blank lines after class or function definition, found 1
> support/scripts/xorg-release:180:1: W391 blank line at end of file
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> ---
> support/scripts/xorg-release | 180 -------------------------------------------
> 1 file changed, 180 deletions(-)
> delete mode 100755 support/scripts/xorg-release
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-04-27 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 19:24 [Buildroot] [PATCH] support/scripts: drop xorg-release script Thomas Petazzoni
2018-04-25 19:34 ` Bernd Kuhls
2018-04-25 21:02 ` Ricardo Martincoski
2018-04-27 20:50 ` 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=20180427225045.68c9983c@windsurf \
--to=thomas.petazzoni@bootlin.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.