From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: Progress of containers at 2.6.32/33?
Date: Mon, 22 Feb 2010 08:58:20 -0600 [thread overview]
Message-ID: <20100222145820.GA31011@us.ibm.com> (raw)
In-Reply-To: <m1r5oepjye.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
Quoting Eric W. Biederman (ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org):
>
> 2.6.32 is likely to be used widely so I expect everyone's out of tree
> patches to be updated. As a metric to figuring out which things have
> worked and which things have not I would like ask all of those who are
> maintaining out of tree container patches to give some feedback on
> what code they have been able to remove from their patchsets when
> using the latest kernel, and which patches persist.
>
> I have been in some conversations lately that indicate that we have
> some tremendous short comings in the work that has gone on in the
> public tree. So I am asking now so we can guage where we are at
> as a community.
>
> Eric
Hey Eric,
can you give some specific examples which came out of those conversations?
Because I'm not quite sure what type of info you're looking for (and I
don't think I'm the only one).
By 'short comings in the work' do you mean things being addressed in
private trees, or shortcomings which have become apparent which are not
yet being addressed?
-serge
next parent reply other threads:[~2010-02-22 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1r5oepjye.fsf@fess.ebiederm.org>
[not found] ` <m1r5oepjye.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2010-02-22 14:58 ` Serge E. Hallyn [this message]
2010-02-23 12:32 ` Progress of containers at 2.6.32/33? Daniel Lezcano
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=20100222145820.GA31011@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.