From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [RFA] info break/watch/trace use get_number_or_range, take two
Date: Tue, 22 Feb 2011 18:48:00 -0000 [thread overview]
Message-ID: <83wrkrsyhy.fsf@gnu.org> (raw)
In-Reply-To: <4D640113.2000800@vmware.com>
> Date: Tue, 22 Feb 2011 10:31:47 -0800
> From: Michael Snyder <msnyder@vmware.com>
> CC: Pedro Alves <pedro@codesourcery.com>,
> "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>
> Eli Zaretskii wrote:
> >> From: Pedro Alves <pedro@codesourcery.com>
> >> Date: Tue, 22 Feb 2011 09:16:51 +0000
> >> Cc: Michael Snyder <msnyder@vmware.com>
> >>
> >>> add_info ("breakpoints", breakpoints_info, _("\
> >>> -Status of user-settable breakpoints, or breakpoint number NUMBER.\n\
> >>> +Status of user-settable breakpoints listed, or all breakpoints if no argument.\n\
> >> "listed" doesn't sound obviously referring to the spec
> >> you pass as argument to the command. "listed where? the
> >> command itself is printing a list." was my thought. Is
> >> there any other way to spell that?
> >
> > How about just losing the "listed" part? What important information
> > does it convey in this context?
>
> What wording do you suggest?
How about
Status of specified breakpoints (all user-settable breakpoints if no argument).
?
next prev parent reply other threads:[~2011-02-22 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 23:00 Michael Snyder
2011-02-22 9:27 ` Pedro Alves
2011-02-22 10:56 ` Eli Zaretskii
2011-02-22 18:32 ` Michael Snyder
2011-02-22 18:48 ` Eli Zaretskii [this message]
2011-02-22 19:02 ` Michael Snyder
2011-02-22 18:31 ` Michael Snyder
2011-02-22 11:49 ` Eli Zaretskii
2011-02-22 18:33 ` Michael Snyder
2011-02-22 18:41 ` Pedro Alves
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=83wrkrsyhy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@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