From: Eli Zaretskii <eliz@gnu.org>
To: "Jim Blandy" <jimb@red-bean.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: Document conventions for terminating query/set packet names
Date: Fri, 05 May 2006 10:06:00 -0000 [thread overview]
Message-ID: <ufyjodbuq.fsf@gnu.org> (raw)
In-Reply-To: <8f2776cb0605041024u7c420707ie2fbff8a32ce32f0@mail.gmail.com> (jimb@red-bean.com)
> Date: Thu, 4 May 2006 10:24:22 -0700
> From: "Jim Blandy" <jimb@red-bean.com>
>
> Here's a revised patch:
>
> 2006-05-04 Jim Blandy <jimb@codesourcery.com>
>
> * gdb.texinfo (General Query Packets): Document conventions for
> terminating packet names, and their violations.
Fine with me, but...
> ! The name of a query or set packet should be separated from any
> ! parameters by a @samp{:}; the parameters themselves should be
> ! separated by @samp{,} or @samp{;}. Stubs must be careful to match the
> ! full packet name, in case packet names have common prefixes. The
> ! @code{qP} and @code{qL} packets predate these conventions; since we
> ! suspect they are in widespread use in places that are difficult to
> ! upgrade, new packets should not begin with @code{qP} or @code{qL}.
...perhaps the last sentence will be better placed in a footnote.
WDYT?
next prev parent reply other threads:[~2006-05-05 10:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 19:51 Jim Blandy
2006-05-03 19:56 ` Daniel Jacobowitz
2006-05-03 22:54 ` Jim Blandy
2006-05-04 1:57 ` Daniel Jacobowitz
2006-05-04 6:13 ` Jim Blandy
2006-05-04 12:38 ` Daniel Jacobowitz
2006-05-04 17:24 ` Jim Blandy
2006-05-05 10:06 ` Eli Zaretskii [this message]
2006-05-05 19:14 ` Jim Blandy
2006-05-05 19:15 ` Jim Blandy
2006-05-05 19:18 ` Jim Blandy
2006-05-05 21:49 ` Eli Zaretskii
2006-05-05 21:59 ` Jim Blandy
2006-05-05 22:09 ` Eli Zaretskii
2006-05-05 16:25 ` Daniel Jacobowitz
2006-05-09 20:41 ` Daniel Jacobowitz
2006-05-09 21:16 ` Andrew Cagney
2006-05-10 3:18 ` Eli Zaretskii
2006-05-14 17:09 ` Daniel Jacobowitz
2006-05-10 21:14 ` Jim Blandy
2006-05-04 15:55 ` 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=ufyjodbuq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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