From: belouargamohamed@gmail.com
To: docs@lists.yoctoproject.org
Cc: f.lahoudere@technologyandstrategy.com,
BELOUARGA Mohamed <m.belouarga@technologyandstrategy.com>
Subject: [PATCH] ref-manual: add documentation of the variable SPDX_NAMESPACE_PREFIX
Date: Mon, 18 Mar 2024 20:16:11 +0100 [thread overview]
Message-ID: <20240318191610.37757-1-m.belouarga@technologyandstrategy.com> (raw)
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>
---
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 6e66dc735..3f7c8e2c7 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7911,6 +7911,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.25.1
next reply other threads:[~2024-03-18 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 19:16 belouargamohamed [this message]
2024-03-19 9:18 ` [docs] [PATCH] ref-manual: add documentation of the variable SPDX_NAMESPACE_PREFIX 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=20240318191610.37757-1-m.belouarga@technologyandstrategy.com \
--to=belouargamohamed@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=f.lahoudere@technologyandstrategy.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).