From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [OE-core] [PATCH 6/8] python3-pbr: upgrade 7.1.0 -> 7.1.2
Date: Wed, 26 Aug 2026 10:58:11 +0200 [thread overview]
Message-ID: <DKYR23KHZXH4.15WVJ8FA59H6V@bootlin.com> (raw)
In-Reply-To: <40554eb0fcecd37e5e080fe5b93efcfeafca7843.camel@linuxfoundation.org>
On Wed Aug 26, 2026 at 10:49 AM CEST, Richard Purdie wrote:
> On Wed, 2026-08-26 at 10:33 +0200, Mathieu Dubois-Briand via
> lists.openembedded.org wrote:
>> Changelog:
>>
>> * Fix hook ordering race that drops subpackages from wheels
>
> 7.1.1 in the subject! :)
>
> Cheers,
>
> Richard
Right! I forgot to change title from AUH, I will do so.
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-08-26 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 8:33 [PATCH 0/8] Various upgrades Mathieu Dubois-Briand
2026-08-26 8:33 ` [PATCH 1/8] python3-imagesize: upgrade 2.0.0 -> 2.0.1 Mathieu Dubois-Briand
2026-08-26 11:23 ` Patchtest results for " patchtest
2026-08-26 8:33 ` [PATCH 2/8] libslirp: upgrade 4.9.3 -> 4.9.4 Mathieu Dubois-Briand
2026-08-26 8:33 ` [PATCH 3/8] cmake,cmake-native: upgrade 4.4.2 -> 4.4.3 Mathieu Dubois-Briand
2026-08-26 8:33 ` [PATCH 4/8] python3-cryptography: upgrade 50.0.0 -> 50.0.1 Mathieu Dubois-Briand
2026-08-26 8:33 ` [PATCH 5/8] python3-git: upgrade 3.1.59 -> 3.1.60 Mathieu Dubois-Briand
2026-08-26 8:33 ` [PATCH 6/8] python3-pbr: upgrade 7.1.0 -> 7.1.2 Mathieu Dubois-Briand
2026-08-26 8:49 ` [OE-core] " Richard Purdie
2026-08-26 8:58 ` Mathieu Dubois-Briand [this message]
2026-08-26 8:33 ` [PATCH 7/8] python3-uv-build: upgrade 0.12.5 -> 0.12.6 Mathieu Dubois-Briand
2026-08-26 8:33 ` [PATCH 8/8] man-pages: upgrade 6.18 -> 6.19 Mathieu Dubois-Briand
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=DKYR23KHZXH4.15WVJ8FA59H6V@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=thomas.petazzoni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.