From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit 2/2] NEWS: Create a new section for the next release branch.
Date: Thu, 08 Jul 2010 15:42:00 -0000 [thread overview]
Message-ID: <20100708154203.GM2595@adacore.com> (raw)
In-Reply-To: <83sk3u7bgs.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 81 bytes --]
> Shouldn't the last line say "in GDB 7.2"?
Good catch, fixed thusly:
--
Joel
[-- Attachment #2: NEWS.diff --]
[-- Type: text/x-diff, Size: 881 bytes --]
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.391
diff -u -u -p -r1.391 NEWS
--- NEWS 7 Jul 2010 17:52:37 -0000 1.391
+++ NEWS 8 Jul 2010 15:41:07 -0000
@@ -3,7 +3,7 @@
*** Changes since GDB 7.2
-*** Changes in GDB 7.1
+*** Changes in GDB 7.2
* C++ Improvements:
Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.11976
diff -u -u -p -r1.11976 ChangeLog
--- ChangeLog 7 Jul 2010 17:52:37 -0000 1.11976
+++ ChangeLog 8 Jul 2010 15:41:09 -0000
@@ -1,3 +1,7 @@
+2010-07-08 Joel Brobecker <brobecker@adacore.com>
+
+ * NEWS: Fix typo in section name (s/GDB 7.1/GDB 7.2).
+
2010-07-07 Joel Brobecker <brobecker@adacore.com>
* NEWS: Create a new section for the next release branch.
prev parent reply other threads:[~2010-07-08 15:42 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 ` [commit 2/2] NEWS: Create a new section for the next release branch Joel Brobecker
2010-07-08 6:10 ` Eli Zaretskii
2010-07-08 15:42 ` Joel Brobecker [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=20100708154203.GM2595@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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