From: Jeff Garzik <jeff@garzik.org>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [Patch 1/3] CLD: End-to-end verbosity
Date: Wed, 07 Apr 2010 00:36:32 -0400 [thread overview]
Message-ID: <4BBC0BD0.6080304@garzik.org> (raw)
In-Reply-To: <20100406213231.45939ce5@redhat.com>
On 04/06/2010 11:32 PM, Pete Zaitcev wrote:
> On Tue, 06 Apr 2010 10:40:33 -0400
> Jeff Garzik<jeff@garzik.org> wrote:
>
>> The debug levels are
>>
>> 0: key messages affecting server operation, only
>> 1: debugging output enabled, sans per-packet output
>> 2: debugging output enabled, including per-packet output
>
> The previous patch did just that:
> Why did you reject it?
That's a damned good question. I have no idea. Did I ever reply to
that patch? It looks like I fscked up and missed it?
Jeff
next prev parent reply other threads:[~2010-04-07 4:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 0:43 [Patch 1/3] CLD: End-to-end verbosity Pete Zaitcev
2010-04-06 14:40 ` Jeff Garzik
2010-04-07 3:32 ` Pete Zaitcev
2010-04-07 4:36 ` Jeff Garzik [this message]
2010-04-07 5:22 ` Pete Zaitcev
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=4BBC0BD0.6080304@garzik.org \
--to=jeff@garzik.org \
--cc=hail-devel@vger.kernel.org \
--cc=zaitcev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.