From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [drow@mvista.com: Re: RFA: LOC_COMPUTED support]
Date: Mon, 24 Feb 2003 03:30:00 -0000 [thread overview]
Message-ID: <200302240330.h1O3UIK06085@duracef.shout.net> (raw)
Daniel J asks:
> I'd rather discuss a transition to C++ than any particular instance of
> this problem. Do you think it's feasible?
At this moment in time, I don't think it's even feasible to have a
discussion about C++. I'm referring to people's communication
bandwidth rather than the topic.
My two cents,
Michael C
next reply other threads:[~2003-02-24 3:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 3:30 Michael Elizabeth Chastain [this message]
2003-02-24 4:15 ` Daniel Jacobowitz
[not found] <20030213211157.GA13537@nevyn.them.org>
2003-02-20 23:08 ` Jim Blandy
2003-02-21 15:24 ` Daniel Jacobowitz
2003-02-21 17:08 ` Andrew Cagney
2003-02-21 17:14 ` Daniel Jacobowitz
2003-02-21 17:22 ` Andrew Cagney
2003-02-21 17:19 ` Joel Brobecker
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=200302240330.h1O3UIK06085@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