From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Serge E. Hallyn" Subject: Re: Feeding containers patches into linux-next Date: Tue, 15 Jul 2008 10:29:33 -0500 Message-ID: <20080715152933.GA12061@us.ibm.com> References: <1216133004.8856.53.camel@nimitz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1216133004.8856.53.camel@nimitz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Dave Hansen Cc: Containers List-Id: containers.vger.kernel.org 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