mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: SeongJae Park <sjpark@amazon.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: SeongJae Park <sjpark@amazon.com>, <akpm@linux-foundation.org>,
	<colin.king@canonical.com>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>, SeongJae Park <sjpark@amazon.de>
Subject: Re: Re: [PATCH v2] scripts/spelling: Recommend blocklist/allowlist instead of blacklist/whitelist
Date: Wed, 10 Jun 2020 11:16:55 +0200	[thread overview]
Message-ID: <20200610091655.4682-1-sjpark@amazon.com> (raw)
In-Reply-To: <b16e47c9-db60-4d20-6e72-bf0b5ab29a38@suse.cz> (raw)

On Wed, 10 Jun 2020 10:50:24 +0200 Jiri Slaby <jslaby@suse.cz> wrote:

> On 09. 06. 20, 14:25, 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.
> 
> Sorry, but no, it's definitely not.
> 
> > 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
> 
> Blocklist means a list of blocks here.

How about 'denylist', then?

> 
> >  boardcast||broadcast
> >  borad||board
> >  boundry||boundary
> > @@ -1495,6 +1496,7 @@ whcih||which
> >  whenver||whenever
> >  wheter||whether
> >  whe||when
> > +whitelist||allowlist
> 
> Wut? allowlist I am seeing for the 1st time.

Wouldn't it easy to infer the intention, though?

> 
> Some purists, linguists, and politicians are true fellows at times, or
> at least they think so. This comes in waves and even if they try hard,
> people won't adopt their nonsense. Like we, Czechs, still call piano by
> German Klavier, and not břinkoklapka, suggested in 19th century (among
> many others) by the horny extremists.
> 
> Shall we stop using black, white, blue, and other colors only because
> they relate to skin color of avatars now? I doubt that.

Well, I have no strong opinion on this, but... if some people are really being
hurt by use of some terms and we could avoid spread of the term with only
little cost, I believe it's worth to make the change.


Thanks,
SeongJae Park

> 
> thanks,
> -- 
> js
> suse labs

      reply	other threads:[~2020-06-10  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09 12:25 SeongJae Park
2020-06-09 12:56 ` Greg KH
2020-06-09 13:05   ` SeongJae Park
2020-06-10  1:35 ` Joe Perches
2020-06-10  5:33   ` SeongJae Park
2020-06-10  8:50 ` Jiri Slaby
2020-06-10  9:16   ` SeongJae Park [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=20200610091655.4682-1-sjpark@amazon.com \
    --to=sjpark@amazon.com \
    --cc=akpm@linux-foundation.org \
    --cc=colin.king@canonical.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®