From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: RFC: Remote "qSupported" features probe
Date: Tue, 13 Jun 2006 18:23:00 -0000 [thread overview]
Message-ID: <uk67k532m.fsf@gnu.org> (raw)
In-Reply-To: <20060612195313.GA11276@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 12 Jun 2006 15:53:13 -0400)
> Date: Mon, 12 Jun 2006 15:53:13 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> Eli, there's a big chunk of texinfo in here. It's been basically rewritten
> since the last time I posted a texinfo version of the documentation; could
> you take a look at it, please?
Taking a look...
> +@table @samp
> +@item @var{stubfeature} @r{[};@var{stubfeature}@r{]}@dots{}
> +The stub supports or does not support each returned @var{stubfeature},
> +depending on the form of each @var{stubfeature} (see below for the
> +possible forms).
> +@item
> +An empty reply indicates that @samp{qSupported} is not recognized,
> +or that no features needed to be reported to @value{GDBN}.
Did you look at how this empty @item is typeset in the printed version
of the manual? I suspect it won't do what you want. Perhaps saying
"(@emph{empty})" explicitly will look better.
Other than that, I'm happy with the doco patch. Thanks!
next prev parent reply other threads:[~2006-06-13 18:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 19:53 Daniel Jacobowitz
2006-06-13 8:43 ` Nathan Sidwell
2006-06-13 13:07 ` Daniel Jacobowitz
2006-06-13 18:41 ` Eli Zaretskii
2006-06-13 18:43 ` Daniel Jacobowitz
2006-06-20 20:51 ` Daniel Jacobowitz
2006-06-21 3:14 ` Eli Zaretskii
2006-06-21 14:44 ` Daniel Jacobowitz
2006-06-13 13:38 ` Nathan Sidwell
2006-06-13 13:44 ` Daniel Jacobowitz
2006-06-13 13:46 ` Nathan Sidwell
2006-06-13 18:23 ` Eli Zaretskii [this message]
2006-06-13 18:35 ` Daniel Jacobowitz
2006-06-13 18:45 ` Eli Zaretskii
2006-06-13 19:16 ` Daniel Jacobowitz
2006-06-14 3:26 ` Eli Zaretskii
2006-06-20 20:42 ` Daniel Jacobowitz
2006-06-21 3:11 ` Eli Zaretskii
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=uk67k532m.fsf@gnu.org \
--to=eliz@gnu.org \
--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