From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: [rfc/remote] Tell remote stubs which signals are boring
Date: Thu, 26 Oct 2006 21:16:00 -0000 [thread overview]
Message-ID: <20061026211624.GA21239@nevyn.them.org> (raw)
In-Reply-To: <m33b9adbpe.fsf@codesourcery.com>
On Thu, Oct 26, 2006 at 02:11:25PM -0700, Jim Blandy wrote:
> (Thanks, Mark, for asking about this!) Please don't use a space to
> mark the end of the packet name. At the moment, the remote protocol
> documentation uses spaces just for clarity; if they become meaningful,
> then we're going to have to revamp our manual notation --- again.
>
> The text in "Overview" suggests using ',', ';', or ':'.
Typo in the documentation. The top of the general query packets page
is quite clear that it ought to be a colon, and so it is. Thanks.
> > Each listed SIGNAL, using the same signal numbering used in
>
> I'd like to see "and syntax" added here --- I assume that's so?
How much syntax is there to a single number?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-26 21:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 21:24 Daniel Jacobowitz
2006-10-25 21:33 ` Mark Kettenis
2006-10-25 22:56 ` David Daney
2006-10-26 1:40 ` Daniel Jacobowitz
2006-10-26 7:02 ` Eli Zaretskii
2006-10-26 6:57 ` Eli Zaretskii
2006-10-26 12:18 ` Daniel Jacobowitz
2006-10-26 15:01 ` Eli Zaretskii
2006-10-26 15:10 ` Daniel Jacobowitz
2006-10-26 15:18 ` Eli Zaretskii
2006-10-26 15:22 ` Daniel Jacobowitz
2006-10-26 15:27 ` Mark Kettenis
2006-10-26 15:37 ` Daniel Jacobowitz
2006-10-26 17:54 ` Mark Kettenis
2006-10-26 21:11 ` Jim Blandy
2006-10-26 21:16 ` Daniel Jacobowitz [this message]
2006-10-26 21:28 ` Jim Blandy
2006-10-26 21:37 ` Daniel Jacobowitz
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=20061026211624.GA21239@nevyn.them.org \
--to=drow@false.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