From: Joe Perches <joe@perches.com>
To: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
sj38.park@gmail.com, mpe@ellerman.id.au, jslaby@suse.cz,
colin.king@canonical.com, sjpark@amazon.de,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: + scripts-deprecated_terms-recommend-denylist-allowlist-instead-of-blacklist-whitelist.patch added to -mm tree
Date: Wed, 17 Jun 2020 22:52:18 -0700 [thread overview]
Message-ID: <5dc6fb7ebfd1d38079d63e54d6fb2b05fa69001a.camel@perches.com> (raw)
In-Reply-To: <20200617213222.OcDiV%akpm@linux-foundation.org>
On Wed, 2020-06-17 at 14:32 -0700, akpm@linux-foundation.org wrote:
> The patch titled
> Subject: scripts/deprecated_terms: recommend denylist/allowlist instead of blacklist/whitelist
> has been added to the -mm tree. Its filename is
> scripts-deprecated_terms-recommend-denylist-allowlist-instead-of-blacklist-whitelist.patch
[]
> ------------------------------------------------------
> From: SeongJae Park <sjpark@amazon.de>
> Subject: scripts/deprecated_terms: recommend denylist/allowlist instead of blacklist/whitelist
>
> This commit recommends that patches replace 'blacklist' and 'whitelist'
> with 'denylist' and 'allowlist', because the new suggestions are
> incontrovertible, doesn't make people hurt, and are more self-explanatory.
[]
> --- a/scripts/deprecated_terms.txt~scripts-deprecated_terms-recommend-denylist-allowlist-instead-of-blacklist-whitelist
> +++ a/scripts/deprecated_terms.txt
> @@ -3,3 +3,5 @@
> # The format of each line is:
> # deprecated||suggested
> #
> +blacklist||denylist
> +whitelist||allowlist
I think this is a poor use of deprecated terms
as it has nothing to do with skin color.
parent reply other threads:[~2020-06-18 5:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200617213222.OcDiV%akpm@linux-foundation.org>]
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=5dc6fb7ebfd1d38079d63e54d6fb2b05fa69001a.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=sj38.park@gmail.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
all inboxes | Powered by JetHome®