From: David Partain <david.partain@est.tech>
To: "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>
Subject: Re: [OE-core][PATCH] vim: upgrade 9.1.2144 -> 9.2.0
Date: Tue, 3 Mar 2026 10:23:18 +0000 [thread overview]
Message-ID: <17678281463335733ecacbfc29bedd53164414d2.camel@est.tech> (raw)
In-Reply-To: <AS1PR10MB56978C6748852F61C4F7109BFD74A@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
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
next prev parent reply other threads:[~2026-03-03 10:23 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 [this message]
2026-04-22 6:37 ` Yu, Mingli
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=17678281463335733ecacbfc29bedd53164414d2.camel@est.tech \
--to=david.partain@est.tech \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.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