From: Michael Snyder <msnyder@vmware.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] output remote protocol timestamps with "set debug remote"
Date: Sat, 22 Nov 2008 15:31:00 -0000 [thread overview]
Message-ID: <492709A5.7070505@vmware.com> (raw)
In-Reply-To: <20081118212221.GC3838@adacore.com>
Joel Brobecker wrote:
>> ... to enable timestamps, you do "set debug remote 2". level 1
>> still outputs the same as usual.
> [...]
>> WDYT?
>
> Sounds like a very useful feature to me. And since I was at it,
> I had a quick look at the code, which looks fine. I'm in favor.
Me too. My only question is, now that we're distinguishing
more than just "!=0", should we define some "verbosity levels"?
next prev parent reply other threads:[~2008-11-21 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 23:21 Pedro Alves
2008-11-19 11:37 ` Joel Brobecker
2008-11-22 15:31 ` Michael Snyder [this message]
2008-11-19 13:11 ` Daniel Jacobowitz
2008-11-19 14:07 ` Pedro Alves
2008-11-19 23:07 ` Daniel Jacobowitz
2008-11-20 1:46 ` 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=492709A5.7070505@vmware.com \
--to=msnyder@vmware.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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