All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: "Jon Mason" <jdmason@kudzu.us>
Cc: yocto@lists.yoctoproject.org,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] Inclusive Language Proposal for YP/OE
Date: Fri, 04 Feb 2022 14:21:15 +0100	[thread overview]
Message-ID: <lyiltukbsk.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CAPoiz9wL16OTzxNHdw_5-L72GOHkhhM0--WZF7An071cx6sr_A@mail.gmail.com> (Jon Mason's message of "Mon, 24 Jan 2022 11:17:58 -0500")

"Jon Mason" <jdmason@kudzu.us> writes:

> For BB_DISKMON_DIRS, the actions "ABORT, STOPTASKS and WARN" would
> become "HALT, NO_NEW_TASKS and "WARN".

I am not an native english speaker, but for "HALT" I will have to think
twice whether it will pause the operation or abort it.  I would stay at
"ABORT" because it makes much more clear what happens.


> BB_HASHCONFIG_WHITELIST -> BB_HASHCONFIG_IGNORE_VARS
> BB_SETSCENE_ENFORCE_WHITELIST -> BB_SETSCENE_ENFORCE_IGNORE_TASKS
> BB_HASHBASE_WHITELIST -> BB_BASEHASH_IGNORE_VARS
> MULTI_PROVIDER_WHITELIST -> BB_MULTI_PROVIDER_ALLOWED

The new variable names sound like boolean flags, not like lists.


> SSTATE_DUPWHITELIST -> SSTATE_ALLOW_OVERLAP_FILES
> CVE_CHECK_PN_WHITELIST -> CVE_CHECK_SKIPRECIPE
> CVE_CHECK_WHITELIST -> CVE_CHECK_IGNORECVE
> SYSROOT_DIRS_BLACKLIST -> SYSROOT_DIRS_IGNORE
> LICENSE_FLAGS_WHITELIST -> LICENSE_FLAGS_ACCEPTED
> UNKNOWN_CONFIGURE_WHITELIST -> UNKNOWN_CONFIGURE_OPT_IGNORE
> SDK_LOCAL_CONF_BLACKLIST -> ESDK_LOCALCONF_REMOVE
> SDK_LOCAL_CONF_WHITELIST -> ESDK_LOCALCONF_ALLOW
> SDK_INHERIT_BLACKLIST -> ESDK_CLASS_INHERIT_DISABLE

ditto; sounds like flags but not like lists


Enrico


  parent reply	other threads:[~2022-02-04 13:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 16:17 Inclusive Language Proposal for YP/OE Jon Mason
2022-01-25  8:26 ` Paul Barker
2022-01-26  1:51   ` [yocto] " Paul Eggleton
2022-01-25 15:50 ` [OE-core] " Chuck Wolber
2022-01-25 16:00   ` [oe] " Ross Burton
2022-01-25 16:47   ` Richard Purdie
2022-01-25 16:30 ` [oe] " Ross Burton
2022-01-26  8:37   ` Mikko.Rapeli
2022-01-25 23:07 ` [OE-core] " Randy MacLeod
2022-01-29  3:30 ` [oe] " Peter Kjellerstedt
2022-02-04 13:21 ` Enrico Scholz [this message]
2022-02-04 13:58   ` [oe] [OE-core] " Alexander Kanavin
2022-02-04 14:16     ` Enrico Scholz
2022-02-04 15:01       ` Bryan Evenson
2022-02-04 18:38         ` Enrico Scholz
2022-02-04 19:12           ` Alexander Kanavin
2022-02-04 20:08             ` Enrico Scholz
2022-02-21  8:21 ` [oe] " Marta Rybczynska

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=lyiltukbsk.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --cc=jdmason@kudzu.us \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=yocto@lists.yoctoproject.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 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.