Yocto Project Documentation
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: michael.opdenacker@rootcommit.com, ross.burton@arm.com,
	paul.eggleton@microsoft.com
Subject: Re: [docs] [PATCH 08/16] ref-manual: add missing image manifest variables
Date: Wed, 09 Oct 2024 15:56:55 +0000 (UTC)	[thread overview]
Message-ID: <80980048-ae8a-4cb8-a85f-9dc79caaae71@rootcommit.com> (raw)
In-Reply-To: <20241009074120.866786-9-antonin.godard@bootlin.com>

Hi Antonin

Just a quick nitpick!

On 10/9/24 09:41, Antonin Godard via lists.yoctoproject.org wrote:
> From: Antonin Godard <antonin.godard@bootlin.com>
>
> New variables that control the output of the image task manifests.=
>   
> +   :term:`IMGMANIFESTDIR`
> +      When inheriting the :ref:`ref-classes-image` class directly or through the
> +      :ref:`ref-classes-core-image` class, the :term:`IMGMANIFESTDIR` points to
s/points/setting points/
Cheers
Michael.

-- 
Michael Opdenacker
Root Commit
https://rootcommit.com



  reply	other threads:[~2024-10-09 15:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  7:40 [PATCH 00/16] Updates for styhead antonin.godard
2024-10-09  7:40 ` [PATCH 01/16] ref-manual: add missing CVE_CHECK manifest variables antonin.godard
2024-10-09 15:50   ` [docs] " Michael Opdenacker
2024-10-09  7:41 ` [PATCH 02/16] ref-manual: add new vex class antonin.godard
2024-10-09  7:41 ` [PATCH 03/16] ref-manual: add new retain class and variables antonin.godard
2024-10-09  7:41 ` [PATCH 04/16] ref-manual: add missing nospdx class antonin.godard
2024-10-09  7:41 ` [PATCH 05/16] ref-manual: add new RECIPE_UPGRADE_EXTRA_TASKS variable antonin.godard
2024-10-09  7:41 ` [PATCH 06/16] ref-manual: drop siteconfig class antonin.godard
2024-10-09  7:41 ` [PATCH 07/16] ref-manual: add missing TESTIMAGE_FAILED_QA_ARTIFACTS antonin.godard
2024-10-09  7:41 ` [PATCH 08/16] ref-manual: add missing image manifest variables antonin.godard
2024-10-09 15:56   ` Michael Opdenacker [this message]
2024-10-09  7:41 ` [PATCH 09/16] ref-manual: add missing EXTERNAL_KERNEL_DEVICETREE variable antonin.godard
2024-10-09  7:41 ` [PATCH 10/16] ref-manual: drop TCLIBCAPPEND variable antonin.godard
2024-10-09  7:41 ` [PATCH 11/16] ref-manual: add missing OPKGBUILDCMD variable antonin.godard
2024-10-09 15:58   ` [docs] " Michael Opdenacker
2024-10-09  7:41 ` [PATCH 12/16] ref-manual: add missing variable PRSERVER_UPSTREAM antonin.godard
2024-10-09 14:28   ` [docs] " Michael Opdenacker
2024-10-09 14:39     ` Antonin Godard
2024-10-09  7:41 ` [PATCH 13/16] ref-manual: merge patch-status-* to patch-status antonin.godard
2024-10-09 16:02   ` [docs] " Michael Opdenacker
2024-10-09  7:41 ` [PATCH 14/16] ref-manual: add mission pep517-backend sanity check antonin.godard
2024-10-09  7:41 ` [PATCH 15/16] release-notes-5.1: update for several section antonin.godard
2024-10-09 16:18   ` [docs] " Michael Opdenacker
2024-10-10  9:12     ` Antonin Godard
2024-10-09  7:41 ` [PATCH 16/16] release-notes-5.1: update release note for styhead antonin.godard
2024-10-09 12:53   ` [docs] " Richard Purdie
2024-10-09 14:33     ` Antonin Godard
2024-10-09 14:41       ` Richard Purdie
2024-10-09 16:26   ` 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=80980048-ae8a-4cb8-a85f-9dc79caaae71@rootcommit.com \
    --to=michael.opdenacker@rootcommit.com \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=paul.eggleton@microsoft.com \
    --cc=ross.burton@arm.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