From: "Yu, Mingli" <mingli.yu@windriver.com>
To: David Partain <david.partain@est.tech>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"peter.marko@siemens.com" <peter.marko@siemens.com>,
"yoann.congal@smile.fr" <yoann.congal@smile.fr>
Cc: Randy MacLeod <randy.macleod@windriver.com>,
"Chen, Qi" <Qi.Chen@windriver.com>
Subject: Re: [OE-core][PATCH] vim: upgrade 9.1.2144 -> 9.2.0
Date: Wed, 22 Apr 2026 14:37:22 +0800 [thread overview]
Message-ID: <c97339dc-7e9b-4e49-9df8-8df32d4fa5e3@windriver.com> (raw)
In-Reply-To: <17678281463335733ecacbfc29bedd53164414d2.camel@est.tech>
The number of the vim CVEs in 2026 has reached 15 so far [1], and may
still be growing. Could we keep upgrading vim to resolve the vim CVEs
for LTS branch maintenance as we have done in the past?
[1] https://github.com/vim/vim/security
Thanks,
On 3/3/26 18:23, David Partain 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, 2026-02-24 at 16:45 +0000, Peter Marko via lists.openembedded.org wrote:
>> Alternatively, we could also continue updating vim in LTS like we did in the
>> past.
>> For now, there are two active CVEs in LTS releases.
>> Please let me know if I need to backport patches now or if vim upgrade would
>> be accepted.
>
> Greetings,
>
> I've found it quite useful in the past that vim simply gets updated to the
> latest, even in the LTS branch we use. Keeping up with vim CVEs is painful
> otherwise. As such, I would prefer to keep doing things as they have been done
> in the past.
>
> Cheers,
>
> David
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#232302): https://lists.openembedded.org/g/openembedded-core/message/232302
> Mute This Topic: https://lists.openembedded.org/mt/117978611/3618448
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [mingli.yu@eng.windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2026-04-22 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18973B8A1D1BE087.558139@lists.openembedded.org>
2026-02-24 16:45 ` [OE-core][PATCH] vim: upgrade 9.1.2144 -> 9.2.0 Marko, Peter
2026-02-24 17:18 ` Alexander Kanavin
2026-02-24 17:52 ` Marko, Peter
2026-02-26 22:44 ` Yoann Congal
2026-03-03 10:23 ` David Partain
2026-04-22 6:37 ` Yu, Mingli [this message]
2026-04-22 9:53 ` Alexander Kanavin
2026-02-24 16:27 Peter Marko
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=c97339dc-7e9b-4e49-9df8-8df32d4fa5e3@windriver.com \
--to=mingli.yu@windriver.com \
--cc=Qi.Chen@windriver.com \
--cc=david.partain@est.tech \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--cc=randy.macleod@windriver.com \
--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