Yocto Project Documentation
 help / color / mirror / Atom feed
From: Antonin Godard <antonin.godard@bootlin.com>
To: yoann.congal@smile.fr
Cc: docs@lists.yoctoproject.org, Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [docs] [PATCH v2 0/4] Document my team's commits for 5.1
Date: Tue, 1 Oct 2024 11:25:06 +0200	[thread overview]
Message-ID: <d6bbd990-3dfa-4236-8010-5f87a8492acc@bootlin.com> (raw)
In-Reply-To: <20240927220033.3941455-1-yoann.congal@smile.fr>

Hi Yoann,

On 28/09/2024 00:00, Yoann Congal via lists.yoctoproject.org wrote:
> This series should cover theses patches:
> 61186bc98a5 (oeqa/selftest: Only rewrite envvars paths that absolutely point to builddir, 2024-09-10)
> a19bb8c1d51 (spirv-tools: Update merged patch to backport status, 2024-09-05)
> c01e633ab91 (python3-libarchive-c: add ptest, 2024-08-02)
> 47ed8ac83a6 (spirv-tools: Fix git-describe related reproducibility, 2024-08-03)
> d85a10e4985 (insane: skip unimplemented-ptest checks if disabled, 2024-07-10)
> c45d45422d6 (Revert "insane: skip unimplemented-ptest on S=WORKDIR recipes", 2024-07-09)
> 0df9d22928c (recipe style guide: add recommendation for patches without signature, 2024-06-06)
> 8fc967d0c7d (migration-5.1: add the recommended pattern for S/UNPACKDIR definition, 2024-05-28)
> 268dfbd9491 (Revert "oeqa/selftest/devtool: fix test_devtool_add_git_style2", 2024-04-26)
> 3c05286fa10 (oeqa/selftest/devtool: fix _test_devtool_add_git_url, 2024-04-26)
> 
> (Not every commit was documentation worthy)
> 
> v1->v2: Reviews from Quentin Schulz, thanks!
> 
> Yoann Congal (4):
>    migration/release-notes-5.1: document oeqa/selftest envvars change
>    release-notes-5.1: document added python3-libarchive-c ptest
>    release-notes-5.1: document fixed _test_devtool_add_git_url test
>    release-notes-5.1: document spirv-tools reproducibility
> 
>   documentation/migration-guides/migration-5.1.rst  | 15 +++++++++++++++
>   .../migration-guides/release-notes-5.1.rst        |  8 ++++++++
>   2 files changed, 23 insertions(+)

Thank you for these patches, I am ok by this version of the series too! 
Quentin can also review your v2 if he has time to.

Reviewed-by: Antonin Godard <antonin.godard@bootlin.com>

Cheers,
Antonin


      parent reply	other threads:[~2024-10-01  9:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 22:00 [PATCH v2 0/4] Document my team's commits for 5.1 Yoann Congal
2024-09-27 22:00 ` [PATCH v2 1/4] migration/release-notes-5.1: document oeqa/selftest envvars change Yoann Congal
2024-10-01  9:40   ` [docs] " Quentin Schulz
2024-10-01 10:09     ` Antonin Godard
2024-10-01 10:20       ` Quentin Schulz
2024-10-01 10:30         ` Antonin Godard
2024-10-02  8:57     ` Yoann Congal
2024-10-02  9:35       ` Quentin Schulz
2024-10-03 12:23         ` Improvement of the oeqa/selftest environment variable rewrite change Yoann Congal
2024-09-27 22:00 ` [PATCH v2 2/4] release-notes-5.1: document added python3-libarchive-c ptest Yoann Congal
2024-09-27 22:00 ` [PATCH v2 3/4] release-notes-5.1: document fixed _test_devtool_add_git_url test Yoann Congal
2024-09-27 22:00 ` [PATCH v2 4/4] release-notes-5.1: document spirv-tools reproducibility Yoann Congal
2024-10-01  9:41   ` [docs] " Quentin Schulz
2024-10-01  9:25 ` Antonin Godard [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=d6bbd990-3dfa-4236-8010-5f87a8492acc@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=yoann.congal@smile.fr \
    /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