From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: sergiodj@linux.vnet.ibm.com, gdb-patches@sourceware.org
Subject: Re: [RFA] Fix "show convenience" test
Date: Wed, 16 Sep 2009 17:08:00 -0000 [thread overview]
Message-ID: <83ab0uyfzk.fsf@gnu.org> (raw)
In-Reply-To: <200909161416.22783.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Wed, 16 Sep 2009 14:16:22 +0100
> Cc: gdb-patches@sourceware.org
>
> Hmm, I had already approved Paul's similar follow up patch at
> <http://sourceware.org/ml/gdb-patches/2009-04/msg00105.html>.
> I looks like it was waiting for a docs review.
Ouch! sorry about that (binary attachments tend to have this effect on
me ;-).
> The variable @code{$_siginfo} is bound to extra signal information
> -inspection (@pxref{extra signal information}).
> +inspection (@pxref{extra signal information}). Note that @code{$_siginfo}
> +could be empty. For example, it will be empty before you execute the
> +@code{run} command.
> @end table
A couple of comments:
. "the variable ... is bound to extra signal information inspection"
is awkward wording. "How about "contains extra signal
information"?
. I don't understand the note about it being ``empty''? What does
that mean, exactly, and why the example is talking about before
`run'? I could understand that it's empty if no signals were
delivered yet, but what does `run' has to do with this?
. Please leave two spaces between sentences, not one.
Thanks.
next prev parent reply other threads:[~2009-09-16 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 0:32 Sérgio Durigan Júnior
2009-09-16 13:16 ` Pedro Alves
2009-09-16 17:08 ` Eli Zaretskii [this message]
2009-09-17 16:37 ` Paul Pluzhnikov
2009-09-17 17:26 ` Eli Zaretskii
2009-09-17 17:57 ` Paul Pluzhnikov
2009-09-17 18:16 ` Pedro Alves
2009-09-17 18:29 ` Paul Pluzhnikov
2009-09-17 19:25 ` Joseph S. Myers
2009-09-17 19:52 ` Pedro Alves
2009-09-17 18:26 ` 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=83ab0uyfzk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=sergiodj@linux.vnet.ibm.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