From: Eli Zaretskii <eliz@gnu.org>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org, roland@redhat.com
Subject: Re: [patch] Fix for 'too much spew with "set verbose on"'
Date: Sat, 31 Jul 2010 07:10:00 -0000 [thread overview]
Message-ID: <83bp9o2kma.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTimRceDgkDt88ZybuEdGYAPZq_=6dkEknP0yRaKU@mail.gmail.com>
> From: Paul Pluzhnikov <ppluzhnikov@google.com>
> Date: Fri, 30 Jul 2010 14:52:15 -0700
> Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>,
> roland@redhat.com
>
> --001636e1ef44fb5cc7048ca1de0a
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Fri, Jul 30, 2010 at 11:18 AM, Pedro Alves <pedro@codesourcery.com> wrote:
>
> > set debug libthread-db
>
> Good idea. Revised patch attached.
The doco and the help strings are okay with me.
Thanks.
next prev parent reply other threads:[~2010-07-31 7:10 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
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 [this message]
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=83bp9o2kma.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--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