From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: mtk.manpages@gmail.com,
"Eric W. Biederman" <ebiederm@xmission.com>,
Seth Forshee <seth.forshee@canonical.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-api@vger.kernel.org
Subject: Re: [PATCH RFC] user-namespaced file capabilities - now with even more magic
Date: Fri, 25 Nov 2016 09:33:50 +0100 [thread overview]
Message-ID: <d2160ca5-12e5-0be7-ade7-c4ee63e1df32@gmail.com> (raw)
In-Reply-To: <20161124225246.GA16648@mail.hallyn.com>
Hi Serge,
On 11/24/2016 11:52 PM, Serge E. Hallyn wrote:
> Quoting Michael Kerrisk (man-pages) (mtk.manpages@gmail.com):
[...]
>> Could we have a man-pages patch for this feature? Presumably for
>> user_namespaces(7) or capabilities(7).
>
> capabilities.7 doesn't actually mention anything about user namespaces
> right now.
True. There's really just this:
Interaction with user namespaces
For a discussion of the interaction of capabilities and user
namespaces, see user_namespaces(7).
> I'll come up with a patch for both I think. Do you have a
> deadline for a new release coming up?
No deadlines as such. The last couple of years, as a sort of
experiment, I've fallen into the same release cycle as the kernel
(typically making a release in the week or so after the kernel release),
and I am even using a similar numbering scheme. Ideally, the man-pages
patch would go into the release that corresponds to the kernel release
that makes the change.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2016-11-25 8:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 15:17 [PATCH RFC] user-namespaced file capabilities - now with even more magic Serge E. Hallyn
2016-11-23 23:01 ` Eric W. Biederman
2016-11-24 8:15 ` Michael Kerrisk (man-pages)
2016-11-24 22:52 ` Serge E. Hallyn
2016-11-25 8:33 ` Michael Kerrisk (man-pages) [this message]
2016-11-25 17:50 ` Serge E. Hallyn
2016-11-25 20:43 ` Michael Kerrisk (man-pages)
2016-11-29 21:29 ` Serge E. Hallyn
2016-12-08 4:43 ` Eric W. Biederman
2016-12-08 4:56 ` Serge E. Hallyn
2016-12-08 5:13 ` Eric W. Biederman
2016-12-09 8:03 ` Eric W. Biederman
2016-12-09 13:42 ` Serge E. Hallyn
2016-12-09 21:39 ` Eric W. Biederman
2016-12-09 23:29 ` Eric W. Biederman
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=d2160ca5-12e5-0be7-ade7-c4ee63e1df32@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=ebiederm@xmission.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=seth.forshee@canonical.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).