From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
BELOUARGA Mohamed <m.belouarga@technologyandstrategy.com>
Subject: [kirkstone][PATCH 8/9] ref-manual: add documentation of the variable SPDX_NAMESPACE_PREFIX
Date: Mon, 25 Mar 2024 14:27:36 +0100 [thread overview]
Message-ID: <20240325132737.3018073-9-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20240325132737.3018073-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: BELOUARGA Mohamed <m.belouarga@technologyandstrategy.com>
The documentation of the variable SPDX_NAMESPACE_PREFIX does not exist.
This variable is used to change the prefix of some links in SPDX docs.
Signed-off-by: BELOUARGA Mohamed <m.belouarga@technologyandstrategy.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/variables.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index aa1d5f393d..5e5b688878 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7521,6 +7521,11 @@ system and gives an overview of their function and contents.
image), compared to just using the
:ref:`create-spdx <ref-classes-create-spdx>` class with no option.
+ :term:`SPDX_NAMESPACE_PREFIX`
+ This option could be used in order to change the prefix of ``spdxDocument``
+ and the prefix of ``documentNamespace``. It is set by default to
+ ``http://spdx.org/spdxdoc``.
+
:term:`SPDX_PRETTY`
This option makes the SPDX output more human-readable, using
identation and newlines, instead of the default output in a
--
2.34.1
next prev parent reply other threads:[~2024-03-25 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 13:27 [kirkstone][PATCH 0/9] documentation backports michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 1/9] manuals: add initial stylechecks with Vale michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 2/9] profile-manual: usage.rst: formatting fixes michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 3/9] manuals: use "manual page(s)" michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 4/9] profile-manual: usage.rst: fix reference to bug report michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 5/9] migration-guides: add release notes for 4.0.17 michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 6/9] contributor-guide: be more specific about meta-* trees michael.opdenacker
2024-03-25 13:27 ` [kirkstone][PATCH 7/9] profile-manual: usage.rst: further style improvements michael.opdenacker
2024-03-25 13:27 ` michael.opdenacker [this message]
2024-03-25 13:27 ` [kirkstone][PATCH 9/9] dev-manual: improve descriptions of 'bitbake -S printdiff' 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=20240325132737.3018073-9-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=m.belouarga@technologyandstrategy.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