From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] php: security bump to version 7.0.12
Date: Fri, 14 Oct 2016 09:26:55 +0200 [thread overview]
Message-ID: <20161014092655.452324f3@free-electrons.com> (raw)
In-Reply-To: <1476398366-29332-1-git-send-email-gustavo@zacarias.com.ar>
Hello,
On Thu, 13 Oct 2016 19:39:26 -0300, Gustavo Zacarias wrote:
> See http://www.php.net/ChangeLog-7.php#7.0.12 since there are no CVEs
> out yet.
>
> And drop upstream patch.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> ...pt-enclose-phpdbg_load_module_or_extensio.patch | 47 ----------------------
> package/php/php.hash | 2 +-
> package/php/php.mk | 2 +-
> 3 files changed, 2 insertions(+), 49 deletions(-)
> delete mode 100644 package/php/0007-phpdbg_prompt-enclose-phpdbg_load_module_or_extensio.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-14 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 22:39 [Buildroot] [PATCH] php: security bump to version 7.0.12 Gustavo Zacarias
2016-10-14 7:26 ` Thomas Petazzoni [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=20161014092655.452324f3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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