From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: Ping: canonicalize type names on input / output
Date: Mon, 30 Mar 2009 18:59:00 -0000 [thread overview]
Message-ID: <m38wmmn8xs.fsf@fleche.redhat.com> (raw)
I'd like to ping this patch of Daniel's:
http://sourceware.org/ml/gdb-patches/2007-10/msg00510.html
I didn't see any response to the content of this patch.
I would like to put this in as a prerequisite for the Python
pretty-printing support. Without this, it is difficult to manipulate
some types by name, e.g.:
http://sourceware.org/ml/archer/2008-q4/msg00219.html
We've been using this on the Python branch, and a couple others, for a
while without ill effects; though Jan did find a bug and supplied this
additional fix:
http://sourceware.org/ml/archer/2009-q1/msg00383.html
If there are no comments I will check this in.
Tom
next reply other threads:[~2009-03-30 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 18:59 Tom Tromey [this message]
2009-03-30 19:03 ` Daniel Jacobowitz
2009-03-30 21:25 ` Tom Tromey
2009-03-31 13:37 ` Eli Zaretskii
2009-03-31 20:32 ` Tom Tromey
2009-03-30 19:08 ` Eli Zaretskii
2009-03-30 19:15 ` Tom Tromey
2009-03-30 21:16 ` Eli Zaretskii
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=m38wmmn8xs.fsf@fleche.redhat.com \
--to=tromey@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