public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 0/3] libctf: error handling improvements
Date: Mon, 31 Aug 2020 23:07:25 +0100	[thread overview]
Message-ID: <87eenmmpuq.fsf@esperi.org.uk> (raw)
In-Reply-To: <cefdc497-ee18-23bd-e8ab-6af8b9c6f823@redhat.com> (Nick Clifton via Binutils's message of "Wed, 26 Aug 2020 10:59:54 +0100")

On 26 Aug 2020, Nick Clifton via Binutils spake thusly:

> Hi Nick,
>
>>> Uh - can you point me at the original patch please ?
>>> (I loose track of these things.  It must be my age).
>> 
>> Sure!
>> 
>> <https://sourceware.org/pipermail/binutils/2020-July/112674.html> and
>
> Thanks - that was exactly what I needed.
>
> Patch series approved - please apply the lot! :-)

(FYI: thank you, pushed. And then forgot to hit send on the email saying
as much and left it languishing unsent for days! sorry.)

      reply	other threads:[~2020-08-31 22:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 19:16 Nick Alcock
2020-07-31 19:16 ` [PATCH 1/3] libctf, binutils: initial work towards libctf gettextization Nick Alcock
2020-07-31 19:16 ` [PATCH 2/3] libctf, binutils, include, ld: gettextize and improve error handling Nick Alcock
2020-07-31 19:16 ` [PATCH 3/3] binutils, ld: dequote libctf error messages Nick Alcock
2020-08-20 15:15 ` [PATCH 0/3] libctf: error handling improvements Nick Alcock
2020-08-21 13:15   ` Nick Clifton
2020-08-25 22:57     ` Nick Alcock
2020-08-26  9:59       ` Nick Clifton
2020-08-31 22:07         ` Nick Alcock [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=87eenmmpuq.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).