Linux Container Development
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
	Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
	"Eric W. Biederman"
	<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
	Serge Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
	Dave Hansen <havebl>
Cc: Kir Kolyshkin <kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
	Denis Lunev <den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Subject: OLS2008 "namespaces status update" report
Date: Wed, 16 Jan 2008 11:35:11 +0300	[thread overview]
Message-ID: <478DC1BF.6070507@openvz.org> (raw)

Hi, guys.

We're coming up to the deadline of proposals submissions for
OLS2008 and I noticed, that we didn't decide whether we're
going to make some summary report about the namespaces/cgroups
development status.

I think it worth making this one.

Besides, we can send a request for a mini-summit.

Thanks,
Pavel

             reply	other threads:[~2008-01-16  8:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16  8:35 Pavel Emelyanov [this message]
     [not found] ` <478DC1BF.6070507-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-16  9:38   ` OLS2008 "namespaces status update" report Balbir Singh
2008-01-16  9:40   ` Cedric Le Goater
     [not found]     ` <478DD0FD.60804-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-01-16 10:22       ` Pavel Emelyanov
     [not found]         ` <478DDACF.4030802-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-16 13:16           ` Denis V. Lunev
     [not found]             ` <478E03B2.7090905-3ImXcnM4P+0@public.gmane.org>
2008-01-16 14:53               ` Serge E. Hallyn
2008-01-16 16:08               ` Kir Kolyshkin
     [not found]                 ` <478E2C17.1010109-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-16 16:34                   ` Cedric Le Goater
2008-01-16 16:40                   ` Balbir Singh

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=478DC1BF.6070507@openvz.org \
    --to=xemul-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
    --cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
    --cc=den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
    --cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
    --cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
    --cc=kir-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@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