From: Jeff Law <law@redhat.com>
To: Matthias Klose <doko@ubuntu.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Cc: gdb-patches@sourceware.org, binutils <binutils@sourceware.org>
Subject: Re: [patch] update zlib to the 1.2.10 release.
Date: Thu, 12 Jan 2017 21:39:00 -0000 [thread overview]
Message-ID: <b8cf51e3-067e-e630-daab-935507633275@redhat.com> (raw)
In-Reply-To: <ef0a09d9-8d24-0440-92f1-1822f6ec7e06@ubuntu.com>
On 01/12/2017 02:26 PM, Matthias Klose wrote:
> On 12.01.2017 22:17, Jeff Law wrote:
>> On 01/05/2017 07:45 AM, Matthias Klose wrote:
>>> These are the changes updating zlib from 1.2.8 to 1.2.10. It is only used when
>>> building without a system zlib. The new release includes fixes for security
>>> issues CVE-2016-9840, CVE-2016-9841, CVE-2016-9842, CVE-2016-9843.
>>>
>>> Checked with a build with disabled system-zlib. Ok for the trunk?
>> Were there any changes that we needed to carry forward or any changes you needed
>> to make to the upstream sources?
>
> I backed out the changes to the configure* and Makefile* changes (and only
> these), which are completely different to zlib upstream. There are no
> additions/deletions to zlib source files, so these build changes still work with
> the updated zlib.
One more note. I think that, in general, backing out local changes
which don't have a strong need to be carried forward is absolutely the
right thing to do. The less hacking we do on these libraries we pull
from other sources, the better, IMHO.
jeff
next prev parent reply other threads:[~2017-01-12 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 14:45 Matthias Klose
2017-01-12 21:17 ` Jeff Law
2017-01-12 21:27 ` Matthias Klose
2017-01-12 21:38 ` Jeff Law
2017-01-12 21:39 ` Jeff Law [this message]
2017-01-13 12:14 ` Matthias Klose
2017-01-22 18:01 ` Matthias Klose
2017-01-22 18:12 ` NightStrike
2017-01-22 18:42 ` Matthias Klose
2017-01-23 22:57 ` Iain Buclaw
2017-01-23 4:09 ` Joel Brobecker
2017-01-23 9:10 ` Matthias Klose
2017-01-23 16:01 ` Nick Clifton
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=b8cf51e3-067e-e630-daab-935507633275@redhat.com \
--to=law@redhat.com \
--cc=binutils@sourceware.org \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).