All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Dsouza <kdsouza@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2] nfs4_getfacl: Add support to accept more paths
Date: Sat, 3 Feb 2018 21:10:41 +0530	[thread overview]
Message-ID: <CAA_-hQJMYG2y4a_6pEusdEy0obV3+dT_9uVe44C0FbdvkcUEPQ@mail.gmail.com> (raw)
In-Reply-To: <20180202211903.GB6635@fieldses.org>

On Sat, Feb 3, 2018 at 2:49 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
> Thanks, one nit:
>
> On Sat, Feb 03, 2018 at 02:03:31AM +0530, Kenneth Dsouza wrote:
>> Update man page with information for multiple file path support.
>>
>> Signed-off-by: Kenneth D'souza <kdsouza@redhat.com>
>> ---
>>  man/man1/nfs4_getfacl.1     |  7 ++++++-
>>  nfs4_getfacl/nfs4_getfacl.c | 18 +++++++++---------
>>  2 files changed, 15 insertions(+), 10 deletions(-)
>>
>> diff --git a/man/man1/nfs4_getfacl.1 b/man/man1/nfs4_getfacl.1
>> index fc092be..b556e1a 100644
>> --- a/man/man1/nfs4_getfacl.1
>> +++ b/man/man1/nfs4_getfacl.1
>> @@ -9,7 +9,7 @@
>>  nfs4_getfacl \- get NFSv4 file/directory access control lists
>>  .SH SYNOPSIS
>>  .B nfs4_getfacl [-H]
>> -.I file
>> +file ...
>>  .SH DESCRIPTION
>>  .B nfs4_getfacl
>>  will display the NFSv4 Access Control List (ACL) for
>> @@ -28,6 +28,7 @@ The output format for an NFSv4 file ACL, e.g., is:
>>  .RS
>>  .nf
>>
>> +# file: /somedir
>>  A::OWNER@:rwatTnNcCy
>>  A::alice@nfsdomain.org:rxtncy
>>  A::bob@nfsdomain.org:rwadtTnNcCy
>> @@ -42,6 +43,10 @@ In the example output above, the user
>> `alice@nfsdomain.org' has the equivalent
>>  of "read" and "execute" permissions, `bob@nfsdomain.org' has "read" and
>>  "write", and both `GROUP@' and `EVERYONE@' have "read".
>>
>> +.B nfs4_getfacl
>> +reads a list of files from standard input. The ACL listings of
>> +multiple files are separated by blank lines.
>> +
>
> The list of files comes from the command line arguments, not standard
> input, right?
   Yes

> I've modified the man page slightly but otherwise taken your patch
> unchanged; result is pushed out to git now, let me know if it looks OK
> to you.
>
> --b.

 It looks good. Thank you for fixing it.

      reply	other threads:[~2018-02-03 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-02 20:33 [PATCH v2] nfs4_getfacl: Add support to accept more paths Kenneth Dsouza
2018-02-02 21:19 ` J. Bruce Fields
2018-02-03 15:40   ` Kenneth Dsouza [this message]

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=CAA_-hQJMYG2y4a_6pEusdEy0obV3+dT_9uVe44C0FbdvkcUEPQ@mail.gmail.com \
    --to=kdsouza@redhat.com \
    --cc=bfields@fieldses.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.