mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-02 18:32:15 +02:00
Code Issues Packages Projects Releases Wiki Activity

make the documentation a bit more inclusive

Browse Source 
Except the name of variables which can't be changed only in the
documentation for obvious reasons and workflow or developement
explanations around the use of the "master" branch which cannot be
replaced with "development" branch instead, most of the non-inclusive
words that appear in https://inclusivenaming.org/word-lists/tier-1/
should have been replaced in this patch.

(From yocto-docs rev: 2755f35060084f7af356091de9dc144f85530fe2)

Signed-off-by: Quentin Schulz <foss+yocto@0leil.net>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Quentin Schulz
2021-12-06 16:04:01 +01:00
committed by Richard Purdie
parent 99474e0d68
commit e71983bc7d
14 changed files with 151 additions and 159 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
documentation/bsp-guide/bsp.rst
View File

@@ -1121,12 +1121,12 @@ list describes them in order of preference:
how to use these variables.
If you build as you normally would, without specifying any recipes in
the :term:`LICENSE_FLAGS_WHITELIST`, the build stops and provides you
with the list of recipes that you have tried to include in the image
that need entries in the :term:`LICENSE_FLAGS_WHITELIST`. Once you enter
the appropriate license flags into the whitelist, restart the build
to continue where it left off. During the build, the prompt will not
appear again since you have satisfied the requirement.
the :term:`LICENSE_FLAGS_WHITELIST` variable, the build stops and provides
you with the list of recipes that you have tried to include in the image
that need entries in the :term:`LICENSE_FLAGS_WHITELIST` variable. Once you
enter the appropriate license flags into it, restart the build to continue
where it left off. During the build, the prompt will not appear again since
you have satisfied the requirement.
Once the appropriate license flags are on the white list in the
:term:`LICENSE_FLAGS_WHITELIST` variable, you can build the encumbered