From: Paul Eggleton <bluelightning@bluelightning.org>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com>,
docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 9/9] release-notes: additional features and one known issue for 5.0
Date: Thu, 18 Apr 2024 07:50:53 -0700 [thread overview]
Message-ID: <67767a97a85d5232f3e7f50c869fc7c2@bluelightning.org> (raw)
In-Reply-To: <269d718f-5d81-4ef4-865c-036f4215fc08@bootlin.com>
On 15.04.2024 08:22, Michael Opdenacker wrote:
> On 4/15/24 at 10:06, Quentin Schulz wrote:
>> I think there's a way to link to the bitbake doc for inherit
>> directive.
>>
>> Maybe something like:
>>
>> """
>> :ref:`inherit
>> <bitbake:bitbake-user-manual/bitbake-user-manual-metadata:\`\`inherit\`\`
>> directive>`
>> """
>>
>> would work? Just a suggestion though.
>
>
> It works! I made the change.
>
>>
>>> + it is only evaluated at the end of parsing - recommended where
>>> a conditional
>>> + expression is used, e.g.
>>> +
>>
>> I think we're missing a double colon here to make this a code snippet?
>>
>> """
>> expression is used, e.g.::
>> """
Thanks to you both, I added this late and didn't even think about
linking to the BitBake manual - perfect!
Cheers
Paul
next prev parent reply other threads:[~2024-04-18 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 20:43 [PATCH 0/9] Updates for the 5.0 release Paul Eggleton
2024-04-14 20:43 ` [PATCH 1/9] ref-manual: Add virtual-slash QA check Paul Eggleton
2024-04-14 20:43 ` [PATCH 2/9] ref-manual: add new python classes Paul Eggleton
2024-04-15 13:43 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 3/9] classes: cve_check: add note about remote patches Paul Eggleton
2024-04-14 20:43 ` [PATCH 4/9] variables: add TARGET_DBGSRC_DIR Paul Eggleton
2024-04-14 20:43 ` [PATCH 5/9] dev-manual: update reference to sstate-cache-management script Paul Eggleton
2024-04-14 20:43 ` [PATCH 6/9] dev-manual: update custom distribution section Paul Eggleton
2024-04-15 14:04 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 7/9] release-notes: Add CVEs, recipe upgrades and contributors for 5.0 Paul Eggleton
2024-04-15 14:24 ` Michael Opdenacker
2024-04-18 14:47 ` [docs] " Paul Eggleton
2024-04-18 15:26 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 8/9] migration: Extend migration guide " Paul Eggleton
2024-04-15 14:41 ` Michael Opdenacker
2024-04-14 20:43 ` [PATCH 9/9] release-notes: additional features and one known issue " Paul Eggleton
2024-04-15 8:06 ` [docs] " Quentin Schulz
2024-04-15 15:22 ` Michael Opdenacker
2024-04-18 14:50 ` Paul Eggleton [this message]
2024-04-15 15:41 ` Michael Opdenacker
2024-04-15 15:43 ` [PATCH 0/9] Updates for the 5.0 release Michael Opdenacker
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=67767a97a85d5232f3e7f50c869fc7c2@bluelightning.org \
--to=bluelightning@bluelightning.org \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@bootlin.com \
--cc=quentin.schulz@theobroma-systems.com \
/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