From: Michael Snyder <msnyder@vmware.com>
To: Michael Snyder <msnyder@vmware.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Resubmit, reverse debugging [0/5]
Date: Wed, 15 Oct 2008 18:20:00 -0000 [thread overview]
Message-ID: <48F63377.5020307@vmware.com> (raw)
In-Reply-To: <20081014122648.GB7471@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Fri, Oct 10, 2008 at 02:58:06PM -0700, Michael Snyder wrote:
>> OK, here's a patch that adds
>> 1) remote protocol documentation
>> 2) The requested extension to the 'T' reply to replace E06
>> 3) A big honking "deprecated" warning for E06.
>
> I'm even fine with the warning being replaced by a comment. The most
> important part, IMO, is having a non-hackish version of the protocol
> implemented and documented.
All right, so that's in.
We also discussed earlier the idea of a capability check,
or like a qSupported message. Are we going to make that a
requirement before this patch can go in? Or can it be added
as a subsequent, incremental improvement?
And are there any more requirements before this patch can go in?
next prev parent reply other threads:[~2008-10-15 18:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 2:17 Michael Snyder
2008-10-10 17:44 ` Michael Snyder
2008-10-10 17:54 ` Daniel Jacobowitz
2008-10-10 18:38 ` Michael Snyder
2008-10-11 2:43 ` Daniel Jacobowitz
2008-10-11 2:48 ` Michael Snyder
2008-10-11 8:02 ` Eli Zaretskii
2008-10-13 19:21 ` Michael Snyder
2008-10-14 7:56 ` Jakob Engblom
2008-10-14 9:07 ` teawater
2008-10-14 12:24 ` Daniel Jacobowitz
2008-10-14 12:27 ` Daniel Jacobowitz
2008-10-15 18:20 ` Michael Snyder [this message]
2008-10-15 18:30 ` Daniel Jacobowitz
2008-10-15 18:42 ` Michael Snyder
2008-10-15 18:47 ` Pedro Alves
2008-10-15 18:49 ` Michael Snyder
2008-10-11 9:47 ` Joel Brobecker
2008-10-13 19:22 ` Michael Snyder
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=48F63377.5020307@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
/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