From: Eli Zaretskii <eliz@gnu.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: Document conventions for terminating query/set packet names
Date: Fri, 05 May 2006 21:49:00 -0000 [thread overview]
Message-ID: <uk690b0rn.fsf@gnu.org> (raw)
In-Reply-To: <vt2ejz8p9fk.fsf@theseus.home.> (message from Jim Blandy on Fri, 05 May 2006 12:18:23 -0700)
> Cc: gdb-patches@sourceware.org
> From: Jim Blandy <jimb@codesourcery.com>
> Date: Fri, 05 May 2006 12:18:23 -0700
>
> (Argh. In Emacs, the command to insert '@code{}' in a texinfo-mode
> buffer is C-c C-c c. But in a mail-mode buffer, C-c C-c is 'send
> message'...)
Yeah, was bitten by that one, too.
> We could replace that last sentence with:
>
> New packets should not begin with @samp{qP} or @samp{qL}.@footnote{The
> @samp{qP} and @samp{qL} packets predate these conventions, and don't
> have any terminator for the packet name; we suspect they are in
> widespread use in places that are difficult to upgrade.}
>
> if you prefer.
Yes, that's what I had in mind, sorry it wasn't immediately clear.
But please start the footnote _before_ the period, and add the period
after the right brace that ends the footnote.
next prev parent reply other threads:[~2006-05-05 21:49 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
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 [this message]
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=uk690b0rn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@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