public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [release/HEAD 2/2] Update NEWS post GDB 7.10 branch creation.
Date: Mon, 06 Jul 2015 20:05:00 -0000	[thread overview]
Message-ID: <1436213104-19619-3-git-send-email-brobecker@adacore.com> (raw)
In-Reply-To: <1436213104-19619-1-git-send-email-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 3473fa5..96843e8 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,11 @@
 2015-07-06  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.
+
+2015-07-06  Joel Brobecker  <brobecker@adacore.com>
+
 	GDB 7.10 branch created (66c4b3e8a628a207bc6aafef6af0c4128195f56e):
 	* version.in: Bump version to 7.10.50.DATE-cvs.
 
diff --git a/gdb/NEWS b/gdb/NEWS
index 748fc00..bbeeb40 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -1,7 +1,9 @@
 		What has changed in GDB?
 	     (Organized release by release)
 
-*** Changes since GDB 7.9
+*** Changes since GDB 7.10
+
+*** Changes in GDB 7.10
 
 * Support for process record-replay and reverse debugging on aarch64*-linux*
   targets has been added.  GDB now supports recording of A64 instruction set
-- 
2.1.4

  reply	other threads:[~2015-07-06 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 20:05 FYI/HEAD: Patches applied to branch master Joel Brobecker
2015-07-06 20:05 ` Joel Brobecker [this message]
2015-07-06 20:05 ` [release/HEAD 1/2] Bump version to 7.10.50.DATE-cvs 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=1436213104-19619-3-git-send-email-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).