From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: simon.marchi@polymtl.ca, gdb-patches@sourceware.org
Subject: Re: [PATCH] Handle dprintf argument evaluation errors better (PR gdb/16551)
Date: Thu, 23 Aug 2018 02:42:00 -0000 [thread overview]
Message-ID: <83in41by7h.fsf@gnu.org> (raw)
In-Reply-To: <8284ef0e-7f4b-b29e-0a55-2342ad261632@ericsson.com> (message from Simon Marchi on Wed, 22 Aug 2018 20:03:05 -0400)
> CC: <gdb-patches@sourceware.org>, Eli Zaretskii <eliz@gnu.org>
> From: Simon Marchi <simon.marchi@ericsson.com>
> Date: Wed, 22 Aug 2018 20:03:05 -0400
>
> Eli, would it be possible to take a look at least at the NEWS/doc part of this patch? If
> there are no comments on the behavior change, I would be ready to merge this patch, but
> I'd like to make sure that NEWS/doc is ok first.
Sorry I missed that: the documentation parts are OK.
Thanks.
next prev parent reply other threads:[~2018-08-23 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 20:02 Simon Marchi
2018-06-27 14:32 ` Simon Marchi
2018-08-23 0:03 ` Simon Marchi
2018-08-23 2:42 ` Eli Zaretskii [this message]
2018-08-23 9:44 ` Pedro Alves
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=83in41by7h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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).