From: Tejun Heo <tj@kernel.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
Roman Gushchin <guro@fb.com>, lkml <linux-kernel@vger.kernel.org>,
linux-man <linux-man@vger.kernel.org>,
cgroups@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: cgroups(7): extending man-pages documentation for cgroups v2
Date: Mon, 8 Jan 2018 04:29:11 -0800 [thread overview]
Message-ID: <20180108122911.GM3668920@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <7e5b2a80-9439-4229-0ad0-eecca026a282@gmail.com>
Hello, Michael.
On Tue, Jan 02, 2018 at 07:21:27PM +0100, Michael Kerrisk (man-pages) wrote:
> There are some older features, as well as new features in
> cgroups v2 that have not so far been documented in the cgroups(7)
> manual page. I have been working on patches to add documentation
> for these features, and the man-pages branch containing these
> patches can be found at:
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/log/?h=draft_cgroup_updates
>
> I will send the updates as a series of plain text messages,
> and CC relevant people on the various patches. Would it be
> possible for you to review these patches please.
Yes, will do. Sorry about the delay. Was traveling and then caught a
cold.
Thanks.
--
tejun
next prev parent reply other threads:[~2018-01-08 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 18:21 cgroups(7): extending man-pages documentation for cgroups v2 Michael Kerrisk (man-pages)
2018-01-08 12:29 ` Tejun Heo [this message]
[not found] ` <20180108122911.GM3668920-4dN5La/x3IkLX0oZNxdnEQ2O0Ztt9esIQQ4Iyu8u01E@public.gmane.org>
2018-01-08 23:32 ` Michael Kerrisk (man-pages)
[not found] ` <bd719e73-a5e0-f327-8925-4e1e6356295d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-11 0:16 ` Michael Kerrisk (man-pages)
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=20180108122911.GM3668920@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=peterz@infradead.org \
--cc=serge@hallyn.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