From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: Feeding containers patches into linux-next
Date: Tue, 15 Jul 2008 10:29:33 -0500 [thread overview]
Message-ID: <20080715152933.GA12061@us.ibm.com> (raw)
In-Reply-To: <1216133004.8856.53.camel@nimitz>
Quoting Dave Hansen (dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org):
> We've been basically merging containers patches through Andrew and -mm
> for a while now. It seems that some of the testing is starting to move
> toward linux-next.
>
> Has anyone considered what it would take for us to get a tree pulled
> into there?
I'd guess we would need to:
1. Beg Stephen :)
2. Work with the lkml community to decide which patches are
sufficiently agreed-upon at least in principle to go into
linux-next. I really think Eric's netns/sysfs patchset
belongs there. I'd also like to see the freezer container
patchset.
3. Pick someone to be maintain that tree. Ideally someone
whom everyone here can agree upon.
-serge
next prev parent reply other threads:[~2008-07-15 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 14:43 Feeding containers patches into linux-next Dave Hansen
2008-07-15 15:29 ` Serge E. Hallyn [this message]
[not found] ` <20080715152933.GA12061-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-07-15 17:50 ` Eric W. Biederman
[not found] ` <m1d4lff355.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-07-15 17:55 ` Dave Hansen
2008-07-15 18:56 ` Eric W. Biederman
[not found] ` <m1fxqbc6y2.fsf-B27657KtZYmhTnVgQlOflh2eb7JE58TQ@public.gmane.org>
2008-07-15 19:07 ` Dave Hansen
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=20080715152933.GA12061@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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