Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755658Ab3GCD3q (ORCPT ); Tue, 2 Jul 2013 23:29:46 -0400 Received: from ipmail05.adl6.internode.on.net ([150.101.137.143]:6269 "EHLO ipmail05.adl6.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755398Ab3GCD3p (ORCPT ); Tue, 2 Jul 2013 23:29:45 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqQMAOGZ01F5LCeA/2dsb2JhbABagwm7bIUlBAGBAhd0giMBAQU6HCMQCAMYCSUPBSUDIRMUh3q7TRaOMoEdB4NtA5dJkUaDIyo Date: Wed, 3 Jul 2013 13:29:41 +1000 From: Dave Chinner To: Greg KH Cc: Linus Torvalds , Stephen Rothwell , Andreas Dilger , "Theodore Ts'o" , Linux Kernel Mailing List Subject: Re: [GIT PULL] ext4 updates for 3.11 Message-ID: <20130703032941.GH14996@dastard> References: <20130703094529.99444050e676467d281a3b51@canb.auug.org.au> <20130703005419.GA7744@kroah.com> <20130703010111.GA7986@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130703010111.GA7986@kroah.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2142 Lines: 48 On Tue, Jul 02, 2013 at 06:01:11PM -0700, Greg KH wrote: > On Tue, Jul 02, 2013 at 05:58:15PM -0700, Linus Torvalds wrote: > > On Tue, Jul 2, 2013 at 5:54 PM, Greg KH wrote: > > > On Tue, Jul 02, 2013 at 05:02:21PM -0700, Linus Torvalds wrote: > > >> > > >> I'm really not convinced this whole Lustre thing was correctly > > >> handled. Merging it into stable and yet being in such bad shape that > > >> it isn't enabled even there? I just dunno. But I have the turd in my > > >> tree now, let's hope it gets fixed up. > > > > > > It's in "staging", not "stable" :) > > > > Yes. But what was the reason to actually merge it even there? And once > > it gets merged, disabling it again rather than fixing the problems it > > has? > > The problems turned out to be too big, too late in the merge cycle for > me to be able to take them (they still aren't even done, as I don't have > a working set of patches yet.) So I just disabled it from the build to > give Andreas and team time to get it working properly. > > I could have just removed it, but I thought I would give them a chance. > > > This is a filesystem that Intel apparently wants to push. I think it > > would have been a better idea to push back a bit and say "at least > > clean it up a bit first". It's not like Intel is one of the clueless > > companies that couldn't have done so and need help from the community. > > For this filesystem, it seems that they don't have any resources to do > this work and are relying on the community to help out. Which is odd, > but big companies are strange some times... Didn't we learn this lesson already with POHMELFS? i.e. that dumping filesystem code in staging on the assumption "the community" will fix it up when nobody in "the community" uses or can even test that filesystem is a broken development model.... Cheers, Dave. -- Dave Chinner david@fromorbit.com -- 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/