From: "Simon Marchi (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Subject: [review v2] Use strerror_r in safe_strerror if available
Date: Thu, 31 Oct 2019 20:10:00 -0000 [thread overview]
Message-ID: <20191031201018.4A22620AF6@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1572551088000.I81048fbaf148035c221c528727f7efe58ba528eb@gnutoolchain-gerrit.osci.io>
Simon Marchi has posted comments on this change.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/474
......................................................................
Patch Set 2:
Thanks!
--
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I81048fbaf148035c221c528727f7efe58ba528eb
Gerrit-Change-Number: 474
Gerrit-PatchSet: 2
Gerrit-Owner: Christian Biesinger <cbiesinger@google.com>
Gerrit-CC: Simon Marchi <simon.marchi@polymtl.ca>
Gerrit-Comment-Date: Thu, 31 Oct 2019 20:10:18 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
next prev parent reply other threads:[~2019-10-31 20: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) [this message]
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
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=20191031201018.4A22620AF6@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=gnutoolchain-gerrit@osci.io \
/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