From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] gdb/931 - Canonicalize type names on input / output
Date: Mon, 22 Oct 2007 21:23:00 -0000 [thread overview]
Message-ID: <ur6jmsvfn.fsf@gnu.org> (raw)
In-Reply-To: <20071022165632.GA5202@caradoc.them.org> (message from Daniel Jacobowitz on Mon, 22 Oct 2007 12:56:32 -0400)
> Date: Mon, 22 Oct 2007 12:56:32 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>
>
> I would like to add a NEWS entry for this. Eli, is this a reasonable
> one?
>
> * GDB now parses C++ symbol and type names more flexibly.
Yes, but this is too general to be useful to the reader. How about
adding a couple of examples where it now does TRT?
Thanks.
prev parent reply other threads:[~2007-10-22 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 17:27 Daniel Jacobowitz
2007-10-22 21:23 ` Eli Zaretskii [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=ur6jmsvfn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.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