From: NightStrike <nightstrike@gmail.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>,
gdb-patches@sourceware.org, binutils <binutils@sourceware.org>
Subject: Re: [patch] update zlib to the 1.2.10 release.
Date: Sun, 22 Jan 2017 18:12:00 -0000 [thread overview]
Message-ID: <CAF1jjLuVE3WWVXHWYj+Xbau-h8ohzroTSiSL0iC2BV99PHjGjg@mail.gmail.com> (raw)
In-Reply-To: <5b68833c-cf12-d858-9636-d12c40236dcd@ubuntu.com>
On Sun, Jan 22, 2017 at 1:00 PM, Matthias Klose <doko@ubuntu.com> wrote:
> NightStrike proposed to revert to the 1.2.8 release until zlib stabilizes again;
> I'm open for that, but didn't want to stay with the 1.2.10 release.
I don't recall making that proposal. I thought I just suggested that
since modern zlib now supports having a separate build and source
directory (at least according to the December changelog: "Allow
building zlib outside of the source directory"), you should check to
see if the gcc build system had any hacks to accomplish the same thing
that could now be removed.
next prev parent reply other threads:[~2017-01-22 18:12 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
2017-01-13 12:14 ` Matthias Klose
2017-01-22 18:01 ` Matthias Klose
2017-01-22 18:12 ` NightStrike [this message]
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=CAF1jjLuVE3WWVXHWYj+Xbau-h8ohzroTSiSL0iC2BV99PHjGjg@mail.gmail.com \
--to=nightstrike@gmail.com \
--cc=binutils@sourceware.org \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=law@redhat.com \
/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).