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, thomas.petazonni@bootlin.com
Subject: Re: [docs] [PATCH 13/16] ref-manual: merge patch-status-* to patch-status
Date: Wed, 09 Oct 2024 16:02:31 +0000 (UTC) [thread overview]
Message-ID: <72682ba8-dba3-4708-b7d8-98f4f9c4edde@rootcommit.com> (raw)
In-Reply-To: <20241009074120.866786-14-antonin.godard@bootlin.com>
Hi Antonin
On 10/9/24 09:41, Antonin Godard via lists.yoctoproject.org wrote:
> From: Antonin Godard <antonin.godard@bootlin.com>
>
> These are not distinct anymore and check for any patches in any layer.
>
> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
> ---
> documentation/ref-manual/classes.rst | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
> index 121887d1f..0fce37cfa 100644
> --- a/documentation/ref-manual/classes.rst
> +++ b/documentation/ref-manual/classes.rst
> @@ -1461,12 +1461,8 @@ The tests you can list with the :term:`WARN_QA` and
> - ``patch-fuzz:`` Checks for fuzz in patch files that may allow
> them to apply incorrectly if the underlying code changes.
>
> -- ``patch-status-core:`` Checks that the Upstream-Status is specified
> - and valid in the headers of patches for recipes in the OE-Core layer.
> -
> -- ``patch-status-noncore:`` Checks that the Upstream-Status is specified
> - and valid in the headers of patches for recipes in layers other than
> - OE-Core.
> +- ``patch-status:`` Checks that the Upstream-Status is specified and valid in
> + the headers of patches for recipes.
Not your fault here, but an opportunity to write:
Checks that the ``Upstream-Status`` value is specified...
Cheers
Michael.
--
Michael Opdenacker
Root Commit
https://rootcommit.com
next prev parent reply other threads:[~2024-10-09 16:02 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 ` [docs] " Michael Opdenacker
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 ` Michael Opdenacker [this message]
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=72682ba8-dba3-4708-b7d8-98f4f9c4edde@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 \
--cc=thomas.petazonni@bootlin.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