From: Eli Zaretskii <eliz@gnu.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [python][patch] PR python/19151 Hardware breakpoints in GDB Python.
Date: Mon, 30 Apr 2018 14:31:00 -0000 [thread overview]
Message-ID: <83fu3csr5v.fsf@gnu.org> (raw)
In-Reply-To: <12c35b5f-aa8d-17b3-476d-2fbf4eb3587d@redhat.com> (message from Phil Muldoon on Mon, 30 Apr 2018 12:46:57 +0100)
> From: Phil Muldoon <pmuldoon@redhat.com>
> Date: Mon, 30 Apr 2018 12:46:57 +0100
>
> 2018-04-30 Phil Muldoon <pmuldoon@redhat.com>
>
> * python.texi (Breakpoints In Python): Mention
> gdb.BP_HARDWARE_BREAKPOINT.
OK for this part.
(Is this NEWS-worthy?)
Thanks.
prev parent reply other threads:[~2018-04-30 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 11:47 Phil Muldoon
2018-04-30 12:37 ` Phil Muldoon
2018-04-30 14:33 ` Eli Zaretskii
2018-05-09 14:31 ` Pedro Alves
2018-04-30 14:31 ` Eli Zaretskii [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=83fu3csr5v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.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).