From: Quentin Schulz <quentin.schulz@cherry.de>
To: Dawid Bijak <bijak.dawid@gmail.com>,
bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org, richard.purdie@linuxfoundation.org
Subject: Re: [PATCH v2 3/4] doc: bitbake-user-manual-metadata: explain inherit_defer example
Date: Thu, 7 May 2026 15:56:32 +0200 [thread overview]
Message-ID: <a3a8a5c5-81c3-4764-aba6-32c84ce55a7e@cherry.de> (raw)
In-Reply-To: <20260501091418.76994-4-bijak.dawid@gmail.com>
Hi Dawid,
On 5/1/26 11:14 AM, Dawid Bijak wrote:
> Add a short paragraph describing how the inherit_defer makes use of override
> syntax to achieve conditional inheritance, and rename VARIABLE to
> VARNAME so the example uses the same identifier as the preceding
> code block.
>
Can you please instead rename VARNAME in inherit_defer to VARIABLE to
match the rest of the file?
Otherwise, looks good.
Cheers,
Quentin
next prev parent reply other threads:[~2026-05-07 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 9:14 [PATCH v2 0/4] doc: bitbake-user-manual-metadata: clarify inherit_defer documentation Dawid Bijak
2026-05-01 9:14 ` [PATCH v2 1/4] doc: bitbake-user-manual-metadata: remove incorrect claim Dawid Bijak
2026-05-07 13:48 ` Quentin Schulz
2026-05-07 19:04 ` Dawid Bijak
2026-05-01 9:14 ` [PATCH v2 2/4] doc: bitbake-user-manual-metadata: remove invalid anonymous Python example Dawid Bijak
2026-05-07 13:52 ` Quentin Schulz
2026-05-01 9:14 ` [PATCH v2 3/4] doc: bitbake-user-manual-metadata: explain inherit_defer example Dawid Bijak
2026-05-07 13:56 ` Quentin Schulz [this message]
2026-05-01 9:14 ` [PATCH v2 4/4] doc: bitbake-user-manual-metadata: move inline python examples to inherit section Dawid Bijak
2026-05-07 14:05 ` 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=a3a8a5c5-81c3-4764-aba6-32c84ce55a7e@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=bijak.dawid@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox