[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFxdNVX9koH=GViv1Haj3kU07PD-CTKCNuWrm-c-BF3mQw@mail.gmail.com>
Date: Tue, 2 Jul 2013 17:58:15 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Greg KH <greg@...ah.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Andreas Dilger <andreas.dilger@...el.com>,
"Theodore Ts'o" <tytso@....edu>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] ext4 updates for 3.11
On Tue, Jul 2, 2013 at 5:54 PM, Greg KH <greg@...ah.com> 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?
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.
As it is, it got merged, and apparently things are going *backwards*
rather than forwards because it doesn't even show up in the
allmodconfig builds I do.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists