From: Phil Muldoon <pmuldoon@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, pedro@codesourcery.com
Subject: Re: [python] [doc] PR 12930/12802 (clarify Breakpoint::stop doco)
Date: Fri, 07 Oct 2011 13:48:00 -0000 [thread overview]
Message-ID: <m3ipo0sykz.fsf@redhat.com> (raw)
In-Reply-To: <83obxugeev.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 06 Oct 2011 20:31:36 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Phil Muldoon <pmuldoon@redhat.com>
>> CC: eli@gnu.org, pedro@codesourcery.com
>> Date: Thu, 06 Oct 2011 11:58:51 +0100
>>
>> This patch address the PRs 12930, and 12802 which both arise from
>> confusion regarding the scope of actions in the Breakpoint::stop
>> callback. I have added some documentation to clarify.
>
> Thanks.
>
> Okay with those changes.
Thanks, so committed.
Cheers,
Phil
prev parent reply other threads:[~2011-10-07 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 10:59 Phil Muldoon
2011-10-06 13:40 ` Pedro Alves
2011-10-06 13:58 ` Phil Muldoon
2011-10-06 14:02 ` Pedro Alves
2011-10-06 18:32 ` Eli Zaretskii
2011-10-07 10:22 ` Phil Muldoon
2011-10-07 13:48 ` Phil Muldoon [this message]
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=m3ipo0sykz.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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