From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH] Minor NEWS rearrangement
Date: Fri, 14 Jun 2019 18:31:00 -0000 [thread overview]
Message-ID: <20190614183130.8216-1-tromey@adacore.com> (raw)
I noticed that a NEWS item about Python scripting changes appeared
between an item about a convenience function and an item about a
convenience variable. I think it's better for the latter to be next
to each other.
gdb/ChangeLog
2019-06-14 Tom Tromey <tromey@adacore.com>
* NEWS: Move convenience variable news above Python news.
---
gdb/ChangeLog | 4 ++++
gdb/NEWS | 8 ++++----
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index 76564d06774..0a3b5b8b6c8 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -21,6 +21,10 @@
* Two new convenience functions $_cimag and $_creal that extract the
imaginary and real parts respectively from complex numbers.
+* New built-in convenience variables $_shell_exitcode and $_shell_exitsignal
+ provide the exitcode or exit status of the shell commands launched by
+ GDB commands such as "shell", "pipe" and "make".
+
* Python API
** The gdb.Value type has a new method 'format_string' which returns a
@@ -32,10 +36,6 @@
** gdb.Type has a new property 'objfile' which returns the objfile the
type was defined in.
-* New built-in convenience variables $_shell_exitcode and $_shell_exitsignal
- provide the exitcode or exit status of the shell commands launched by
- GDB commands such as "shell", "pipe" and "make".
-
* New commands
| [COMMAND] | SHELL_COMMAND
--
2.20.1
next reply other threads:[~2019-06-14 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 18:31 Tom Tromey [this message]
2019-06-14 19:01 ` Eli Zaretskii
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=20190614183130.8216-1-tromey@adacore.com \
--to=tromey@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