From: Doug Evans <xdje42@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Yao Qi <qiyaoltc@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Replace address and aspace with thread in struct step_over_info
Date: Thu, 22 Dec 2016 23:51:00 -0000 [thread overview]
Message-ID: <m3mvfnv7xt.fsf@sspiff.org> (raw)
In-Reply-To: <5717C47A.9090905@redhat.com> (Pedro Alves's message of "Wed, 20 Apr 2016 19:03:38 +0100")
Pedro Alves <palves@redhat.com> writes:
> On 04/20/2016 07:01 PM, Doug Evans wrote:
>
>> A good place for a comment explaining Why Things Are The Way They Are.
>>
>> Not sure how you want to word this.
>
> That looks just fine to me.
Thanks.
Committed.
next prev parent reply other threads:[~2016-12-22 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 13:29 [PATCH 0/2] Add thread info in 'struct step_over_info' Yao Qi
2016-04-15 13:29 ` [PATCH 2/2] Replace address and aspace with thread in struct step_over_info Yao Qi
2016-04-19 10:43 ` Pedro Alves
2016-04-19 13:55 ` Yao Qi
2016-04-20 18:01 ` Doug Evans
2016-04-20 18:03 ` Pedro Alves
2016-12-22 23:51 ` Doug Evans [this message]
2016-04-15 13:29 ` [PATCH 1/2] Refactor function set_step_over_info 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=m3mvfnv7xt.fsf@sspiff.org \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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).