From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) Subject: Re: Feeding containers patches into linux-next Date: Tue, 15 Jul 2008 11:56:21 -0700 Message-ID: References: <1216133004.8856.53.camel@nimitz> <20080715152933.GA12061@us.ibm.com> <1216144516.9459.7.camel@nimitz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1216144516.9459.7.camel@nimitz> (Dave Hansen's message of "Tue, 15 Jul 2008 10:55:16 -0700") 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 Dave Hansen writes: > On Tue, 2008-07-15 at 10:50 -0700, Eric W. Biederman wrote: >> The classic challenge is that we really need most of the patches to go >> through other maintainers because they are not for subsystems we >> maintain. So I am fairly certain things like our network namespace >> work will show up in linux-next because they show up in net-next-2.6. > > But, there are things like the mqueue patches that are against areas > that really have no maintainers. Do you think there will be many more > like that? Probably. We are touching parts of the kernel that rarely change. Eric