From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Select a particular mangling of a demangled symbol in lookup_block_symbol
Date: Sat, 16 Feb 2002 10:59:00 -0000 [thread overview]
Message-ID: <200202161859.g1GIxVZ10810@duracef.shout.net> (raw)
Hi Daniel,
> Meanwhile, I'd like to put this patch in because it is a strict
> improvement over what we have.
I got some sleep so that I could look at this particular patch
with fresh eyes.
I agree with you; this patch can never do harm (as far as I can tell).
So I don't object to it.
Michael C
next reply other threads:[~2002-02-16 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-16 10:59 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-15 18:15 Michael Elizabeth Chastain
2002-02-15 16:38 Michael Elizabeth Chastain
2002-02-15 16:46 ` Daniel Jacobowitz
2002-02-14 15:55 Daniel Jacobowitz
2002-03-19 11:53 ` Daniel Jacobowitz
2002-03-19 14:25 ` Elena Zannoni
2002-03-19 14:20 ` Elena Zannoni
2002-03-19 14:47 ` Elena Zannoni
2002-03-22 10:55 ` Daniel Jacobowitz
2002-03-22 12:11 ` Elena Zannoni
2002-03-22 14:53 ` Daniel Jacobowitz
2002-03-22 10:52 ` Daniel Jacobowitz
2002-03-22 12:10 ` Elena Zannoni
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=200202161859.g1GIxVZ10810@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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