From: Tom Tromey <tom@tromey.com>
To: "Christian Biesinger \(Code Review\)"
<gerrit@gnutoolchain-gerrit.osci.io>
Cc: Christian Biesinger <cbiesinger@google.com>,
gdb-patches@sourceware.org, gnutoolchain-gerrit@osci.io,
Tom Tromey <tromey@sourceware.org>,
Hannes Domani <ssbssa@yahoo.de>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [review v3] Use strerror_r in safe_strerror if available
Date: Fri, 01 Nov 2019 17:10:00 -0000 [thread overview]
Message-ID: <87lfsz34kp.fsf@tromey.com> (raw)
In-Reply-To: <20191101152230.36C67218A2@gnutoolchain-gerrit.osci.io> (Christian Biesinger's message of "Fri, 1 Nov 2019 11:22:30 -0400")
>>>>> "Christian" == Christian Biesinger (Code Review) <gerrit@gnutoolchain-gerrit.osci.io> writes:
>> The windows build now fails, because safe_strerror() of mingw-strerror. […]
Christian> Thanks; tromey has a patch for that at https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/478
I pushed it a little while ago.
Tom
next prev parent reply other threads:[~2019-11-01 17:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 19:44 [review] " Christian Biesinger (Code Review)
2019-10-31 19:53 ` Simon Marchi (Code Review)
2019-10-31 20:05 ` [review v2] " Christian Biesinger (Code Review)
2019-10-31 20:05 ` Christian Biesinger (Code Review)
2019-10-31 20:10 ` Simon Marchi (Code Review)
2019-10-31 20:10 ` Simon Marchi (Code Review)
2019-10-31 20:15 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-10-31 20:15 ` Sourceware to Gerrit sync (Code Review)
2019-11-01 15:21 ` [review v3] " Hannes Domani (Code Review)
2019-11-01 15:22 ` Christian Biesinger (Code Review)
2019-11-01 17:10 ` Tom Tromey [this message]
2019-11-06 1:08 ` Pedro Alves (Code Review)
2019-11-06 19:37 ` Christian Biesinger (Code Review)
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=87lfsz34kp.fsf@tromey.com \
--to=tom@tromey.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=gerrit@gnutoolchain-gerrit.osci.io \
--cc=gnutoolchain-gerrit@osci.io \
--cc=simon.marchi@polymtl.ca \
--cc=ssbssa@yahoo.de \
--cc=tromey@sourceware.org \
/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