From: Daniel Jacobowitz <drow@false.org>
To: teawater <teawater@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB remote user interface 0.0.0 release
Date: Thu, 18 May 2006 22:52:00 -0000 [thread overview]
Message-ID: <20060518215555.GA18245@nevyn.them.org> (raw)
In-Reply-To: <daef60380605180859l31da8a17td85b5fe0fcb99cc0@mail.gmail.com>
On Thu, May 18, 2006 at 11:59:31PM +0800, teawater wrote:
> How do you think about it?
I don't understand why you needed it. Why is this better than talking
the existing GDB/MI protocol over a pipe?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-18 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 16:37 teawater
2006-05-18 16:54 ` Bob Rossi
2006-05-19 1:41 ` teawater
2006-05-19 2:31 ` Bob Rossi
2006-05-18 22:52 ` Daniel Jacobowitz [this message]
2006-05-19 2:33 ` teawater
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=20060518215555.GA18245@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=teawater@gmail.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