From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/5] new statd [take 1]
Date: Sun, 16 Aug 2009 16:35:02 -0400 [thread overview]
Message-ID: <4A886D76.1040404@RedHat.com> (raw)
In-Reply-To: <20090804180334.21944.64404.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
On 08/04/2009 02:06 PM, Chuck Lever wrote:
> Hi Steve-
>
> Here are some man page patches and the one big patch that adds the new
> IPv6-capable statd. I'd like to start socializing these changes to
> expedite the new statd into mainline nfs-utils.
>
> ---
>
> Chuck Lever (5):
> nfs(5): update nfs(5) with details about IPv6 support
> nfs-utils: introduce new statd implementation
I 'm waited on these to allow the new statd implementation to shake
out a bit port...
> statd: change default state dir to /var/lib/nfs/statd
I would like to get an 'ACK' from other distros on this one since
they could depending on what happens today...
> nfs(5): Remove trailing blanks
> nfs(5): Add description of lookupcache mount option
I committed these
steved.
next prev parent reply other threads:[~2009-08-16 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 18:06 [PATCH 0/5] new statd [take 1] Chuck Lever
[not found] ` <20090804180334.21944.64404.stgit-RytpoXr2tKZ9HhUboXbp9zCvJB+x5qRC@public.gmane.org>
2009-08-04 18:06 ` [PATCH 1/5] nfs(5): Add description of lookupcache mount option Chuck Lever
2009-08-04 18:06 ` [PATCH 2/5] nfs(5): Remove trailing blanks Chuck Lever
2009-08-04 18:07 ` [PATCH 3/5] statd: change default state dir to /var/lib/nfs/statd Chuck Lever
2009-08-04 18:07 ` [PATCH 5/5] NFS man page: update nfs(5) with details about IPv6 support Chuck Lever
2009-08-05 13:51 ` [PATCH 0/5] new statd [take 1] Chuck Lever
2009-08-05 17:18 ` J. Bruce Fields
2009-08-16 20:35 ` Steve Dickson [this message]
[not found] ` <4A886D76.1040404-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-08-17 13:57 ` Chuck Lever
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=4A886D76.1040404@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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