From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pmuldoon@redhat.com, simon.marchi@polymtl.ca, gdb-patches@sourceware.org
Subject: Re: [RFA/RFC] Clarify contents of NEWS entry re: Python "rbreak" (waa: "Re: [python][patch] Python rbreak")
Date: Fri, 02 Feb 2018 03:16:00 -0000 [thread overview]
Message-ID: <20180202031635.7fdgdxev24r6hb3i@adacore.com> (raw)
In-Reply-To: <83h8r0efdn.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
> > > > [hi Eli -- not sure if the attached patch is obvious or not, so I will
> > > > wait for your approval, assuming Phil confirms. Thank you!]
> > >
> > > Are you asking about the NEWS entry or about the entire patch? If
> > > the latter, I don't think I saw it, and neither do I see it in the
> > > list archives. I think. What am I missing?
> >
> > Just asking whether you approve the patch I attached, or if you
> > have some comments.
>
> Ah, OK. But where was it posted? I don't seem to be able to find it,
> neither in my inbox nor in the list archives. How did I miss it?
I was posted ... in my head! Another example of the forgetting to
attach the patch classic. Sorry about that.
gdb/ChangeLog:
* NEWS <Changes in GDB 8.1>: Clarify that "rbreak" is a new
Python function, rather than a new command.
Thanks,
--
Joel
[-- Attachment #2: 0001-gdb-NEWS-Clarify-the-news-entry-for-rbreak-in-GDB-8..patch --]
[-- Type: text/x-diff, Size: 1214 bytes --]
From 1db141b40e47bd5fc19dc4ee2a4c6f9c4fe2881b Mon Sep 17 00:00:00 2001
From: Joel Brobecker <brobecker@adacore.com>
Date: Thu, 1 Feb 2018 13:41:52 +0400
Subject: [PATCH] gdb/NEWS: Clarify the news entry for "rbreak" in GDB 8.1
gdb/ChangeLog:
* NEWS <Changes in GDB 8.1>: Clarify that "rbreak" is a new
Python function, rather than a new command.
---
gdb/NEWS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index 9cd38f3d91..1767cef920 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -125,9 +125,9 @@
gdb.new_thread are emitted. See the manual for further
description of these.
- ** A new command, "rbreak" has been added to the Python API. This
- command allows the setting of a large number of breakpoints via a
- regex pattern in Python. See the manual for further details.
+ ** A new function, "gdb.rbreak" has been added to the Python API.
+ This function allows the setting of a large number of breakpoints
+ via a regex pattern in Python. See the manual for further details.
** Python breakpoints can now accept explicit locations. See the
manual for a further description of this feature.
--
2.11.0
next prev parent reply other threads:[~2018-02-02 3:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 11:30 [python][patch] Python rbreak Phil Muldoon
2017-10-11 12:11 ` Eli Zaretskii
2017-10-11 12:27 ` Phil Muldoon
2017-10-11 16:19 ` Kevin Buettner
2017-10-11 16:24 ` Phil Muldoon
2017-10-13 8:08 ` Phil Muldoon
2017-10-16 22:22 ` Simon Marchi
2017-10-16 23:01 ` Phil Muldoon
2017-10-17 0:24 ` Simon Marchi
2017-11-03 9:46 ` Phil Muldoon
2017-11-03 10:05 ` Eli Zaretskii
2017-11-13 19:29 ` Phil Muldoon
2018-02-01 9:47 ` [RFA/RFC] Clarify contents of NEWS entry re: Python "rbreak" (waa: "Re: [python][patch] Python rbreak") Joel Brobecker
2018-02-01 10:26 ` Phil Muldoon
2018-02-01 16:21 ` Eli Zaretskii
2018-02-01 17:32 ` Joel Brobecker
2018-02-01 18:25 ` Eli Zaretskii
2018-02-02 3:16 ` Joel Brobecker [this message]
2018-02-09 4:30 ` Joel Brobecker
2018-02-09 9:26 ` Eli Zaretskii
2018-02-09 12:13 ` Joel Brobecker
2017-11-14 20:23 ` [python][patch] Python rbreak Simon Marchi
2017-11-16 14:19 ` Phil Muldoon
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=20180202031635.7fdgdxev24r6hb3i@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.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).