From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [Patch 1/7] tabled: make two dump displays uniform
Date: Tue, 6 Apr 2010 12:29:31 -0600 [thread overview]
Message-ID: <20100406122931.1ba7a78d@redhat.com> (raw)
In-Reply-To: <4BBB6815.7040606@garzik.org>
On Tue, 06 Apr 2010 12:57:57 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> applied, thanks. I will endeavor to make the stats dump more like nfs4d
> in the future, FWIW.
I was going to look into it too, but there's now some stuff
I urgently need to address in Darcy's report on tabled's faults.
So I only wrote nfs4 into the endless TODO.
-- Pete
prev parent reply other threads:[~2010-04-06 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 1:51 [Patch 1/7] tabled: make two dump displays uniform Pete Zaitcev
2010-04-02 17:27 ` Jeff Garzik
2010-04-02 18:23 ` Pete Zaitcev
2010-04-06 16:57 ` Jeff Garzik
2010-04-06 18:29 ` Pete Zaitcev [this message]
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=20100406122931.1ba7a78d@redhat.com \
--to=zaitcev@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.org \
/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).