From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: RFC: Add named errors and messages to remote protocol
Date: Wed, 04 Jul 2007 21:29:00 -0000 [thread overview]
Message-ID: <ur6nndfi9.fsf@gnu.org> (raw)
In-Reply-To: <m3lkdwejdz.fsf@codesourcery.com> (message from Jim Blandy on Wed, 04 Jul 2007 00:08:08 -0700)
> From: Jim Blandy <jimb@codesourcery.com>
> Date: Wed, 04 Jul 2007 00:08:08 -0700
>
> A stub is required to support the @samp{g}, @samp{G}, @samp{m}, @samp{M},
> @samp{c}, and @samp{s} @var{command}s. All other @var{command}s are
> optional.
> on that response (but see also @ref{qSupported}).
Something is wrong here.
next prev parent reply other threads:[~2007-07-04 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3fy4oyfa3.fsf@codesourcery.com>
[not found] ` <20070703171613.GH2868@caradoc.them.org>
2007-07-04 7:08 ` Jim Blandy
2007-07-04 21:29 ` Eli Zaretskii [this message]
2007-07-05 19:39 ` Jim Blandy
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=ur6nndfi9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.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