From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: GDB manual: document tracepoint packets
Date: Mon, 21 Nov 2005 04:47:00 -0000 [thread overview]
Message-ID: <uu0e7xgq0.fsf@gnu.org> (raw)
In-Reply-To: <8f2776cb0511192143h21c1d647yc766a09e1bcc3184@mail.gmail.com> (message from Jim Blandy on Sat, 19 Nov 2005 21:43:58 -0800)
> Date: Sat, 19 Nov 2005 21:43:58 -0800
> From: Jim Blandy <jimb@red-bean.com>
> Cc: gdb-patches@sources.redhat.com
>
> > > + @item OK
> > > + The packet was understood and carried out.
> > > + @item
> >
> > Does this @item really need to be empty? If so, why, and what do we
> > want to appear here in print?
>
> It does. This appears as a pair of matched single quotes enclosing
> nothing in both the Info and printable manuals. The remote stub
> returns an empty packet to indicate that it didn't understand the
> command. Blank @items are used elsewhere in the manual for this
> purpose.
Should we perhaps say "(empty)" to prevent readers from thinking it's
a typo?
next prev parent reply other threads:[~2005-11-20 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 13:12 Jim Blandy
2005-11-20 14:57 ` Eli Zaretskii
2005-11-20 16:08 ` Jim Blandy
2005-11-20 19:27 ` Jim Blandy
2005-11-21 4:47 ` Eli Zaretskii [this message]
2005-11-21 4:52 ` Jim Blandy
2005-11-21 7:29 ` 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=uu0e7xgq0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@red-bean.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