From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] vim: Upgrade 9.0.0242 -> 9.0.0341
Date: Wed, 31 Aug 2022 17:21:18 +0100 [thread overview]
Message-ID: <bf42031e0112176dc1efea54df994161f2e554b3.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8T_Cntva5-+YXX7Dzhf2YJNOyPkbbEYWWZAmHUm4g3xA@mail.gmail.com>
On Wed, 2022-08-31 at 18:17 +0200, Alexander Kanavin wrote:
> I have to wonder, what is really going on there? :-) This never ending
> stream of CVEs makes vim formally the most insecure item in core. Does
> anyone know?
Personally I suspect some kind of bug bounty system may be influencing
things. I have wondered about removing vim from core.
Cheers,
Richard
next prev parent reply other threads:[~2022-08-31 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 16:07 [PATCH] vim: Upgrade 9.0.0242 -> 9.0.0341 Richard Purdie
2022-08-31 16:17 ` [OE-core] " Alexander Kanavin
2022-08-31 16:20 ` Pavel Zhukov
2022-08-31 16:21 ` Richard Purdie [this message]
2022-08-31 16:30 ` Alexander Kanavin
2022-08-31 16:40 ` Khem Raj
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=bf42031e0112176dc1efea54df994161f2e554b3.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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