From: James Morris Subject: Re: [PATCH v8 00/41] Richacls Date: Tue, 6 Oct 2015 20:49:04 +1100 (AEDT) Message-ID: References: <1443391772-10171-1-git-send-email-agruenba@redhat.com> <20151004062313.GA20212@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: Andreas Gruenbacher , Alexander Viro , "Theodore Ts'o" , Andreas Dilger , "J. Bruce Fields" , Jeff Layton , Trond Myklebust , Anna Schumaker , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org, linux-api@vger.kernel.org To: Christoph Hellwig Return-path: In-Reply-To: <20151004062313.GA20212@infradead.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Sat, 3 Oct 2015, Christoph Hellwig wrote: > On Mon, Sep 28, 2015 at 12:08:51AM +0200, Andreas Gruenbacher wrote: > > Hello, > > > > here's another update of the richacl patch queue. At this stage, I would > > like to ask for final feedback so that the core and ext4 code (patches > > 1-19) can be merged in the 4.4 merge window. The nfsd and nfs code should > > then go through the respective maintainer trees. > > Now way in this form even if everyone agrees we should have these > bastard ACLs. I certainly disagree. > Where is the rationale for them? This url doesn't work: http://acl.bestbits.at/richacl/ -- James Morris