From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/1] gnu: vim: Fix CVE-2017-5953.
Date: Tue, 14 Feb 2017 14:28:07 -0500 [thread overview]
Message-ID: <20170214192807.GB8462@jasmine> (raw)
In-Reply-To: <87y3x8spzd.fsf@gnu.org>
On Tue, Feb 14, 2017 at 05:21:10PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
>
> > * gnu/packages/patches/vim-CVE-2017-5953.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Add it.
> > * gnu/packages/vim.scm (vim)[source]: Use it.
I corrected the upstream mistake and pushed as
1ae04e35111f1455134943ee098f39e55aebc3eb.
I expect there will be a further upstream update to this fix.
prev parent reply other threads:[~2017-02-14 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 22:33 [PATCH 0/1] Vim CVE-2017-5953 Leo Famulari
2017-02-13 22:33 ` [PATCH 1/1] gnu: vim: Fix CVE-2017-5953 Leo Famulari
2017-02-14 16:21 ` Ludovic Courtès
2017-02-14 19:28 ` Leo Famulari [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170214192807.GB8462@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).