From: Leo Famulari <leo@famulari.name>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: Remove pcre-CVE-2016-3191.patch.
Date: Mon, 23 Jan 2017 16:28:15 -0500 [thread overview]
Message-ID: <20170123212815.GA735@jasmine> (raw)
In-Reply-To: <84C459AE-0D37-4300-8399-BCDC6DC0E2C7@flashner.co.il>
On Mon, Jan 23, 2017 at 08:45:26PM +0000, Efraim Flashner wrote:
> On January 23, 2017 10:41:19 PM GMT+02:00, Leo Famulari <leo@famulari.name> wrote:
> >On Mon, Jan 23, 2017 at 08:31:29AM +0000, Efraim Flashner wrote:
> >> efraim pushed a commit to branch core-updates
> >> in repository guix.
> >>
> >> commit 0e88ada940953ac6b12fcbfd2add08835edcf49d
> >> Author: Efraim Flashner <efraim@flashner.co.il>
> >> Date: Mon Jan 23 10:28:15 2017 +0200
> >>
> >> gnu: Remove pcre-CVE-2016-3191.patch.
> >>
> >> This is a follow-up to 026ee1a5a669658c8d4745c2733b4c201ca0e48e.
> >>
> >> * gnu/packages/patches/pcre-CVE-2016-3191.patch: Delete file.
> >> * gnu/local.mk (dist_patch_DATA): Remove it.
> >
> >It's too early for this commit because pcre2 is still using this patch,
> >right?
> >
> >If so, can you revert this change?
>
> I used git grep for the patch name and pcre was the only one using it. On core updates pcre2 has a separate pcre2 patch covering the same cve
Ah, my mistake :) Thanks for the follow-up commit!
prev parent reply other threads:[~2017-01-23 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170123083129.31983.24662@vcs.savannah.gnu.org>
[not found] ` <20170123083129.49CC8220078@vcs.savannah.gnu.org>
2017-01-23 20:41 ` 01/01: gnu: Remove pcre-CVE-2016-3191.patch Leo Famulari
2017-01-23 20:45 ` Efraim Flashner
2017-01-23 21: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170123212815.GA735@jasmine \
--to=leo@famulari.name \
--cc=efraim@flashner.co.il \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.