From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [release/HEAD 2/2] Update gdb/NEWS after GDB 18 branch creation.
Date: Thu, 6 Aug 2026 18:14:52 +0100 [thread overview]
Message-ID: <d71c8e3e713b6baf884a7b12a9435e53111b574b.1786036265.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1786036265.git.aburgess@redhat.com>
This commit a new section for the next release branch, and renames
the section of the current branch, now that it has been cut.
---
gdb/NEWS | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index 8f40ca5cb11..10c182067f9 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -1,7 +1,9 @@
What has changed in GDB?
(Organized release by release)
-*** Changes since GDB 17
+*** Changes since GDB 18
+
+*** Changes in GDB 18
* Support for the Common Trace Format (CTF) has been removed. GDB now
saves trace information exclusively in its own "tfile" format.
--
2.25.4
prev parent reply other threads:[~2026-08-06 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 17:14 FYI/HEAD: Patches applied to branch master Andrew Burgess
2026-08-06 17:14 ` [release/HEAD 1/2] Bump version to 19.0.50.DATE-git Andrew Burgess
2026-08-06 17:14 ` Andrew Burgess [this message]
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=d71c8e3e713b6baf884a7b12a9435e53111b574b.1786036265.git.aburgess@redhat.com \
--to=aburgess@redhat.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