From: Quality Quorum <qqi@world.std.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: remote nits
Date: Wed, 15 Dec 1999 05:53:00 -0000 [thread overview]
Message-ID: <Pine.SGI.3.95.991215084518.6945A-100000@world.std.com> (raw)
In-Reply-To: <3855F0D8.12905961@cygnus.com>
> > It is unclear from document that 'qRcmd' indeed allows responses
> > starting from 'E', however there is a code handling this case
> > in remote.c
>
> The normal response to Rcmd is a HEX encoded byte-stream. E is a hex
> digit.
It seems like there is an established practice of using low case
characters for hex encodings sent by stubs - otherwise 'm' request
would never work correctly. So, this is not an issue at all, unless,
you would tell me that existing implementations of qRcmd break
this one too :).
BTW, I got it while working on v0.2 of protocol spec, I was quite
surprised that the positive impact of this exercise was that immediate.
>
> Andrew
>
Thanks,
Aleksey
next prev parent reply other threads:[~1999-12-15 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3855F0D8.12905961@cygnus.com>
1999-12-14 6:47 ` Quality Quorum
1999-12-14 7:35 ` Andrew Cagney
1999-12-15 5:53 ` Quality Quorum [this message]
[not found] <Pine.SGI.3.95.991214105557.17037A-100000@world.std.com>
1999-12-14 15:02 ` Andrew Cagney
1999-12-14 15:31 ` Quality Quorum
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=Pine.SGI.3.95.991215084518.6945A-100000@world.std.com \
--to=qqi@world.std.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.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