From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: lsf10-pc@lists.linuxfoundation.org,
"linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Ext4 Developers List" <linux-ext4@vger.kernel.org>
Subject: [LSF/VM TOPIC] Re: [Lsf10-pc] Rich-acl discussion for Linus Storage and Filesystem summit
Date: Wed, 03 Mar 2010 19:39:06 +0530 [thread overview]
Message-ID: <878wa9o5tp.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1267607061.15025.11.camel@mulgrave.site>
On Wed, 03 Mar 2010 14:34:21 +0530, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Tue, 2010-03-02 at 10:16 -0500, Trond Myklebust wrote:
> > On Tue, 2010-03-02 at 20:28 +0530, Aneesh Kumar K.V wrote:
> > > Hi,
> > >
> > > Suggestion for discussion at LSF summit:
> > >
> > > Rich-acl patches posted at
> > > http://article.gmane.org/gmane.comp.file-systems.ext4/17414 helps in
> > > defining a new acl format for Linux that can interoperate better with
> > > NFSv4 acl and CIFS acl. I would like have a discussion on the new acl
> >
> > What about NTFS?
> >
> > > format, rules regarding how to handle file mode changes and acl
> > > values. Also how to handle uid to nfs name@domain mapping
> > >
> > > -aneesh
> >
> > I very much second this proposal. We've been spinning our wheels on the
> > issue of support for non-posix draft acls for far too long.
>
> So could we take the proposal to the relevant list to see who else wants
> to talk about it and whether any of the ground work can be covered
> beforehand?
>
Adding fsdevel, ext4 list. samba will also be interested, but that is
subscriber only list
-aneesh
parent reply other threads:[~2010-03-03 14:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1267607061.15025.11.camel@mulgrave.site>]
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=878wa9o5tp.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf10-pc@lists.linuxfoundation.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).