From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <stondo@gmail.com>, <docs@lists.yoctoproject.org>
Cc: <stefano.tondo.ext@siemens.com>
Subject: Re: [docs] [PATCH v3 1/1] ref-manual/dev-manual: document new SPDX variables and capabilities
Date: Thu, 26 Mar 2026 09:28:05 +0100 [thread overview]
Message-ID: <DHCKLP69J7YE.1Y7HHPEXU80KI@bootlin.com> (raw)
In-Reply-To: <20260323133143.1185958-2-stefano.tondo.ext@siemens.com>
Hi,
Thanks, merged on master-next with the following syntax fixes:
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index f0a0d1646..e1da9f630 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -9271,11 +9271,11 @@ system and gives an overview of their function and contents.
The value of this variable is the base prefix used to look up the
agent's details. The following sub-variables are read using that prefix:
- - ``<PREFIX>_name``: display name of the supplier (required)
- - ``<PREFIX>_type``: agent type: ``organization``, ``person``,
- ``software``, or ``agent`` (optional, defaults to ``agent``)
- - ``<PREFIX>_comment``: free-text comment (optional)
- - ``<PREFIX>_id_email``: contact e-mail address (optional)
+ - ``<PREFIX>_name``: display name of the supplier (required)
+ - ``<PREFIX>_type``: agent type: ``organization``, ``person``,
+ ``software``, or ``agent`` (optional, defaults to ``agent``)
+ - ``<PREFIX>_comment``: free-text comment (optional)
+ - ``<PREFIX>_id_email``: contact e-mail address (optional)
The simplest approach is to use the variable itself as its own prefix,
so the sub-variable names follow directly from
@@ -9428,8 +9428,8 @@ system and gives an overview of their function and contents.
The sub-variables follow the same agent prefix convention as
:term:`SPDX_IMAGE_SUPPLIER`:
- - ``SPDX_INVOKED_BY_name``: display name of the invoking agent
- - ``SPDX_INVOKED_BY_type``: agent type, such as ``software`` for a CI system
+ - ``SPDX_INVOKED_BY_name``: display name of the invoking agent
+ - ``SPDX_INVOKED_BY_type``: agent type, such as ``software`` for a CI system
Example (CI pipeline invoking the build)::
@@ -9483,8 +9483,8 @@ system and gives an overview of their function and contents.
The sub-variables follow the same agent prefix convention as
:term:`SPDX_IMAGE_SUPPLIER`:
- - ``SPDX_ON_BEHALF_OF_name``: display name of the commissioning agent
- - ``SPDX_ON_BEHALF_OF_type``: agent type, such as ``organization``
+ - ``SPDX_ON_BEHALF_OF_name``: display name of the commissioning agent
+ - ``SPDX_ON_BEHALF_OF_type``: agent type, such as ``organization``
Example (CI system building on behalf of a customer organization)::
Antonin
prev parent reply other threads:[~2026-03-26 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:31 [PATCH v3 0/1] ref-manual/dev-manual: document new SPDX variables and capabilities Stefano Tondo
2026-03-23 13:31 ` [PATCH v3 1/1] " Stefano Tondo
2026-03-26 8:28 ` 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=DHCKLP69J7YE.1Y7HHPEXU80KI@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=stefano.tondo.ext@siemens.com \
--cc=stondo@gmail.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