* [PATCH v2] doc: migration-3.5: variable changes for inclusive language
[not found] <16DCEA2573357EC0.11325@lists.yoctoproject.org>
@ 2022-03-17 9:20 ` Michael Opdenacker
0 siblings, 0 replies; only message in thread
From: Michael Opdenacker @ 2022-03-17 9:20 UTC (permalink / raw)
To: docs; +Cc: Michael Opdenacker
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/migration-guides/migration-3.5.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/documentation/migration-guides/migration-3.5.rst b/documentation/migration-guides/migration-3.5.rst
index da09b6f449..6d452a6edf 100644
--- a/documentation/migration-guides/migration-3.5.rst
+++ b/documentation/migration-guides/migration-3.5.rst
@@ -7,6 +7,16 @@ Project 3.5 Release (codename "kirkstone") from the prior release.
Recipe changes
--------------
+- To use more `inclusive language <https://inclusivenaming.org/>`__
+ in the code and documentation, some variables have been renamed or even
+ deleted. BitBake will stop with an error when renamed or removed variables
+ still exist in your recipes or configuration.
+
+ A :oe_git:`convert-variable-renames.py
+ </openembedded-core/tree/scripts/contrib/convert-variable-renames.py>`
+ script is provided to convert your recipes and configuration,
+ and also warns you about the use of problematic words.
+
- Because of the uncertainty in future default branch names in git repositories,
it is now required to add a branch name to all URLs described
by ``git://`` and ``gitsm://`` :term:`SRC_URI` entries. For example::
--
2.25.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2022-03-17 9:20 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <16DCEA2573357EC0.11325@lists.yoctoproject.org>
2022-03-17 9:20 ` [PATCH v2] doc: migration-3.5: variable changes for inclusive language Michael Opdenacker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox