From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Support IPv6 in umount.nfs command
Date: Tue, 17 Feb 2009 16:27:45 -0500 [thread overview]
Message-ID: <499B2BD1.2030306@RedHat.com> (raw)
In-Reply-To: <20090128225938.21484.82096.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
Chuck Lever wrote:
> Hi Steve-
>
> The first patch in this series is a simple update to .gitignore.
>
> The following patches implement support for IPv6 addresses in the
> umount.nfs command.
>
> I think it would be prudent to stop after this set, and let the
> extensive changes I've submitted so far soak a little bit. These
> probably won't see wide-ranging use until after the next release of
> nfs-utils, I'm guessing.
>
> Given the problems that arose after the last nfs-utils release, I
> think this might be a good stopping point until after the next
> nfs-utils release. By then, I might even have full support completed
> for IPv6 in rpc.statd and sm-notify.
>
Committed...
steved.
prev parent reply other threads:[~2009-02-17 21:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 23:07 [PATCH 0/4] Support IPv6 in umount.nfs command Chuck Lever
[not found] ` <20090128225938.21484.82096.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2009-01-28 23:07 ` [PATCH 1/4] nfs-utils: git should ignore cscope.* files Chuck Lever
2009-01-28 23:07 ` [PATCH 2/4] umount.nfs command: Add an AF_INET6-capable version of nfs_call_unmount() Chuck Lever
2009-01-28 23:07 ` [PATCH 3/4] umount.nfs command: Support AF_INET6 server addresses Chuck Lever
2009-01-28 23:07 ` [PATCH 4/4] umount command: remove do_nfs_umount23 function Chuck Lever
2009-02-17 21:27 ` Steve Dickson [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=499B2BD1.2030306@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