gdb/NEWS: group general news items together

I noticed that the list of general NEWS items seemed to have gotten
mixed up a bit in the NEWS file.  This commit just moves things around
so that the general items all appear at the start of the 'Changes
since GDB 15' section.  I've not changed any of the actual content.

diff --git a/gdb/NEWS b/gdb/NEWS
index fa57b56237d3d1576d23909ac30a772b1de3d9e7..cfc9cb05f77caa924126167982f86884bea939ad 100644 (file)
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -21,20 +21,6 @@
   inferior containing the thread of interest.  The breakpoint will
   be hit no less than before.
 
-* Python API
-
-  ** Added gdb.record.clear.  Clears the trace data of the current recording.
-     This forces re-decoding of the trace for successive commands.
-
-* Debugger Adapter Protocol changes
-
-  ** The "scopes" request will now return a scope holding global
-     variables from the stack frame's compilation unit.
-
-  ** The "scopes" request will return a "returnValue" scope holding
-     the return value from the latest "stepOut" command, when
-     appropriate.
-
 * For ARM targets, the offset of the pc in the jmp_buf has been fixed to match
   glibc 2.20 and later.  This should only matter when not using libc probes.
   This may cause breakage when using an incompatible libc, like uclibc or
@@ -51,6 +37,20 @@
   history has been reached.  It also specifies that the forward execution can
   continue, and the recording will also continue.
 
+* Python API
+
+  ** Added gdb.record.clear.  Clears the trace data of the current recording.
+     This forces re-decoding of the trace for successive commands.
+
+* Debugger Adapter Protocol changes
+
+  ** The "scopes" request will now return a scope holding global
+     variables from the stack frame's compilation unit.
+
+  ** The "scopes" request will return a "returnValue" scope holding
+     the return value from the latest "stepOut" command, when
+     appropriate.
+
 * New commands
 
 maintenance info inline-frames [ADDRESS]