From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Andreas Gruenbacher <agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
"J. Bruce Fields"
<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Linux API <linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Dave Chinner <david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org>,
Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Anna Schumaker
<anna.schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>,
Trond Myklebust
<trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>,
Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>,
Andreas Dilger <adilger-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org>
Subject: Re: getrichacl(1) man page review comments
Date: Sun, 14 Feb 2016 22:30:39 +0100 [thread overview]
Message-ID: <56C0F1FF.3050003@gmail.com> (raw)
In-Reply-To: <56B77139.4080209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi Andreas,
Here's a few more comments on the current getrichacl(1) page
that I fetched from the git repo.
> .\"
> .\" RichACL Manual Pages
> .\"
> .\" Copyright (C) 2015,2016 Red Hat, Inc.
> .\" Written by Andreas Gruenbacher <agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> .\" This is free documentation; you can redistribute it and/or
> .\" modify it under the terms of the GNU General Public License as
> .\" published by the Free Software Foundation; either version 2 of
> .\" the License, or (at your option) any later version.
> .\"
> .\" The GNU General Public License's references to "object code"
> .\" and "executables" are to be interpreted as the output of any
> .\" document formatting or typesetting system, including
> .\" intermediate and printed output.
> .\"
> .\" This manual is distributed in the hope that it will be useful,
> .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
> .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> .\" GNU General Public License for more details.
> .\"
> .\" You should have received a copy of the GNU General Public
> .\" License along with this manual. If not, see
> .\" <http://www.gnu.org/licenses/>.
> .\"
> .TH GETRICHACL 7 2015-09-01 "Linux" "Rich Access Control Lists"
>
> .SH NAME
> getrichacl \- Get Rich Access Control Lists
>
> .SH SYNOPSIS
> .B getrichacl
> .RI [ option "]... [" file ]...
>
> .SH DESCRIPTION
> For each file,
> .B getrichacl
> displays the file name and the file's Rich Access Control List (RichACL).
>
> The output format of
> .B getrichacl
> is as follows:
Add a blank line here.
> .fam C
> .RS
> .nf
> 1: file:
> 2: flags:a
> 3: owner:rwp-------------::mask
> 4: group:r-p-------------::mask
> 5: other:r---------------::mask
> 6: owner@:rwp-------------::allow
> 7: user:foo:r-p-------------::allow
> 8: group@:r-p-------------::allow
> 9: group:bar:r-p-------------::allow
> 10: everyone@:r---------------::allow
> 11:
> .fi
> .RE
> .fam T
>
> Line 1 contains the file name, followed by a colon.
>
> Line 2 contains the ACL flags. This line is omitted if no flags are set.
>
> Lines 3--5 indicate the owner, group, and other file masks, which are only
> shown if the \fB\-\-raw\fR option is specified.
>
> Lines 6--10 indicate different ACL entries for the file owner
> .RB ( owner@ ),
> user \fIfoo\fR, the owning group
> .RB ( group@ ),
> group \fIbar\fR, and for everyone
> .RB ( everyone@ ).
>
> A blank line follows at the end.
>
> The default output format uses the single-letter forms of flags and
> permissions, identifiers of ACL entries are right justified, permissions are
> vertically aligned, and permissions which are always granted
> .RB ( read_attributes ", " read_acl ", " synchronize )
> are omitted. See the
> .BR richacl (7)
> manual page for the defined flags and permissions.
>
> By default,
> .B getrichacl
> displays the effective permissions remaining after applying the file masks to
> the ACL. The file masks and underlying NFSv4 ACL can be displayed with the
> \fB\-\-raw\fR option.
>
> When
> .B getrichacl
> is used on a file that does not have a RichACL or on a filesystem that does not
> support RichACLs,
> .B getrichacl
Replace the previous line with "it".
> displays the access permissions defined by the traditional file permission bits
> as a RichACL. When
> .B getrichacl
> is used on a file that has a POSIX ACL (see
> .BR acl (5)),
> it prints an error message.
>
> .SH OPTIONS
> .TP
> \fB\-\-long\fR, \fB\-l\fR
> Display access masks and flags in their long form.
> .TP
> \fB\-\-full\fR
> Also show permissions which are always implicitly allowed.
> .TP
> \fB\-\-raw\fR
> Show ACLs as stored on the file system, including the file masks. Implies
> \fB\-\-full\fR.
> .TP
> \fB\-\-unaligned\fR
> Do not align ACL entries or pad missing permissions with '-'.
> .TP
> \fB\-\-numeric-ids\fR
> Display numeric user and group IDs instead of names.
> .TP
> \fB\-\-access\fR [=\fIuser\fR[:\fIgroup\fR:...]}, \fB\-a\fR[\fIuser\fR[:\fIgroup\fR:...]}
> Instead of showing the ACL, show which permissions the user running the command
> has for the specified file(s). When \fIuser\fR is specified, show which
> permissions the specified user has instead. If \fIuser\fR is followed by a
> colon and a (possibly empty) list of groups, assume that \fIuser\fR is a member
> in the specified groups; otherwise,
> .BR getgrouplist (3)
> is used to determine the groups \fIuser\fR is a member in.
s/in/of/
> .TP
> \fB\-\-version\fR, \fB\-v\fR
> Display the version of
> .B getrichacl
> and exit.
> .TP
> \fB\-\-help\fR, \fB\-h\fR
> Display command-line usage help text.
>
> .SH AUTHOR
> Written by Andreas Grünbacher <agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>.
>
> Please send your bug reports, suggested features and comments to the above address.
>
> .SH CONFORMING TO
> Rich Access Control Lists are Linux-specific.
>
> .SH SEE ALSO
> .BR richacl (7),
> .BR setrichacl (1)
Cheers,
Michael
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: mtk.manpages@gmail.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, 14 Feb 2016 22:30:39 +0100 [thread overview]
Message-ID: <56C0F1FF.3050003@gmail.com> (raw)
In-Reply-To: <56B77139.4080209@gmail.com>
Hi Andreas,
Here's a few more comments on the current getrichacl(1) page
that I fetched from the git repo.
> .\"
> .\" RichACL Manual Pages
> .\"
> .\" Copyright (C) 2015,2016 Red Hat, Inc.
> .\" Written by Andreas Gruenbacher <agruenba@redhat.com>
> .\" This is free documentation; you can redistribute it and/or
> .\" modify it under the terms of the GNU General Public License as
> .\" published by the Free Software Foundation; either version 2 of
> .\" the License, or (at your option) any later version.
> .\"
> .\" The GNU General Public License's references to "object code"
> .\" and "executables" are to be interpreted as the output of any
> .\" document formatting or typesetting system, including
> .\" intermediate and printed output.
> .\"
> .\" This manual is distributed in the hope that it will be useful,
> .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
> .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> .\" GNU General Public License for more details.
> .\"
> .\" You should have received a copy of the GNU General Public
> .\" License along with this manual. If not, see
> .\" <http://www.gnu.org/licenses/>.
> .\"
> .TH GETRICHACL 7 2015-09-01 "Linux" "Rich Access Control Lists"
>
> .SH NAME
> getrichacl \- Get Rich Access Control Lists
>
> .SH SYNOPSIS
> .B getrichacl
> .RI [ option "]... [" file ]...
>
> .SH DESCRIPTION
> For each file,
> .B getrichacl
> displays the file name and the file's Rich Access Control List (RichACL).
>
> The output format of
> .B getrichacl
> is as follows:
Add a blank line here.
> .fam C
> .RS
> .nf
> 1: file:
> 2: flags:a
> 3: owner:rwp-------------::mask
> 4: group:r-p-------------::mask
> 5: other:r---------------::mask
> 6: owner@:rwp-------------::allow
> 7: user:foo:r-p-------------::allow
> 8: group@:r-p-------------::allow
> 9: group:bar:r-p-------------::allow
> 10: everyone@:r---------------::allow
> 11:
> .fi
> .RE
> .fam T
>
> Line 1 contains the file name, followed by a colon.
>
> Line 2 contains the ACL flags. This line is omitted if no flags are set.
>
> Lines 3--5 indicate the owner, group, and other file masks, which are only
> shown if the \fB\-\-raw\fR option is specified.
>
> Lines 6--10 indicate different ACL entries for the file owner
> .RB ( owner@ ),
> user \fIfoo\fR, the owning group
> .RB ( group@ ),
> group \fIbar\fR, and for everyone
> .RB ( everyone@ ).
>
> A blank line follows at the end.
>
> The default output format uses the single-letter forms of flags and
> permissions, identifiers of ACL entries are right justified, permissions are
> vertically aligned, and permissions which are always granted
> .RB ( read_attributes ", " read_acl ", " synchronize )
> are omitted. See the
> .BR richacl (7)
> manual page for the defined flags and permissions.
>
> By default,
> .B getrichacl
> displays the effective permissions remaining after applying the file masks to
> the ACL. The file masks and underlying NFSv4 ACL can be displayed with the
> \fB\-\-raw\fR option.
>
> When
> .B getrichacl
> is used on a file that does not have a RichACL or on a filesystem that does not
> support RichACLs,
> .B getrichacl
Replace the previous line with "it".
> displays the access permissions defined by the traditional file permission bits
> as a RichACL. When
> .B getrichacl
> is used on a file that has a POSIX ACL (see
> .BR acl (5)),
> it prints an error message.
>
> .SH OPTIONS
> .TP
> \fB\-\-long\fR, \fB\-l\fR
> Display access masks and flags in their long form.
> .TP
> \fB\-\-full\fR
> Also show permissions which are always implicitly allowed.
> .TP
> \fB\-\-raw\fR
> Show ACLs as stored on the file system, including the file masks. Implies
> \fB\-\-full\fR.
> .TP
> \fB\-\-unaligned\fR
> Do not align ACL entries or pad missing permissions with '-'.
> .TP
> \fB\-\-numeric-ids\fR
> Display numeric user and group IDs instead of names.
> .TP
> \fB\-\-access\fR [=\fIuser\fR[:\fIgroup\fR:...]}, \fB\-a\fR[\fIuser\fR[:\fIgroup\fR:...]}
> Instead of showing the ACL, show which permissions the user running the command
> has for the specified file(s). When \fIuser\fR is specified, show which
> permissions the specified user has instead. If \fIuser\fR is followed by a
> colon and a (possibly empty) list of groups, assume that \fIuser\fR is a member
> in the specified groups; otherwise,
> .BR getgrouplist (3)
> is used to determine the groups \fIuser\fR is a member in.
s/in/of/
> .TP
> \fB\-\-version\fR, \fB\-v\fR
> Display the version of
> .B getrichacl
> and exit.
> .TP
> \fB\-\-help\fR, \fB\-h\fR
> Display command-line usage help text.
>
> .SH AUTHOR
> Written by Andreas Grünbacher <agruenba@redhat.com>.
>
> Please send your bug reports, suggested features and comments to the above address.
>
> .SH CONFORMING TO
> Rich Access Control Lists are Linux-specific.
>
> .SH SEE ALSO
> .BR richacl (7),
> .BR setrichacl (1)
Cheers,
Michael
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Linux API <linux-api@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>,
lkml <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com, "J. Bruce Fields" <bfields@fieldses.org>,
mtk.manpages@gmail.com, linux-fsdevel@vger.kernel.org,
Jeff Layton <jlayton@poochiereds.net>,
linux-ext4@vger.kernel.org,
Anna Schumaker <anna.schumaker@netapp.com>
Subject: Re: getrichacl(1) man page review comments
Date: Sun, 14 Feb 2016 22:30:39 +0100 [thread overview]
Message-ID: <56C0F1FF.3050003@gmail.com> (raw)
In-Reply-To: <56B77139.4080209@gmail.com>
Hi Andreas,
Here's a few more comments on the current getrichacl(1) page
that I fetched from the git repo.
> .\"
> .\" RichACL Manual Pages
> .\"
> .\" Copyright (C) 2015,2016 Red Hat, Inc.
> .\" Written by Andreas Gruenbacher <agruenba@redhat.com>
> .\" This is free documentation; you can redistribute it and/or
> .\" modify it under the terms of the GNU General Public License as
> .\" published by the Free Software Foundation; either version 2 of
> .\" the License, or (at your option) any later version.
> .\"
> .\" The GNU General Public License's references to "object code"
> .\" and "executables" are to be interpreted as the output of any
> .\" document formatting or typesetting system, including
> .\" intermediate and printed output.
> .\"
> .\" This manual is distributed in the hope that it will be useful,
> .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
> .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> .\" GNU General Public License for more details.
> .\"
> .\" You should have received a copy of the GNU General Public
> .\" License along with this manual. If not, see
> .\" <http://www.gnu.org/licenses/>.
> .\"
> .TH GETRICHACL 7 2015-09-01 "Linux" "Rich Access Control Lists"
>
> .SH NAME
> getrichacl \- Get Rich Access Control Lists
>
> .SH SYNOPSIS
> .B getrichacl
> .RI [ option "]... [" file ]...
>
> .SH DESCRIPTION
> For each file,
> .B getrichacl
> displays the file name and the file's Rich Access Control List (RichACL).
>
> The output format of
> .B getrichacl
> is as follows:
Add a blank line here.
> .fam C
> .RS
> .nf
> 1: file:
> 2: flags:a
> 3: owner:rwp-------------::mask
> 4: group:r-p-------------::mask
> 5: other:r---------------::mask
> 6: owner@:rwp-------------::allow
> 7: user:foo:r-p-------------::allow
> 8: group@:r-p-------------::allow
> 9: group:bar:r-p-------------::allow
> 10: everyone@:r---------------::allow
> 11:
> .fi
> .RE
> .fam T
>
> Line 1 contains the file name, followed by a colon.
>
> Line 2 contains the ACL flags. This line is omitted if no flags are set.
>
> Lines 3--5 indicate the owner, group, and other file masks, which are only
> shown if the \fB\-\-raw\fR option is specified.
>
> Lines 6--10 indicate different ACL entries for the file owner
> .RB ( owner@ ),
> user \fIfoo\fR, the owning group
> .RB ( group@ ),
> group \fIbar\fR, and for everyone
> .RB ( everyone@ ).
>
> A blank line follows at the end.
>
> The default output format uses the single-letter forms of flags and
> permissions, identifiers of ACL entries are right justified, permissions are
> vertically aligned, and permissions which are always granted
> .RB ( read_attributes ", " read_acl ", " synchronize )
> are omitted. See the
> .BR richacl (7)
> manual page for the defined flags and permissions.
>
> By default,
> .B getrichacl
> displays the effective permissions remaining after applying the file masks to
> the ACL. The file masks and underlying NFSv4 ACL can be displayed with the
> \fB\-\-raw\fR option.
>
> When
> .B getrichacl
> is used on a file that does not have a RichACL or on a filesystem that does not
> support RichACLs,
> .B getrichacl
Replace the previous line with "it".
> displays the access permissions defined by the traditional file permission bits
> as a RichACL. When
> .B getrichacl
> is used on a file that has a POSIX ACL (see
> .BR acl (5)),
> it prints an error message.
>
> .SH OPTIONS
> .TP
> \fB\-\-long\fR, \fB\-l\fR
> Display access masks and flags in their long form.
> .TP
> \fB\-\-full\fR
> Also show permissions which are always implicitly allowed.
> .TP
> \fB\-\-raw\fR
> Show ACLs as stored on the file system, including the file masks. Implies
> \fB\-\-full\fR.
> .TP
> \fB\-\-unaligned\fR
> Do not align ACL entries or pad missing permissions with '-'.
> .TP
> \fB\-\-numeric-ids\fR
> Display numeric user and group IDs instead of names.
> .TP
> \fB\-\-access\fR [=\fIuser\fR[:\fIgroup\fR:...]}, \fB\-a\fR[\fIuser\fR[:\fIgroup\fR:...]}
> Instead of showing the ACL, show which permissions the user running the command
> has for the specified file(s). When \fIuser\fR is specified, show which
> permissions the specified user has instead. If \fIuser\fR is followed by a
> colon and a (possibly empty) list of groups, assume that \fIuser\fR is a member
> in the specified groups; otherwise,
> .BR getgrouplist (3)
> is used to determine the groups \fIuser\fR is a member in.
s/in/of/
> .TP
> \fB\-\-version\fR, \fB\-v\fR
> Display the version of
> .B getrichacl
> and exit.
> .TP
> \fB\-\-help\fR, \fB\-h\fR
> Display command-line usage help text.
>
> .SH AUTHOR
> Written by Andreas Grünbacher <agruenba@redhat.com>.
>
> Please send your bug reports, suggested features and comments to the above address.
>
> .SH CONFORMING TO
> Rich Access Control Lists are Linux-specific.
>
> .SH SEE ALSO
> .BR richacl (7),
> .BR setrichacl (1)
Cheers,
Michael
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-02-14 21:30 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 16:28 RichACLs man-pages review Michael Kerrisk (man-pages)
2016-02-07 16:28 ` 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:29 ` Michael Kerrisk (man-pages)
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 16:30 ` Michael Kerrisk (man-pages)
2016-02-07 16:30 ` Michael Kerrisk (man-pages)
2016-02-07 18:16 ` Martin Steigerwald
2016-02-07 18:16 ` Martin Steigerwald
[not found] ` <56B77139.4080209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-14 21:30 ` Michael Kerrisk (man-pages) [this message]
2016-02-14 21:30 ` Michael Kerrisk (man-pages)
2016-02-14 21:30 ` Michael Kerrisk (man-pages)
2016-02-07 16:31 ` setrichacl(1) " Michael Kerrisk (man-pages)
2016-02-07 16:31 ` Michael Kerrisk (man-pages)
2016-02-07 16:31 ` Michael Kerrisk (man-pages)
2016-02-14 21:29 ` Michael Kerrisk (man-pages)
2016-02-14 21:29 ` Michael Kerrisk (man-pages)
2016-02-07 16:35 ` richacl(7) " Michael Kerrisk (man-pages)
2016-02-07 16:35 ` Michael Kerrisk (man-pages)
2016-02-07 16:35 ` Michael Kerrisk (man-pages)
[not found] ` <56B77262.7090107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-10 19:34 ` J. Bruce Fields
2016-02-10 19:34 ` J. Bruce Fields
2016-02-10 19:34 ` J. Bruce Fields
2016-02-12 22:25 ` Andreas Gruenbacher
2016-02-12 22:25 ` Andreas Gruenbacher
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 21:27 ` Michael Kerrisk (man-pages)
2016-02-14 21:27 ` Michael Kerrisk (man-pages)
2016-02-14 23:12 ` Andreas Gruenbacher
2016-02-14 23:12 ` Andreas Gruenbacher
2016-02-15 10:25 ` Michael Kerrisk (man-pages)
2016-02-15 10:25 ` Michael Kerrisk (man-pages)
[not found] ` <56C1A788.9020008-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-15 11:35 ` Andreas Gruenbacher
2016-02-15 11:35 ` Andreas Gruenbacher
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-15 14:15 ` Michael Kerrisk (man-pages)
2016-02-15 14:15 ` Michael Kerrisk (man-pages)
2016-02-14 21:31 ` Michael Kerrisk (man-pages)
2016-02-14 21:31 ` 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
2016-02-20 16:37 ` Andreas Gruenbacher
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:01 ` Michael Kerrisk (man-pages)
2016-02-21 21:01 ` Michael Kerrisk (man-pages)
2016-02-21 21:40 ` Michael Kerrisk (man-pages)
2016-02-21 21:40 ` 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-22 14:46 ` Andreas Gruenbacher
2016-02-22 14:46 ` Andreas Gruenbacher
2016-02-23 10:16 ` Michael Kerrisk (man-pages)
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-23 10:28 ` Andreas Gruenbacher
2016-02-23 10:28 ` Andreas Gruenbacher
2016-02-28 22:11 ` Andreas Gruenbacher
2016-02-28 22:11 ` Andreas Gruenbacher
2016-02-28 22:11 ` Andreas Gruenbacher
2016-02-23 10:58 ` Michael Kerrisk (man-pages)
2016-02-23 10:58 ` Michael Kerrisk (man-pages)
2016-02-23 10:58 ` Michael Kerrisk (man-pages)
2016-02-23 11:14 ` Andreas Gruenbacher
2016-02-23 11:14 ` Andreas Gruenbacher
[not found] ` <56CC3B4A.7070204-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-23 15:09 ` Andreas Gruenbacher
2016-02-23 15:09 ` Andreas Gruenbacher
2016-02-23 15:09 ` Andreas Gruenbacher
[not found] ` <CAHc6FU67LnV7-roofFe1y_uTfvgwonRZimyu7Wn1CDRzwHZJSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-23 19:01 ` Andreas Gruenbacher
2016-02-23 19:01 ` Andreas Gruenbacher
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=56C0F1FF.3050003@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=adilger-m1MBpc4rdrD3fQ9qLvQP4Q@public.gmane.org \
--cc=agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=anna.schumaker-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
--cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org \
--cc=david-FqsqvQoI3Ljby3iVrkZq2A@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org \
--cc=xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.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.