From: Andrew Cagney <ac131313@cygnus.com>
To: Quality Quorum <qqi@world.std.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: remote nits
Date: Tue, 14 Dec 1999 07:35:00 -0000 [thread overview]
Message-ID: <38566371.ECAB7FA7@cygnus.com> (raw)
In-Reply-To: <Pine.SGI.3.95.991214083223.29022A-100000@world.std.com>
Quality Quorum wrote:
>
>
> ???????? As far as I understand the document normal response to
> Rcmd is a sequence of zero of more 'O' packets followed, by OK or 'ENN'.
One of the specified return codes is:
reply OUTPUT
A command response with the hex encoded output string OUTPUT.
and is separate to in intermediate O packet.
> IMHO, the only use of Rcmd is to allow user to type some command
> and see the response, in all other cases query should be defined and
> used not a command, we have raw queries just for this purpose.
Sorry you've lost me here.
Andrew
From qqi@world.std.com Tue Dec 14 08:09:00 1999
From: Quality Quorum <qqi@world.std.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: remote nits
Date: Tue, 14 Dec 1999 08:09:00 -0000
Message-id: <Pine.SGI.3.95.991214105557.17037A-100000@world.std.com>
References: <38566371.ECAB7FA7@cygnus.com>
X-SW-Source: 1999-q4/msg00504.html
Content-length: 1043
On Wed, 15 Dec 1999, Andrew Cagney wrote:
> Quality Quorum wrote:
> >
> >
> > ???????? As far as I understand the document normal response to
> > Rcmd is a sequence of zero of more 'O' packets followed, by OK or 'ENN'.
>
> One of the specified return codes is:
>
> reply OUTPUT
> A command response with the hex encoded output string OUTPUT.
This one should be outlawed before it is too late, it simply does not
make any sense.
> > and is separate to in intermediate O packet.
> > > IMHO, the only use of Rcmd is to allow user to type some command
> > and see the response, in all other cases query should be defined and
> > used not a command, we have raw queries just for this purpose.
>
> Sorry you've lost me here.
The question is who is going to issue a command and to interpret a command
response ?
If it is a user then proper response have to be in user-readable
form ('O' packet). If it is machine, then command query should not be
used (we have raw queries for the purpose).
>
> Andrew
>
Thanks,
Aleksey
next prev parent reply other threads:[~1999-12-14 7:35 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 [this message]
1999-12-15 5:53 ` Quality Quorum
[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=38566371.ECAB7FA7@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=qqi@world.std.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