From: Joe Perches <joe@perches.com>
To: SeongJae Park <sjpark@amazon.com>, akpm@linux-foundation.org
Cc: colin.king@canonical.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, SeongJae Park <sjpark@amazon.de>
Subject: Re: [PATCH v2] scripts/spelling: Recommend blocklist/allowlist instead of blacklist/whitelist
Date: Tue, 09 Jun 2020 18:35:46 -0700 [thread overview]
Message-ID: <d086a1a412de3079cefbfb15f38c4dc9aae0045d.camel@perches.com> (raw)
In-Reply-To: <20200609122549.26304-1-sjpark@amazon.com>
On Tue, 2020-06-09 at 14:25 +0200, SeongJae Park wrote:
> From: SeongJae Park <sjpark@amazon.de>
>
> This commit recommends the patches to replace 'blacklist' and
> 'whitelist' with the 'blocklist' and 'allowlist', because the new
> suggestions are incontrovertible, doesn't make people hurt, and more
> self-explanatory.
nack. Spelling is for typos not for politics.
> Signed-off-by: SeongJae Park <sjpark@amazon.de>
> ---
> scripts/spelling.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/scripts/spelling.txt b/scripts/spelling.txt
> index d9cd24cf0d40..ea785568d8b8 100644
> --- a/scripts/spelling.txt
> +++ b/scripts/spelling.txt
> @@ -230,6 +230,7 @@ beter||better
> betweeen||between
> bianries||binaries
> bitmast||bitmask
> +blacklist||blocklist
> boardcast||broadcast
> borad||board
> boundry||boundary
> @@ -1495,6 +1496,7 @@ whcih||which
> whenver||whenever
> wheter||whether
> whe||when
> +whitelist||allowlist
> wierd||weird
> wiil||will
> wirte||write
next prev parent reply other threads:[~2020-06-10 1:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 12:25 [PATCH v2] scripts/spelling: Recommend blocklist/allowlist instead of blacklist/whitelist SeongJae Park
2020-06-09 12:56 ` Greg KH
2020-06-09 13:05 ` SeongJae Park
2020-06-10 1:35 ` Joe Perches [this message]
2020-06-10 5:33 ` SeongJae Park
2020-06-10 8:50 ` Jiri Slaby
2020-06-10 9:16 ` SeongJae Park
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=d086a1a412de3079cefbfb15f38c4dc9aae0045d.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.de \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).