linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	linux-ext4@vger.kernel.org, xfs@oss.sgi.com,
	lkml <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
	linux-cifs@vger.kernel.org, Linux API <linux-api@vger.kernel.org>,
	Dave Chinner <david@fromorbit.com>,
	Christoph Hellwig <hch@infradead.org>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Jeff Layton <jlayton@poochiereds.net>,
	Andreas Dilger <adilger@dilger.ca>
Subject: Re: getrichacl(1) man page review comments
Date: Sun, 07 Feb 2016 19:16:40 +0100	[thread overview]
Message-ID: <1505883.O2zQ69A2Zb@merkaba> (raw)
In-Reply-To: <56B77139.4080209@gmail.com>

Am Sonntag, 7. Februar 2016, 17:30:49 CET schrieb Michael Kerrisk (man-pages):
> Hello Andreas,
> 
> Here, some comments on the getrichacl(1) page.

I know that the command names are based on setfacl and getfacl. But sometimes 
I still wonder about these names. They just don´t fit.

Its chsomething for changing things in Unix traditionally – chown, chmod, 
chattr, chage chsh, you name it –, but there is nothing for querying things. 
So I get where this is coming from, yet I always found setfacl and getfacl 
command names cumbersome.

Sorry, for posting here instead of a previous richacl implementation patchset. 
I fully appreciate that it may be too late to change anything regarding 
command names. Also considering usermod and groupmod the command naming in 
Unix / Linux appears to be a big mess anyway.

Thanks,
-- 
Martin

  reply	other threads:[~2016-02-07 18:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 16:28 RichACLs man-pages review Michael Kerrisk (man-pages)
     [not found] ` <56B770B6.7040803-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-07 16:29   ` Michael Kerrisk (man-pages)
2016-02-07 16:30   ` getrichacl(1) man page review comments Michael Kerrisk (man-pages)
2016-02-07 18:16     ` Martin Steigerwald [this message]
     [not found]     ` <56B77139.4080209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-14 21:30       ` Michael Kerrisk (man-pages)
2016-02-07 16:31   ` setrichacl(1) " Michael Kerrisk (man-pages)
2016-02-14 21:29     ` Michael Kerrisk (man-pages)
2016-02-07 16:35   ` richacl(7) " Michael Kerrisk (man-pages)
     [not found]     ` <56B77262.7090107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-10 19:34       ` J. Bruce Fields
2016-02-12 22:25     ` Andreas Gruenbacher
     [not found]       ` <CAHc6FU5__xbKm4mg8+fK_ZW5ZYsDoQcYBBvQg573Eq4ERDsROw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-14 21:27         ` Michael Kerrisk (man-pages)
2016-02-14 23:12           ` Andreas Gruenbacher
2016-02-15 10:25             ` Michael Kerrisk (man-pages)
     [not found]               ` <56C1A788.9020008-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-15 11:35                 ` Andreas Gruenbacher
     [not found]                   ` <CAHc6FU69k2uRXjSSS+9K0cXzFs74DPsz6DDv8GN=hmh7RpPA-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-15 14:15                     ` Michael Kerrisk (man-pages)
2016-02-14 21:31         ` Michael Kerrisk (man-pages)
     [not found]           ` <56C0F23C.7030902-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-20 16:37             ` Andreas Gruenbacher
     [not found]               ` <CAHc6FU4CCrcrA6=oCiq2A5rGd9CCGELaTZq6tGpmd2jcV_Zp4A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-21 21:01                 ` Michael Kerrisk (man-pages)
2016-02-21 21:40                 ` Michael Kerrisk (man-pages)
     [not found]                   ` <56CA2EEB.9080504-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-22 14:46                     ` Andreas Gruenbacher
2016-02-23 10:16                       ` Michael Kerrisk (man-pages)
     [not found]                         ` <56CC3174.2060207-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-23 10:28                           ` Andreas Gruenbacher
2016-02-28 22:11                           ` Andreas Gruenbacher
2016-02-23 10:58                       ` Michael Kerrisk (man-pages)
2016-02-23 11:14                         ` Andreas Gruenbacher
     [not found]                         ` <56CC3B4A.7070204-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-23 15:09                           ` Andreas Gruenbacher
     [not found]                             ` <CAHc6FU67LnV7-roofFe1y_uTfvgwonRZimyu7Wn1CDRzwHZJSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-23 19:01                               ` Andreas Gruenbacher

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=1505883.O2zQ69A2Zb@merkaba \
    --to=martin@lichtvoll.de \
    --cc=adilger@dilger.ca \
    --cc=agruenba@redhat.com \
    --cc=anna.schumaker@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=jlayton@poochiereds.net \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=trond.myklebust@primarydata.com \
    --cc=xfs@oss.sgi.com \
    /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).