From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <quentin.schulz@cherry.de>, <docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 4/4] poky.yaml.in: split automatic and manually replaced macros
Date: Thu, 04 Dec 2025 14:21:13 +0100 [thread overview]
Message-ID: <DEPGP4JHATVS.S2YO6LSPCXFP@bootlin.com> (raw)
In-Reply-To: <66616c7a-b998-40ed-912c-c0c1a199b890@cherry.de>
Hi,
On Wed Dec 3, 2025 at 4:04 PM CET, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Antonin,
>
> On 12/2/25 5:14 PM, Antonin Godard via lists.yoctoproject.org wrote:
>> Instead of thinking some of these macros should be replaced when a new
>> release is out, split the variable that should be manually maintained
>> and the ones that are automatically computed in set_versions.py.
>>
>> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
>> ---
>> documentation/poky.yaml.in | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/documentation/poky.yaml.in b/documentation/poky.yaml.in
>> index 810efd4d5..f6d6ea9fc 100644
>> --- a/documentation/poky.yaml.in
>> +++ b/documentation/poky.yaml.in
>> @@ -2,6 +2,12 @@
>> # Macros used in the documentation
>> #
>>
>> +#
>> +# Automatically replaced by set_versions.py, no manual update required
>> +# Values below are placeholders to give an idea on how to use them in the
>> +# documentation.
>> +#
>> +
>> # The DISTRO variable represents the current docs version. It should be used
>> # when referring to the current docs version. See also DISTRO_LATEST_TAG.
>> DISTRO : "5.2"
>> @@ -22,6 +28,11 @@ DISTRO_REL_TAG : "yocto-$DISTRO;"
>> DISTRO_REL_LATEST_TAG : "yocto-&DISTRO_LATEST_TAG;"
>> DOCCONF_VERSION : "dev"
>> BITBAKE_SERIES : ""
>
> DISTRO_REL_TAG and DISTRO_REL_LATEST_TAG aren't actually replaced, so
> should we move them with the unchanged variables below?
Ha, had a bit of hesitation for these ones, it's true they aren't replaced
although I doubt they're subject to change. Will move them anyhow, thanks.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-12-04 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 16:14 [PATCH 0/4] Whinlatter release updates Antonin Godard
2025-12-02 16:14 ` [PATCH 1/4] ref-manual/svg/releases.svg: mark styhead and walnascar EOL Antonin Godard
2025-12-03 14:54 ` [docs] " Quentin Schulz
2025-12-02 16:14 ` [PATCH 2/4] ref-manual/svg/releases.svg: mark whinlatter as current release Antonin Godard
2025-12-03 14:57 ` [docs] " Quentin Schulz
2025-12-04 13:19 ` Antonin Godard
2025-12-02 16:14 ` [PATCH 3/4] set_versions.py: add wrynose as devbranch Antonin Godard
2025-12-03 15:00 ` [docs] " Quentin Schulz
2025-12-04 13:19 ` Antonin Godard
2025-12-02 16:14 ` [PATCH 4/4] poky.yaml.in: split automatic and manually replaced macros Antonin Godard
2025-12-03 15:04 ` [docs] " Quentin Schulz
2025-12-04 13:21 ` Antonin Godard [this message]
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=DEPGP4JHATVS.S2YO6LSPCXFP@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--cc=thomas.petazzoni@bootlin.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