From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Add rl78 to NEWS, MAINTAINERS, and Makefile.in
Date: Wed, 15 Feb 2012 03:55:00 -0000 [thread overview]
Message-ID: <20120214175801.5f8ffb62@mesquite.lan> (raw)
In-Reply-To: <4F3AF16A.9090803@earthlink.net>
On Tue, 14 Feb 2012 15:42:34 -0800
Stan Shebs <stanshebs@earthlink.net> wrote:
> Don't you want your new bit underneath "Changes since GDB 7.4"?
You're right. I botched it.
> Also, I don't know that there is anything like a standard for this, but
> I tend to like having features that affect more users higher in the NEWS
> section for a release, and the more arcane/specialized additions more
> towards the end of the section; the theory being that we have so many
> new features in each release, and many readers won't actually make it
> all the way through the list. :-)
I agree with this too.
Let's try the NEWS entry over again...
* NEWS: Mention rl78 as a new target.
Index: NEWS
===================================================================
RCS file: /cvs/src/src/gdb/NEWS,v
retrieving revision 1.487
diff -u -p -r1.487 NEWS
--- NEWS 7 Feb 2012 19:47:15 -0000 1.487
+++ NEWS 15 Feb 2012 00:55:19 -0000
@@ -49,6 +49,10 @@
** "catch load" and "catch unload" can be used to stop when a shared
library is loaded or unloaded, respectively.
+* New targets
+
+Renesas RL78 rl78-*-elf
+
*** Changes in GDB 7.4
* GDB now handles ambiguous linespecs more consistently; the existing
next prev parent reply other threads:[~2012-02-15 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 23:42 Kevin Buettner
2012-02-15 0:58 ` Stan Shebs
2012-02-15 3:55 ` Kevin Buettner [this message]
2012-02-15 6:48 ` Eli Zaretskii
2012-02-15 22:56 ` Kevin Buettner
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=20120214175801.5f8ffb62@mesquite.lan \
--to=kevinb@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