[PATCH] gdb/NEWS: reorder some entries in the NEWS file

[PATCH] gdb/NEWS: reorder some entries in the NEWS file

[Andrew Burgess]

I spotted two entries in the NEWS file that I believe are in the wrong
place, these are:

  - An entry about MI v1 being deprecated, this feels like it should
    be the first entry under the 'MI changes' heading, and

  - An entry for the $_shell convenience function which is currently
    under the 'New commands' heading (sort of), when I think this
    should be listed in the general news section.

---

I've CC'd the authors of the two pieces I've moved in case they
object, otherwise I'll push this in a few days.

Thanks,
Andrew

---
 gdb/NEWS | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/gdb/NEWS b/gdb/NEWS
index fd7ab282f69..dce9b5018c1 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -35,8 +35,6 @@
   currently selected target.  If no remote target is selected, the default
   configuration for future connections is shown.
 
-* MI version 1 has been removed.
-
 * GDB has initial built-in support for the Debugger Adapter Protocol.
   This support requires that GDB be built with Python scripting
   enabled.
@@ -106,6 +104,16 @@
   'inferior' keyword with either the 'thread' or 'task' keywords when
   creating a breakpoint.
 
+* New convenience function "$_shell", to execute a shell command and
+  return the result.  This lets you run shell commands in expressions.
+  Some examples:
+
+   (gdb) p $_shell("true")
+   $1 = 0
+   (gdb) p $_shell("false")
+   $2 = 1
+   (gdb) break func if $_shell("some command") == 0
+
 * New commands
 
 set debug breakpoint on|off
@@ -139,18 +147,10 @@ show tui mouse-events
   Python extensions.  When off, mouse clicks are handled by the terminal,
   enabling terminal-native text selection.
 
-* New convenience function "$_shell", to execute a shell command and
-  return the result.  This lets you run shell commands in expressions.
-  Some examples:
-
-   (gdb) p $_shell("true")
-   $1 = 0
-   (gdb) p $_shell("false")
-   $2 = 1
-   (gdb) break func if $_shell("some command") == 0
-
 * MI changes
 
+** MI version 1 has been removed.
+
 ** mi now reports 'no-history' as a stop reason when hitting the end of the
    reverse execution history.
 

base-commit: 68510906a981d6abd31c51f49b2ec7e18db0a338
-- 
2.25.4

Re: [PATCH] gdb/NEWS: reorder some entries in the NEWS file

[Eli Zaretskii]

> Cc: Andrew Burgess <aburgess@redhat.com>, Tom Tromey <tom@tromey.com>,
>  Pedro Alves <pedro@palves.net>
> Date: Fri, 29 Sep 2023 14:31:19 +0100
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
> 
> 
> I spotted two entries in the NEWS file that I believe are in the wrong
> place, these are:
> 
>   - An entry about MI v1 being deprecated, this feels like it should
>     be the first entry under the 'MI changes' heading, and
> 
>   - An entry for the $_shell convenience function which is currently
>     under the 'New commands' heading (sort of), when I think this
>     should be listed in the general news section.
> 
> ---
> 
> I've CC'd the authors of the two pieces I've moved in case they
> object, otherwise I'll push this in a few days.

Thanks, fine by me.

Re: [PATCH] gdb/NEWS: reorder some entries in the NEWS file

[Andrew Burgess]

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: Andrew Burgess <aburgess@redhat.com>, Tom Tromey <tom@tromey.com>,
>>  Pedro Alves <pedro@palves.net>
>> Date: Fri, 29 Sep 2023 14:31:19 +0100
>> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
>> 
>> 
>> I spotted two entries in the NEWS file that I believe are in the wrong
>> place, these are:
>> 
>>   - An entry about MI v1 being deprecated, this feels like it should
>>     be the first entry under the 'MI changes' heading, and
>> 
>>   - An entry for the $_shell convenience function which is currently
>>     under the 'New commands' heading (sort of), when I think this
>>     should be listed in the general news section.
>> 
>> ---
>> 
>> I've CC'd the authors of the two pieces I've moved in case they
>> object, otherwise I'll push this in a few days.
>
> Thanks, fine by me.

I've gone ahead and pushed this.  If the original authors feel strongly
that their entries shouldn't be moved they can let me know and I'll move
them back.

Thanks,
Andrew