From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [pushed] gdb/NEWS: Move "Xmethods can now specify a result type" to GDB 7.9.1 section.
Date: Wed, 13 May 2015 17:36:00 -0000 [thread overview]
Message-ID: <1431538558-24148-1-git-send-email-brobecker@adacore.com> (raw)
Hello,
As this change was ported to GDB 7.9.1, the NEWS entry is moved to
a newly-created "Changes in GDB 7.9.1" section, matching the NEWS
file which is going to be distributed with the GDB 7.9.1 release.
gdb/ChangeLog:
* NEWS: Create "Changes in GDB 7.9.1" section. Move news about
Xmethods now being able to specify a result type to that new
section.
Pushed as obvious.
Thanks,
--
Joel
---
gdb/ChangeLog | 6 ++++++
gdb/NEWS | 7 ++++++-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index bef49d8..cf4b9de 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,9 @@
+2015-05-13 Joel Brobecker <brobecker@adacore.com>
+
+ * NEWS: Create "Changes in GDB 7.9.1" section. Move news about
+ Xmethods now being able to specify a result type to that new
+ sectioin.
+
2015-05-13 Patrick Palka <patrick@parcs.ath.cx>
* tui/tui-win.c (tui_async_resize_screen): Clear win_resized
diff --git a/gdb/NEWS b/gdb/NEWS
index bf12101..7778830 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -56,7 +56,6 @@
** You can now write frame unwinders in Python.
** gdb.Type objects have a new method "optimized_out",
returning optimized out gdb.Value instance of this type.
- ** Xmethods can now specify a result type.
** gdb.Value objects have new methods "reference_value" and
"const_value" which return a reference to the value and a
"const" version of the value respectively.
@@ -172,6 +171,12 @@ fork-events and vfork-events features in qSupported
HP/PA running HP-UX hppa*-*-hpux*
Itanium running HP-UX ia64-*-hpux*
+*** Changes in GDB 7.9.1
+
+* Python Scripting
+
+ ** Xmethods can now specify a result type.
+
*** Changes in GDB 7.9
* GDB now supports hardware watchpoints on x86 GNU Hurd.
--
1.9.1
reply other threads:[~2015-05-13 17:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1431538558-24148-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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).