From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <ecordonnier@snap.com>
Cc: <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v4 2/2] opkg: upgrade 0.8.0 -> 0.9.0
Date: Mon, 17 Nov 2025 10:43:13 +0100 [thread overview]
Message-ID: <DEAVEY6WFZQJ.3TEPYDJIZ01P7@bootlin.com> (raw)
In-Reply-To: <CAHUKmYb450p4o1-sE1TsFLUgp1iQn6D1ZAhhsZagb3L5BpeGYA@mail.gmail.com>
On Mon Nov 17, 2025 at 10:26 AM CET, Etienne Cordonnier via lists.openembedded.org wrote:
> Hi,
> what is the status of the patch updating to 0.9.0? I have seen that it is
> not in master-next any more.
>
> Thanks
> Étienne
>
Hi Étienne,
Your patch is still in the queue, but is expected to be merged in master
after whinlatter release, so it is not present in master-next at this
time.
You can see it in my master-next branch:
https://git.openembedded.org/openembedded-core-contrib/log/?h=mathieu/master-next&ofs=50
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-11-17 9:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 13:46 [OE-core][PATCH v4 1/2] opkg: upgrade 0.7.0 -> 0.8.0 ecordonnier
2025-10-23 13:46 ` [OE-core][PATCH v4 2/2] opkg: upgrade 0.8.0 -> 0.9.0 ecordonnier
2025-11-27 17:08 ` Gyorgy Sarvari
2025-11-27 18:10 ` Etienne Cordonnier
2025-12-03 21:04 ` Khem Raj
2025-12-03 21:34 ` Khem Raj
2025-12-04 18:56 ` Etienne Cordonnier
2025-12-05 22:15 ` Etienne Cordonnier
2025-12-05 22:34 ` Khem Raj
2025-12-05 22:36 ` Etienne Cordonnier
2025-12-05 22:55 ` Khem Raj
2025-12-08 23:44 ` Etienne Cordonnier
2025-12-09 0:20 ` Khem Raj
2026-01-09 23:43 ` Ricardo de Araujo (Salveti)
[not found] ` <187122D70EFBB6A8.8642@lists.openembedded.org>
2025-11-17 9:26 ` Etienne Cordonnier
2025-11-17 9:43 ` Mathieu Dubois-Briand [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=DEAVEY6WFZQJ.3TEPYDJIZ01P7@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=ecordonnier@snap.com \
--cc=openembedded-core@lists.openembedded.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