From: Steven Johnson <sjohnson@sakuraindustries.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] Add section on interrupts to remote protocol documentation
Date: Sat, 19 Nov 2005 10:57:00 -0000 [thread overview]
Message-ID: <437E7DC6.4050309@sakuraindustries.com> (raw)
In-Reply-To: <8f2776cb0511181336l62caf79bsd91a5d123b4cd471@mail.gmail.com>
Jim Blandy wrote:
>On 11/18/05, Kevin Buettner <kevinb@redhat.com> wrote:
>
>
>>+@samp{Ctrl-C}, on the other hand, is defined and implemented for all
>>+transport mechanisms. It is represented by sending the single byte
>>+@code{0x03} without any of the usual packet overhead described in in
>>+the Overview section (@pxref{Overview}). When a @code{0x03} byte is
>>+transmitted as part of a packet, it is considered to be packet data
>>+and does @emph{not} represent an interrupt. E.g., an @samp{X} packet
>>+(@pxref{X packet}, used for binary downloads, may include an unescaped
>>+@code{0x03} as part of its packet.
>>
>>
>
>Yep, that's pretty explicit. Fine with me.
>
>
>
>
Ditto.
next prev parent reply other threads:[~2005-11-19 1:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 5:59 Kevin Buettner
2005-11-18 8:35 ` Jim Blandy
2005-11-18 11:20 ` Steven Johnson
2005-11-18 11:57 ` Jim Blandy
2005-11-18 17:23 ` Kevin Buettner
2005-11-18 20:25 ` Jim Blandy
2005-11-18 13:53 ` Eli Zaretskii
2005-11-18 15:33 ` Steven Johnson
2005-11-18 14:06 ` Eli Zaretskii
2005-11-18 21:45 ` Kevin Buettner
2005-11-18 21:47 ` Daniel Jacobowitz
2005-11-18 22:07 ` Jim Blandy
2005-11-19 10:57 ` Steven Johnson [this message]
2005-11-18 22:18 ` Kevin Buettner
2005-11-18 22:19 ` Michael Snyder
2005-11-18 22:38 ` Eli Zaretskii
2005-11-19 1:21 ` Kevin Buettner
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=437E7DC6.4050309@sakuraindustries.com \
--to=sjohnson@sakuraindustries.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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