From: Hongxu Jia <hongxu.jia@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/3] vte: 0.82.2 -> 0.83.90
Date: Wed, 11 Feb 2026 10:23:25 +0800 [thread overview]
Message-ID: <a2f62f5b-6c1e-4aae-ab4c-1d14905df6f7@windriver.com> (raw)
In-Reply-To: <CANNYZj8-pjs91R-TiLUo22nZ+bWAyN-P084AmAUPuyY-GY1mQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On 2/10/26 17:54, Alexander Kanavin wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> On Tue, 10 Feb 2026 at 10:50, hongxu via lists.openembedded.org
> <hongxu.jia=windriver.com@lists.openembedded.org> wrote:
>> .../vte/{vte_0.82.2.bb => vte_0.83.90.bb} | 4 +-
> 0.83.90 is a pre-release, we should wait for 0.84
>
> Unfortunately gnome release schedule always is just a bit too late for
> yocto releases, and typically there's no time to test and merge
> version updates. Can the backport be added to existing recipe?
OK, let's wait for 0.84.
The backport is not necessary for 0.82.2, it was introduced in 0.83.90
and fixed in development branch (master)
//Hongxu
> Alex
[-- Attachment #2: Type: text/html, Size: 1691 bytes --]
prev parent reply other threads:[~2026-02-11 2:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 9:50 [PATCH 1/3] vte: 0.82.2 -> 0.83.90 Hongxu Jia
2026-02-10 9:50 ` [PATCH 2/3] dpkg: 1.22.21 -> 1.23.5 Hongxu Jia
2026-02-10 9:50 ` [PATCH 3/3] gnupg: 2.5.14 -> 2.5.17 Hongxu Jia
2026-02-10 10:00 ` Patchtest results for " patchtest
2026-02-10 10:36 ` [OE-core] " Marko, Peter
2026-02-10 10:40 ` Yoann Congal
2026-02-11 2:43 ` [PATCH v2] " Hongxu Jia
2026-02-11 2:35 ` [OE-core] Patchtest results for [PATCH 3/3] " Hongxu Jia
2026-02-10 9:54 ` [OE-core] [PATCH 1/3] vte: 0.82.2 -> 0.83.90 Alexander Kanavin
2026-02-11 2:23 ` Hongxu Jia [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=a2f62f5b-6c1e-4aae-ab4c-1d14905df6f7@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=alex.kanavin@gmail.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