Alexander Kanavin <alex.kana...@gmail.com> 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. > > I'm not taking a stand here, but just providing the context for where > the push for avoidance of 'abort' comes from: > https://inclusivenaming.org/word-lists/tier-1/ > > Keep in mind that for non-native english speakers none of these words > are emotionally charged; they're just terms.
Yes; these are terms. But it should be possible to understand the meaning of these terms without using a special "inclusivenaming" dictionary. Else, we could just use "A", "B" and "C" for the actions above and explain these "terms" in some documentation later. >> > 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. > > I'd say the context should make it clear that they are lists It is bad when a context is required to understand the meaning of a variable. And where do you see a context when local.conf contains | BB_HASHCONFIG_IGNORE_VARS = "true" Enrico
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#161365): https://lists.openembedded.org/g/openembedded-core/message/161365 Mute This Topic: https://lists.openembedded.org/mt/88906624/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
