From: Tom Tromey <tom@tromey.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, binutils@sourceware.org
Subject: Re: [PATCH 3/3] Add minimal thread-safety to BFD
Date: Fri, 03 Nov 2023 17:10:11 -0600 [thread overview]
Message-ID: <87il6itovg.fsf@tromey.com> (raw)
In-Reply-To: <96ed72c6-1d4b-4db6-b7bf-5e4a2f224453@redhat.com> (Nick Clifton's message of "Thu, 2 Nov 2023 12:14:20 +0000")
>> Let me know what you'd prefer.
Nick> Be safe, be paranoid, and let the client decide whether their code can or
Nick> cannot fail.
Alright. I'll send v2 shortly.
I didn't check in the 2 patches you approved since I felt they didn't
really make sense in isolation.
Tom
next prev parent reply other threads:[~2023-11-03 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 19:07 [PATCH 0/3] Threads and BFD Tom Tromey
2023-10-26 19:07 ` [PATCH 1/3] Make _bfd_error_buf static Tom Tromey
2023-11-01 12:27 ` Nick Clifton
2023-10-26 19:07 ` [PATCH 2/3] Make various error-related globals thread-local Tom Tromey
2023-11-01 12:28 ` Nick Clifton
2023-10-26 19:07 ` [PATCH 3/3] Add minimal thread-safety to BFD Tom Tromey
2023-11-01 12:45 ` Nick Clifton
2023-11-01 20:08 ` Tom Tromey
2023-11-01 20:48 ` Tom Tromey
2023-11-02 12:14 ` Nick Clifton
2023-11-03 23:10 ` Tom Tromey [this message]
2023-11-01 12:26 ` [PATCH 0/3] Threads and BFD 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=87il6itovg.fsf@tromey.com \
--to=tom@tromey.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).