From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: qiyaoltc@gmail.com, gdb-patches@sourceware.org
Subject: Re: [RFA] Fix PR python/17981
Date: Mon, 23 May 2016 19:15:00 -0000 [thread overview]
Message-ID: <83y4704mdl.fsf@gnu.org> (raw)
In-Reply-To: <878tz0wq44.fsf@tromey.com> (message from Tom Tromey on Mon, 23 May 2016 13:06:51 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
> Date: Mon, 23 May 2016 13:06:51 -0600
>
> Yao> Yes, it is correct, but it is better to explicitly document an empty
> Yao> sequence is returned if there are no breakpoints.
>
> Here you go.
OK, thanks.
next prev parent reply other threads:[~2016-05-23 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 3:47 Tom Tromey
2016-05-23 8:52 ` Yao Qi
2016-05-23 14:05 ` Tom Tromey
2016-05-23 14:29 ` Yao Qi
2016-05-23 19:07 ` Tom Tromey
2016-05-23 19:15 ` Eli Zaretskii [this message]
2016-05-23 19:07 ` Tom Tromey
2016-05-24 8:38 ` Yao Qi
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=83y4704mdl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.com \
--cc=tom@tromey.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