From: Tom Haynes <thomas.haynes@primarydata.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Christoph Hellwig <hch@infradead.org>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: default NFSv4.2 to on
Date: Wed, 11 Feb 2015 10:12:31 -0800 [thread overview]
Message-ID: <20150211181231.GA80012@kitty.kitty> (raw)
In-Reply-To: <20150211145413.GC25696@fieldses.org>
On Wed, Feb 11, 2015 at 09:54:13AM -0500, J. Bruce Fields wrote:
>
> I agree there's a documentation and marketing problem: it would simplify
> communication with users if "this server supports 4.2" reliably meant
> support for some minimum list of features.
>
The "marketing" message over NFSv4.2 has been pretty consistent - everything
is optional and a fully compliant server can return not supported for
every new feature. I.e., a NFSv4.2 server is pretty simple if you have
an existing NFSv4.1 server.
next prev parent reply other threads:[~2015-02-11 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 16:15 [PATCH] nfsd: default NFSv4.2 to on J. Bruce Fields
2015-02-11 12:37 ` Christoph Hellwig
2015-02-11 14:12 ` J. Bruce Fields
2015-02-11 14:16 ` Christoph Hellwig
2015-02-11 14:54 ` J. Bruce Fields
2015-02-11 15:15 ` Trond Myklebust
2015-02-11 15:32 ` J. Bruce Fields
2015-02-11 18:12 ` Tom Haynes [this message]
2015-02-11 18:27 ` J. Bruce Fields
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=20150211181231.GA80012@kitty.kitty \
--to=thomas.haynes@primarydata.com \
--cc=bfields@fieldses.org \
--cc=hch@infradead.org \
--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