From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>, gdb@sources.redhat.com
Subject: Re: [remote protocol] Allow qSymbol response to continue packets
Date: Fri, 12 Mar 2004 19:45:00 -0000 [thread overview]
Message-ID: <20040312194541.GA31078@nevyn.them.org> (raw)
In-Reply-To: <20040311233833.GA32710@nevyn.them.org>
On Thu, Mar 11, 2004 at 06:38:33PM -0500, Daniel Jacobowitz wrote:
> On Thu, Mar 11, 2004 at 06:20:21PM -0500, Andrew Cagney wrote:
> > Protocol's can't make such assumptions.
>
> I disagree.
Anyway, let me take a stab at implementing it the way you described.
I still think it's overkill, but I may be able to work out a way to do
it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-12 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-06 23:52 Daniel Jacobowitz
2004-03-07 5:45 ` Eli Zaretskii
2004-03-11 20:06 ` Andrew Cagney
2004-03-11 20:16 ` Daniel Jacobowitz
2004-03-11 21:27 ` Andrew Cagney
2004-03-11 21:40 ` Daniel Jacobowitz
2004-03-11 23:21 ` Andrew Cagney
2004-03-11 23:38 ` Daniel Jacobowitz
2004-03-12 19:45 ` Daniel Jacobowitz [this message]
2004-03-17 16:07 ` Andrew Cagney
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=20040312194541.GA31078@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=gdb@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