From: Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
To: Peter Dolding <oiaohm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Single process controlling all cgroups sounds like looking in right direction but wrong solution.
Date: Mon, 15 Jul 2013 07:32:16 -0500 [thread overview]
Message-ID: <20130715123216.GA5663@sergelap> (raw)
In-Reply-To: <CANA3KFWdKbrpZDHHsqKeh-vugK7NjJ1xrFcXyYSRaKn0mUYewg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Quoting Peter Dolding (oiaohm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org):
> I followed the Maintainers File. https://www.kernel.org/doc/linux/MAINTAINERS
> CONTROL GROUPS (CGROUPS)
> M: Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
> M: Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
> L: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Odd, my version has
L: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
L: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
The cgroups entry was added in November 2011 according to git-blame.
I don't know why the kernel.org version is so old.
Still I think that should be patched to remove containers@. I
originally objected to the cgroup@ list creation, but since I
do not believe the relevant cgroup folks read the containers@
list any more, I don't think containers@ should be listed -
certainly not first.
> S: Maintained
> F: include/linux/cgroup*
> F: kernel/cgroup*
> F: mm/*cgroup*
>
>
> Apparently by your response this might be a bit out of date. I just read
> lwm and *Tejun Heo is not even as a main maintainer. Listed as a sub part
> maintainer. By the maintainers file discussions should be in *
> containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org where I sent this.
>
> Tejun Heo please inform if this is still correct. Its either update this
> or tell lwn.net to get your title correct in future.
>
> Serge I am trying to follow policy that is why I posted here in the first
> place.
That sounds unnecessarily defensive - I wasn't complaining, just trying
to help your email get to where it would be best discussed :) Sorry
that it involves an extra step (resending), but I didn't want to simply
reply cc:ing cgroups@, as the email thread tends to get funky that way.
-serge
next prev parent reply other threads:[~2013-07-15 12:32 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 [this message]
2013-07-16 22:06 ` Peter Dolding
[not found] ` <CANA3KFVeYkvidYu=1rV_We3JLH5QEsogCnYQEdA6VGBKD2sbYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-19 20:01 ` Konstantin Ryabitsev
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=20130715123216.GA5663@sergelap \
--to=serge.hallyn-gewih/nmzzlqt0dzr+alfa@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=oiaohm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=tj-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