Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Nick Clifton <nickc@redhat.com>
Cc: gdb-patches@sourceware.org,  binutils@sourceware.org
Subject: Re: RFC: Any objections to rebasing the zlib sources to 1.3.1 ?
Date: Thu, 31 Jul 2025 14:36:23 +0100	[thread overview]
Message-ID: <87cy9g32js.fsf@gentoo.org> (raw)
In-Reply-To: <bf1a25b8-95cd-4813-9c69-680a49d19565@redhat.com>

Nick Clifton <nickc@redhat.com> writes:

> Hi Sam,

Hi Nick,

>
>> I have it ready to go already. It's been approved on the GCC side, I
>> just can't push it yet because of a hook issue. My plan is once it's
>> pushed there to sync it in the binutils-gdb tree.
>
> Perfect - thanks very much.

No problem. I've just landed the gcc side, so I'll commit this side
shortly.

>
> Cheers
>   Nick

thanks,
sam

      reply	other threads:[~2025-07-31 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31 12:17 Nick Clifton
2025-07-31 12:31 ` Sam James
2025-07-31 13:00   ` Nick Clifton
2025-07-31 13:36     ` Sam James [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=87cy9g32js.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@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