From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
BELOUARGA Mohamed <m.belouarga@technologyandstrategy.com>
Subject: [nanbield][PATCH 09/11] ref-manual: add documentation of the variable SPDX_NAMESPACE_PREFIX
Date: Mon, 25 Mar 2024 14:29:24 +0100 [thread overview]
Message-ID: <20240325132926.3018186-10-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20240325132926.3018186-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 8af233004f..7ae61ad0ff 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7925,6 +7925,11 @@ system and gives an overview of their function and contents.
image), compared to just using the :ref:`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:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 13:29 [nanbield][PATCH 00/11] documentation backports michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 01/11] manuals: add initial stylechecks with Vale michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 02/11] profile-manual: usage.rst: formatting fixes michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 03/11] manuals: use "manual page(s)" michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 04/11] profile-manual: usage.rst: fix reference to bug report michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 05/11] documentation: Makefile: remove releases.rst in "make clean" michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 06/11] migration-guides: add release notes for 4.0.17 michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 07/11] contributor-guide: be more specific about meta-* trees michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 08/11] profile-manual: usage.rst: further style improvements michael.opdenacker
2024-03-25 13:29 ` michael.opdenacker [this message]
2024-03-25 13:29 ` [nanbield][PATCH 10/11] sdk-manual: correctly describe separate build-sysroots tasks in direct sdk workflows michael.opdenacker
2024-03-25 13:29 ` [nanbield][PATCH 11/11] 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=20240325132926.3018186-10-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.