From: <Mikko.Rapeli@bmw.de>
To: <ross@burtonini.com>
Cc: <jdmason@kudzu.us>, <yocto@lists.yoctoproject.org>,
<openembedded-core@lists.openembedded.org>,
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] Inclusive Language Proposal for YP/OE
Date: Wed, 26 Jan 2022 08:37:05 +0000 [thread overview]
Message-ID: <YfEIMKst5Mfp8tPN@korppu> (raw)
In-Reply-To: <CAAnfSTu1eneGztK0Kmzcv5Qq89kodoCrgDWzF6JQ7eFStD6Uzg@mail.gmail.com>
Hi,
On Tue, Jan 25, 2022 at 04:30:40PM +0000, Ross Burton wrote:
> On Mon, 24 Jan 2022 at 16:18, Jon Mason <jdmason@kudzu.us> wrote:
> > CVE_CHECK_PN_WHITELIST -> CVE_CHECK_SKIPRECIPE
> > CVE_CHECK_WHITELIST -> CVE_CHECK_IGNORECVE
>
> This is the only one that sticks out to me. I think it needs another
> _, SKIP_RECIPE and IGNORE_CVE.
Please don't include CVE twice in the variable name, that's was annoying and just
got used to the CVE_CHECK_WHITELIST one. CVE_CHECK_IGNORE would do.
Cheers,
-Mikko
> Other than that, +1.
>
> Will we have a bit of logic to detect the obsolete names being set and
> emit warnings/errors?
>
> Ross
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#95071): https://lists.openembedded.org/g/openembedded-devel/message/95071
> Mute This Topic: https://lists.openembedded.org/mt/88650129/3616751
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [mikko.rapeli@bmw.de]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2022-01-26 8:37 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 [this message]
2022-01-25 23:07 ` [OE-core] " Randy MacLeod
2022-01-29 3:30 ` [oe] " Peter Kjellerstedt
2022-02-04 13:21 ` [OE-core] " Enrico Scholz
2022-02-04 13:58 ` [oe] " 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=YfEIMKst5Mfp8tPN@korppu \
--to=mikko.rapeli@bmw.de \
--cc=jdmason@kudzu.us \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ross@burtonini.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox