From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: pushed: [release/HEAD 2/2] Update NEWS post GDB 8.1 branch creation.
Date: Fri, 05 Jan 2018 04:21:00 -0000 [thread overview]
Message-ID: <20180105042130.24834-3-brobecker@adacore.com> (raw)
In-Reply-To: <20180105042130.24834-1-brobecker@adacore.com>
gdb/ChangeLog:
* NEWS: Create a new section for the next release branch.
Rename the section of the current branch, now that it has
been cut.
---
gdb/ChangeLog | 6 ++++++
gdb/NEWS | 4 +++-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 07c45172b2..b63238288e 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,11 @@
2018-01-05 Joel Brobecker <brobecker@adacore.com>
+ * NEWS: Create a new section for the next release branch.
+ Rename the section of the current branch, now that it has
+ been cut.
+
+2018-01-05 Joel Brobecker <brobecker@adacore.com>
+
GDB 8.1 branch created (5219ac6237c272b938c28517bf371429260c71e7):
* version.in: Bump version to 8.1.50.DATE-git.
diff --git a/gdb/NEWS b/gdb/NEWS
index 14fcdf8674..2f834c6ff4 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -1,7 +1,9 @@
What has changed in GDB?
(Organized release by release)
-*** Changes since GDB 8.0
+*** Changes since GDB 8.1
+
+*** Changes in GDB 8.1
* GDB now supports dynamically creating arbitrary register groups specified
in XML target descriptions. This allows for finer grain grouping of
--
2.11.0
next prev parent reply other threads:[~2018-01-05 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 4:21 FYI/HEAD: Patches applied to branch master Joel Brobecker
2018-01-05 4:21 ` Joel Brobecker [this message]
2018-01-05 4:21 ` pushed: [release/HEAD 1/2] Bump version to 8.1.50.DATE-git Joel Brobecker
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=20180105042130.24834-3-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).