From: Pavel Machek <pavel@ucw.cz>
To: SeongJae Park <sjpark@amazon.com>
Cc: akpm@linux-foundation.org, apw@canonical.com, joe@perches.com,
colin.king@canonical.com, sj38.park@gmail.com,
linux-kernel@vger.kernel.org, SeongJae Park <sjpark@amazon.de>
Subject: Re: [PATCH v3 0/2] Recommend blocklist/allowlist instead of blacklist/whitelist
Date: Sun, 14 Jun 2020 23:15:19 +0200 [thread overview]
Message-ID: <20200614211519.GA24529@amd> (raw)
In-Reply-To: <20200610065223.29894-1-sjpark@amazon.com>
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
On Wed 2020-06-10 08:52:21, SeongJae Park wrote:
> From: SeongJae Park <sjpark@amazon.de>
>
> This patchset 1) adds support of deprecated terms in the 'checkpatch.pl'
> and 2) set the 'blacklist' and 'whitelist' as deprecated with
> replacement suggestion of 'blocklist' and 'allowlist', because the
> suggestions are incontrovertible, doesn't make people hurt, and more
> self-explanatory.
I don't think this is good idea.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2020-06-14 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 6:52 [PATCH v3 0/2] Recommend blocklist/allowlist instead of blacklist/whitelist SeongJae Park
2020-06-10 6:52 ` [PATCH v3 1/2] checkpatch: support deprecated terms checking SeongJae Park
2020-06-10 7:13 ` Joe Perches
2020-06-10 8:01 ` SeongJae Park
2020-06-10 8:45 ` Joe Perches
2020-06-10 9:09 ` SeongJae Park
2020-06-10 6:52 ` [PATCH v3 2/2] scripts/deprecated_terms: Recommend blocklist/allowlist instead of blacklist/whitelist SeongJae Park
2020-06-10 13:54 ` SeongJae Park
2020-06-10 7:06 ` [PATCH v3 0/2] " Joe Perches
2020-06-14 21:15 ` Pavel Machek [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=20200614211519.GA24529@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=colin.king@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.de \
/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