public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [kirkstone][PATCH 10/10] dev-manual: licenses: update license manifest location
Date: Wed, 20 Sep 2023 10:15:44 +0200	[thread overview]
Message-ID: <20230920081544.1226760-11-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230920081544.1226760-1-michael.opdenacker@bootlin.com>

From: Michael Opdenacker <michael.opdenacker@bootlin.com>

- Fix broken markup (wasn't displaying properly)
- Update the path to the directory containing license information
  (this change applies to the kirkstone branch)
- Fix typo later in the document

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
 documentation/dev-manual/licenses.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/documentation/dev-manual/licenses.rst b/documentation/dev-manual/licenses.rst
index 15e5c7396a..419af7c326 100644
--- a/documentation/dev-manual/licenses.rst
+++ b/documentation/dev-manual/licenses.rst
@@ -326,7 +326,8 @@ completeness.
 .. note::
 
    The Yocto Project generates a license manifest during image creation
-   that is located in ``${DEPLOY_DIR}/licenses/``\ `image_name`\ ``-``\ `datestamp`
+   that is located in
+   ``${DEPLOY_DIR}/licenses/<image-name>-<machine>.rootfs-<datestamp>/``
    to assist with any audits.
 
 Providing the Source Code
@@ -444,7 +445,7 @@ with source as defined by the GPL and other open source licenses.
 Providing Compilation Scripts and Source Code Modifications
 -----------------------------------------------------------
 
-At this point, we have addressed all we need to prior to generating the
+At this point, we have addressed all we need prior to generating the
 image. The next two requirements are addressed during the final
 packaging of the release.
 
-- 
2.34.1



      parent reply	other threads:[~2023-09-20  8:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20  8:15 [kirkstone][PATCH 00/10] kirkstone backports michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 01/10] sdk-manual: extensible.rst: align with master branch michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 02/10] dev-manual: disk-space: improve wording for obsolete sstate cache files michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 03/10] documentation/README: align with master michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 04/10] dev-manual: new-recipe.rst fix inconsistency with contributor guide michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 05/10] contributor-guide: recipe-style-guide: add Upstream-Status michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 06/10] dev-manual: licenses: mention SPDX for license compliance michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 07/10] template: fix typo in section header michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 08/10] ref-manual: qa-checks: align with master michael.opdenacker
2023-09-20  8:15 ` [kirkstone][PATCH 09/10] manuals: document "mime-xdg" class and MIME_XDG_PACKAGES michael.opdenacker
2023-09-20  8:15 ` michael.opdenacker [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=20230920081544.1226760-11-michael.opdenacker@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    /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