From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [PATCH v2] doc: migration-3.5: variable changes for inclusive language
Date: Thu, 17 Mar 2022 10:20:06 +0100 [thread overview]
Message-ID: <20220317092007.223297-1-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <16DCEA2573357EC0.11325@lists.yoctoproject.org>
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
parent reply other threads:[~2022-03-17 9:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <16DCEA2573357EC0.11325@lists.yoctoproject.org>]
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=20220317092007.223297-1-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@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.