public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Tejun Heo <tj@kernel.org>, "Serge E. Hallyn" <serge@hallyn.com>,
	Roman Gushchin <guro@fb.com>
Cc: mtk.manpages@gmail.com, lkml <linux-kernel@vger.kernel.org>,
	linux-man <linux-man@vger.kernel.org>,
	cgroups@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: cgroups(7): extending man-pages documentation for cgroups v2
Date: Tue, 2 Jan 2018 19:21:27 +0100	[thread overview]
Message-ID: <7e5b2a80-9439-4229-0ad0-eecca026a282@gmail.com> (raw)

Hello Tejun (and Roman and Serge),

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.

Thank you,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

             reply	other threads:[~2018-01-02 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-02 18:21 Michael Kerrisk (man-pages) [this message]
2018-01-08 12:29 ` cgroups(7): extending man-pages documentation for cgroups v2 Tejun Heo
     [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=7e5b2a80-9439-4229-0ad0-eecca026a282@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=guro@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=serge@hallyn.com \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox