From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com
Cc: drow@mvista.com, fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa] new test, pr-1090.exp, multi-register variables
Date: Mon, 24 Feb 2003 15:06:00 -0000 [thread overview]
Message-ID: <200302241506.h1OF6qv15932@duracef.shout.net> (raw)
Andrew C writes:
> The only critical thing in GDB 5.4/6.0 is ensuring that the new EMACS
> mode has everything it needs without relying on level two annotiations.
> And that has a very hard deadline :-(
When is that deadline?
How close is MI to meeting supporting the new EMACS mode ?
Michael C
next reply other threads:[~2003-02-24 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 15:06 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 4:35 Michael Elizabeth Chastain
2003-02-24 5:06 ` Daniel Jacobowitz
2003-02-24 7:27 ` Andrew Cagney
2003-02-24 14:21 ` Daniel Jacobowitz
2003-02-24 15:37 ` Andrew Cagney
2003-02-24 3:55 Michael Elizabeth Chastain
2003-02-24 4:17 ` Daniel Jacobowitz
2003-02-24 7:07 ` Daniel Berlin
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=200302241506.h1OF6qv15932@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=fnasser@redhat.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