Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755785Ab1FHNam (ORCPT ); Wed, 8 Jun 2011 09:30:42 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.124]:60394 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755373Ab1FHNak (ORCPT ); Wed, 8 Jun 2011 09:30:40 -0400 X-Authority-Analysis: v=1.1 cv=yMxAJ7W7nAoPh8ZdbvCArpG6pAdHwgpzIvOq8QbMesM= c=1 sm=0 a=XYJHFtupD_QA:10 a=5SG0PmZfjMsA:10 a=kj9zAlcOel0A:10 a=OPBmh+XkhLl+Enan7BmTLg==:17 a=SZqOXIthU9N7Ez_25wQA:9 a=0oz2n8WfHEC9MGw72IcA:7 a=CjuIK1q_8ugA:10 a=OPBmh+XkhLl+Enan7BmTLg==:117 X-Cloudmark-Score: 0 X-Originating-IP: 67.242.120.143 Date: Wed, 8 Jun 2011 09:30:37 -0400 From: Steven Rostedt To: Theodore Tso Cc: Stefan Priebe - Profihost AG , david@lang.hm, linux-kernel@vger.kernel.org Subject: Re: XFS problem in 2.6.32 Message-ID: <20110608133037.GF27245@home.goodmis.org> References: <4DEE1D96.6020208@profihost.ag> <6D8DA3D2-D90B-4D82-BDC9-C3F0264A68BF@mit.edu> <4DEE2C70.8060301@profihost.ag> <4DEE9EDA.90001@profihost.ag> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1467 Lines: 24 On Tue, Jun 07, 2011 at 11:28:59PM -0400, Theodore Tso wrote: Ted, you need a new MUA, as it reads horribly in mutt. > > Not all distributions will participate in the maintenance stable tree. Red Hat for example is probably worried about people (specifically, Oracle) taking their kernel expertise "for free" and bidding it against them. So it doesn't surprise me that they aren't submitting patches to the stable tree. After all, they would like you to purchase a support contract if you want to get high quality, supported kernel. Why should they give that work away for free? After all, their salaried developers have to get paid somehow. Others will contribute work in the hopes that other people will also contribute fixes back, but of course nothing forces Red Hat to do this. > As a Red Hat employee, I must speak against this. I have *never* been told to keep something from stable. In fact, I've always been encouraged to push to stable. But it is usually the individual engineer's responsibility to get a patch into stable. If something was missed, it was more the fault of that individual engineer that made the fix than Red Hat. Ask Greg, I'm constantly sending stable patches to him. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/