From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@gnat.com>
Subject: [commit 2/2] NEWS: Create a new section for the next release branch.
Date: Wed, 07 Jul 2010 18:50:00 -0000 [thread overview]
Message-ID: <1278528611-27149-3-git-send-email-brobecker@adacore.com> (raw)
In-Reply-To: <1278528611-27149-1-git-send-email-brobecker@adacore.com>
From: Joel Brobecker <brobecker@gnat.com>
NEWS update...
---
gdb/ChangeLog | 6 ++++++
gdb/NEWS | 4 +++-
2 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 87399d1..51e1504 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,11 @@
2010-07-07 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.
+
+2010-07-07 Joel Brobecker <brobecker@adacore.com>
+
GDB 7.2 branch created (branch timestamp: 2010-07-07 17:00 UTC)
* version.in: Bump version to 7.2.50.20100707-cvs.
diff --git a/gdb/NEWS b/gdb/NEWS
index 77c55de..0aa93cc 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -1,7 +1,9 @@
What has changed in GDB?
(Organized release by release)
-*** Changes since GDB 7.1
+*** Changes since GDB 7.2
+
+*** Changes in GDB 7.1
* C++ Improvements:
--
1.7.1
next prev parent reply other threads:[~2010-07-07 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 18:50 [commit/release] Updates on the HEAD following the 7.2 branch creation Joel Brobecker
2010-07-07 18:50 ` [commit 1/2] Record GDB " Joel Brobecker
2010-07-07 18:50 ` Joel Brobecker [this message]
2010-07-08 6:10 ` [commit 2/2] NEWS: Create a new section for the next release branch Eli Zaretskii
2010-07-08 15:42 ` 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=1278528611-27149-3-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=brobecker@gnat.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