From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: steved@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] nfs(5): Replace the term "netid" in mount option descriptions
Date: Tue, 23 Sep 2008 12:56:08 -0400 [thread overview]
Message-ID: <1222188968.7799.32.camel@localhost> (raw)
In-Reply-To: <20080923161636.5119.54434.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
On Tue, 2008-09-23 at 12:16 -0400, Chuck Lever wrote:
> Mike Eisler noted that the use of the term "netid" in the descriptions
> of the "proto=" option is not appropriate, since Linux does not allow
> "udp6" or "tcp6".
Why is it too late to add udp6/tcp6?
Cheers
Trond
next prev parent reply other threads:[~2008-09-23 16:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 16:16 [PATCH 0/2] nfs(5) updates Chuck Lever
[not found] ` <20080923161322.5119.20872.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 16:16 ` [PATCH 1/2] nfs(5): Replace the term "netid" in mount option descriptions Chuck Lever
2008-09-23 16:16 ` [PATCH 2/2] nfs(5): Clarify behavior of the mountproto= and proto= options Chuck Lever
[not found] ` <20080923161636.5119.54434.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 16:30 ` [PATCH 1/2] nfs(5): Replace the term "netid" in mount option descriptions Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRDC8wSA000000ca-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 16:46 ` Chuck Lever
2008-09-23 16:56 ` Trond Myklebust [this message]
2008-09-23 17:11 ` Chuck Lever
[not found] ` <76bd70e30809231011g5ed0cd11o6ccc06ab85f1a96c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[not found] ` <76bd70e30809231011g5ed0cd11o6ccc06ab85f1a96c-JsoAwUIsXouhRSP0FMvGiw@public.gmane.org m>
2008-09-23 19:04 ` Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRDFRaqb000000d0-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 19:55 ` Chuck Lever
2008-09-29 11:37 ` Steve Dickson
[not found] ` <20080923161641.5119.37034.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 16:32 ` [PATCH 2/2] nfs(5): Clarify behavior of the mountproto= and proto= options Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRD77bie000000cb-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 16:47 ` Chuck Lever
2008-09-23 16:41 ` Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRDSzbAU000000cd-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 16:55 ` Chuck Lever
2008-09-29 11:38 ` Steve Dickson
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=1222188968.7799.32.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox