From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: remove version 2.21
Date: Mon, 29 Feb 2016 22:57:45 +0100 [thread overview]
Message-ID: <20160229225745.36f4eba4@free-electrons.com> (raw)
In-Reply-To: <1456142845-5372-2-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Mon, 22 Feb 2016 09:07:25 -0300, Gustavo Zacarias wrote:
> Mask out glibc for sparc as well since it's no longer available.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/glibc/2.21/0001-fix-CVE-2015-7547.patch | 236 ------------------------
> package/glibc/2.21/0002-fix-CVE-2015-1781.patch | 32 ----
> package/glibc/2.21/0003-fix-CVE-2014-8121.patch | 176 ------------------
> package/glibc/Config.in | 4 -
> package/glibc/glibc.hash | 1 -
> toolchain/toolchain-buildroot/Config.in | 5 +-
> 6 files changed, 2 insertions(+), 452 deletions(-)
> delete mode 100644 package/glibc/2.21/0001-fix-CVE-2015-7547.patch
> delete mode 100644 package/glibc/2.21/0002-fix-CVE-2015-1781.patch
> delete mode 100644 package/glibc/2.21/0003-fix-CVE-2014-8121.patch
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-29 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 12:07 [Buildroot] [PATCH v2] glibc: remove version 2.21 Gustavo Zacarias
2016-02-22 12:07 ` [Buildroot] [PATCH] " Gustavo Zacarias
2016-02-22 12:20 ` Thomas Petazzoni
2016-02-22 12:25 ` Gustavo Zacarias
2016-02-22 12:33 ` Thomas Petazzoni
2016-02-22 12:40 ` Gustavo Zacarias
2016-02-29 21:57 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 11:15 Gustavo Zacarias
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=20160229225745.36f4eba4@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 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.