public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches@sourceware.org, roland@redhat.com
Subject: Re: [patch] Fix for 'too much spew with "set verbose on"'
Date: Fri, 30 Jul 2010 18:09:00 -0000	[thread overview]
Message-ID: <83hbjgc06b.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTinY+o2nw0Ld5dq5Grkd05Oyc+ZTiDE=7N0XdDj_@mail.gmail.com>

> From: Paul Pluzhnikov <ppluzhnikov@google.com>
> Date: Fri, 30 Jul 2010 09:24:38 -0700
> Cc: Roland McGrath <roland@redhat.com>,        Paul Pluzhnikov <ppluzhnikov@google.com>
> 
> +Set whether to show processing of libthread_db."), _("\
> +Show whether to show processing of libthread_db."), _("\

"Show whether to show" sounds awkward.  How about

  "Show whether to be verbose during processing of libthread_db."

(and a similar change for the "Set" part)?

> +@kindex maint set show-libthread-db-processing
> +@kindex maint show show-libthread-db-processing
> +@cindex processing @code{libthread_db}
> +@item maint set show-libthread-db-processing
> +@itemx maint show show-libthread-db-processing
> +Control whether to show various internal events while searching for and
> +using @code{libthread_db}.  Use @code{ON} to enable, @code{OFF} to disable.
>  @end table

This part is fine.

Thanks.

       reply	other threads:[~2010-07-30 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTinY+o2nw0Ld5dq5Grkd05Oyc+ZTiDE=7N0XdDj_@mail.gmail.com>
2010-07-30 18:09 ` Eli Zaretskii [this message]
2010-07-30 18:18   ` Pedro Alves
2010-07-30 21:52     ` Paul Pluzhnikov
2010-07-30 22:14       ` Pedro Alves
2010-07-31  7:10       ` Eli Zaretskii
2010-07-31 15:41         ` Paul Pluzhnikov

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=83hbjgc06b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ppluzhnikov@google.com \
    --cc=roland@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).