Linux Container Development
 help / color / mirror / Atom feed
From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: James Bottomley
	<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: New list cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Date: Fri, 04 Nov 2011 11:58:23 -0700	[thread overview]
Message-ID: <m1k47fpve8.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1320222589.3091.43.camel@dabdike> (James Bottomley's message of "Wed, 02 Nov 2011 12:29:49 +0400")

James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org> writes:

> One of the requests I got at the kernel summit was a request for an easy
> to find list for everything cgroup related, so I did:
>
> cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>
> I did say that this containers list was supposed to be it, but they felt
> that the name wasn't generic enough, it was too hard to find at the
> Linux Foundation and it was at that time not working because of the hack
> related outage.
>
> Since the object of this cgroups@vger list is to get more kernel people
> to pay attention to cgroup (and namespace) related issues, could I ask
> that you cc it when you post to the containers list?

Namespace related issues are something else entirely.

You are completely confused in conflating the two.

Eric

      reply	other threads:[~2011-11-04 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02  8:29 New list cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org James Bottomley
2011-11-04 18:58 ` Eric W. Biederman [this message]

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=m1k47fpve8.fsf@fess.ebiederm.org \
    --to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
    --cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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