From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA/testsuite] Allow __libc_start_main above main in annota1.exp
Date: Sat, 09 Feb 2002 08:19:00 -0000 [thread overview]
Message-ID: <npeljud3u3.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3C58212C.5BB1291F@redhat.com>
You know, it wouldn't be hard to write another mi-like interface that
used different builders to emit Emacs Lisp s-expressions. We could
end up with a real killer Emacs interface that way.
next prev parent reply other threads:[~2002-02-09 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 8:02 Michael Elizabeth Chastain
2002-01-30 8:37 ` Fernando Nasser
2002-02-09 8:18 ` Jim Blandy
2002-02-09 8:19 ` Jim Blandy [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-09 16:05 Daniel Jacobowitz
2002-01-09 16:41 ` Andrew Cagney
2002-01-29 21:57 ` Daniel Jacobowitz
2002-01-29 22:59 ` Kevin Buettner
2002-01-30 7:01 ` Fernando Nasser
2002-01-30 21:08 ` Daniel Jacobowitz
2002-02-09 8:19 ` Jim Blandy
2002-02-09 14:14 ` Daniel Jacobowitz
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=npeljud3u3.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=drow@mvista.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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