From: Quentin Schulz <foss+yocto@0leil.net>
To: bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org, Quentin Schulz <quentin.schulz@cherry.de>
Subject: [PATCH v2 1/2] doc: bitbake-user-manual-metadata: promote inherit_defer directive to subsection
Date: Fri, 27 Feb 2026 12:30:15 +0100 [thread overview]
Message-ID: <20260227-shell-invalid-v2-1-df5cec5718bd@cherry.de> (raw)
In-Reply-To: <20260227-shell-invalid-v2-0-df5cec5718bd@cherry.de>
From: Quentin Schulz <quentin.schulz@cherry.de>
Out of all the directives listed in this document, only inherit_defer is
documented in a subsubsection rather than in a subsection.
Therefore, let's be consistent and make inherit_defer documentation into
a subsection.
Fixes: eb10df5a9619 ("doc: bitbake-user-manual: document inherit_defer")
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
index 18f293f4b..1b7941335 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
@@ -813,7 +813,7 @@ evaluated at the end of parsing.
.. _ref-bitbake-user-manual-metadata-inherit-defer:
``inherit_defer`` Directive
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
+---------------------------
The :ref:`inherit_defer <ref-bitbake-user-manual-metadata-inherit-defer>`
directive works like the :ref:`inherit
--
2.53.0
next prev parent reply other threads:[~2026-02-27 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 11:30 [PATCH v2 0/2] doc: bitbake-user-manual-metadata: list known limitations for shell task Quentin Schulz
2026-02-27 11:30 ` Quentin Schulz [this message]
2026-02-27 11:30 ` [PATCH v2 2/2] doc: bitbake-user-manual-metadata: list known limitations for shell tasks Quentin Schulz
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=20260227-shell-invalid-v2-1-df5cec5718bd@cherry.de \
--to=foss+yocto@0leil.net \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
/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