On Thu, May 19, 2022 at 09:47:41AM -0400, Steve Dickson wrote: > > > On 5/14/22 11:23 PM, Trond Myklebust wrote: > >On Sat, 2022-05-14 at 21:59 -0400, J.Bruce Fields wrote: > >>On Sat, May 14, 2022 at 10:44:30AM -0400, trondmy@xxxxxxxxxx wrote: > >>>From: Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> > >>> > >>>The following patch set matches the kernel patches to allow access > >>>to > >>>the NFSv4.1 'dacl' and 'sacl' attributes. The current patches are > >>>very > >>>basic, adding support for encoding/decoding the new attributes only > >>>when > >>>the user specifies the '--dacl' or '--sacl' flags on the command > >>>line. > >> > >>Seems like a reasonable thing to do. > >> > >>I'd rather not be responsible for nfs4-acl-tools any longer, though. > >> > >>--b. > > > >I suspected that might be the case, but since you haven't made any > >announcements about anybody else taking over, I figured I'd start by > >sending these to you. > > > >So who should take over the nfs4-acl-tools maintainer role? Is that > >something Red Hat might be interested in doing, or should I volunteer > >to do it while we wait for somebody to get so fed up that they decide > >to step in? > > > Yeah... it probably something we should take over.... > > I'll add these to my todo list... Where does the upstream repo > live today? The Fedora rpm package points to my repo on linux-nfs. So you can just clone that and update the spec files to point at your repo. --b.
