linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Fields <bfields@fieldses.org>
To: Marc Eshel <eshel@us.ibm.com>
Cc: Libtirpc-devel Mailing List
	<libtirpc-devel@lists.sourceforge.net>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
	linux-nfs-owner@vger.kernel.org
Subject: Re: your mail
Date: Mon, 23 Jul 2018 16:33:06 -0400	[thread overview]
Message-ID: <20180723203306.GA27515@fieldses.org> (raw)
In-Reply-To: <OFA232E502.EADD3A82-ON882582D3.00667F9D-882582D3.0066E0F8@notes.na.collabserv.com>

On Mon, Jul 23, 2018 at 11:43:55AM -0700, Marc Eshel wrote:
> Do you know of any plans to add  IETF RFC 8276 - File System Extended 
> Attributes in NFSv4 to the Linux NFS Client or Server?

I don't understand why you proposed new protocol without having anyone
in mind to implement it on the platforms where you need it.

Matt Benjamin's expressed interest in the past, but he's got a lot on
his plate so I don't know that we can count on that.

--b.

  reply	other threads:[~2018-07-23 21:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 15:25 [PATCH V4] xdrstdio_create buffers do not output encoded values on ppc Steve Dickson
2018-07-11 16:05 ` Steve Dickson
2018-07-11 16:38   ` Trond Myklebust
2018-07-11 18:06     ` [Libtirpc-devel] " Chuck Lever
2018-07-11 18:19       ` Trond Myklebust
2018-07-11 20:42         ` Chuck Lever
2018-07-11 20:58           ` Trond Myklebust
2018-07-18 18:32 ` Steve Dickson
2018-07-23 18:43 ` Marc Eshel
2018-07-23 20:33   ` Bruce Fields [this message]
     [not found] ` <OFA232E502.EADD3A82-ON882582D3.00667F9D-882582D3.0066E08D@LocalDomain>
2018-07-23 18:45   ` IETF RFC 8276 - File System Extended Attributes in NFSv4 Marc Eshel

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=20180723203306.GA27515@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=eshel@us.ibm.com \
    --cc=libtirpc-devel@lists.sourceforge.net \
    --cc=linux-nfs-owner@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).