public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	Andreas Schwab <schwab@linux-m68k.org>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org,
	Alan Modra <amodra@gmail.com>,
	Joseph Myers <joseph@codesourcery.com>,
	Simon Marchi <simon.marchi@ericsson.com>
Subject: Re: [PATCH 3/4] zlib: Sync with GCC
Date: Mon, 18 Jun 2018 09:37:00 -0000	[thread overview]
Message-ID: <86f2e9be-cd92-6ebf-2dbc-2dd10b138013@redhat.com> (raw)
In-Reply-To: <31f1ea31-17e7-0734-cbff-4b369b5201b5@polymtl.ca>

Hi Simon,

>> Looks like commit 93df7317ee has never been copied to gcc.
> 
> Ah I see, so my patch is partly going in the wrong direction then.
> Can somebody from gcc copy that change over there?

I have submitted a request to apply the patch to the gcc sources:

  https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01028.html


> Here's the patch without that change.

This version is approved - please apply.

Cheers
  Nick

  reply	other threads:[~2018-06-18  9:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-16  3:08 [PATCH 0/4] Sync a few directories " Simon Marchi
2018-06-16  3:07 ` [PATCH 2/4] libiberty: Sync " Simon Marchi
2018-06-18  9:25   ` Nick Clifton
2018-06-16  3:08 ` [PATCH 4/4] libdecnumber: " Simon Marchi
2018-06-18  9:38   ` Nick Clifton
2018-06-16  3:08 ` [PATCH 3/4] zlib: " Simon Marchi
2018-06-16  7:28   ` Andreas Schwab
2018-06-16 11:34     ` Simon Marchi
2018-06-18  9:37       ` Nick Clifton [this message]
2018-06-16  3:27 ` [PATCH 1/4] config: " Simon Marchi
2018-06-18  9:23   ` Nick Clifton
2018-06-17  0:50 ` [PATCH 5/4] configure.ac: " Simon Marchi
2018-06-18  9:39   ` Nick Clifton
2018-06-18 13:40 ` [PATCH 0/4] Sync a few directories " Simon Marchi

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=86f2e9be-cd92-6ebf-2dbc-2dd10b138013@redhat.com \
    --to=nickc@redhat.com \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.com \
    --cc=schwab@linux-m68k.org \
    --cc=simon.marchi@ericsson.com \
    --cc=simon.marchi@polymtl.ca \
    /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).