From: Konstantin Ryabitsev <mricon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Peter Dolding <oiaohm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Serge Hallyn
<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
webmaster-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: Single process controlling all cgroups sounds like looking in right direction but wrong solution.
Date: Fri, 19 Jul 2013 16:01:21 -0400 [thread overview]
Message-ID: <51E99B11.5020904@kernel.org> (raw)
In-Reply-To: <CANA3KFVeYkvidYu=1rV_We3JLH5QEsogCnYQEdA6VGBKD2sbYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
On 16/07/13 06:06 PM, Peter Dolding wrote:
> Webmaster https://www.kernel.org/doc/linux/MAINTAINERS and the
> Maintainers file in git don't match. Would suspect other sections
> in doc directory are also out.
Correct, that seems to have been completely overlooked. I just put
together a script that will auto-build and update the documentation
tree. The following is now auto-updated each time Linus tags his tree:
https://www.kernel.org/doc/Documentation/
https://www.kernel.org/doc/htmldocs/
https://www.kernel.org/doc/readme/
https://www.kernel.org/doc/linux/
https://www.kernel.org/doc/makehelp.txt
Best,
--
Konstantin Ryabitsev
Senior Systems Administrator
Linux Foundation Collab Projects
Montréal, Québec
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 730 bytes --]
next prev parent reply other threads:[~2013-07-19 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANA3KFV6LmfKYUo305Fo2Yv_0kJGSSa7OjnGi8BMb+0Ys9e8NA@mail.gmail.com>
[not found] ` <20130715032551.GA3046@ac100>
2013-07-15 3:47 ` Single process controlling all cgroups sounds like looking in right direction but wrong solution Peter Dolding
[not found] ` <CANA3KFWdKbrpZDHHsqKeh-vugK7NjJ1xrFcXyYSRaKn0mUYewg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-15 3:52 ` Peter Dolding
2013-07-15 12:32 ` Serge Hallyn
2013-07-16 22:06 ` Peter Dolding
[not found] ` <CANA3KFVeYkvidYu=1rV_We3JLH5QEsogCnYQEdA6VGBKD2sbYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-19 20:01 ` Konstantin Ryabitsev [this message]
2013-07-18 9:38 ` Rob Landley
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=51E99B11.5020904@kernel.org \
--to=mricon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=oiaohm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
--cc=webmaster-DgEjT+Ai2ygdnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox