From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S263336AbVFYEnr@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S263336AbVFYEnr (ORCPT <rfc822;willy@w.ods.org>);
	Sat, 25 Jun 2005 00:43:47 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263337AbVFYEnq
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Sat, 25 Jun 2005 00:43:46 -0400
Received: from mail.dvmed.net ([216.237.124.58]:60614 "EHLO mail.dvmed.net")
	by vger.kernel.org with ESMTP id S263336AbVFYEnY (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sat, 25 Jun 2005 00:43:24 -0400
Message-ID: <42BCE0DD.5050608@pobox.com>
Date: Sat, 25 Jun 2005 00:43:09 -0400
From: Jeff Garzik <jgarzik@pobox.com>
User-Agent: Mozilla Thunderbird 1.0.2-6 (X11/20050513)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Hans Reiser <reiser@namesys.com>
CC: David Masover <ninja@slaphack.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
       Christoph Hellwig <hch@infradead.org>, Andrew Morton <akpm@osdl.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: reiser4 plugins
References: <200506231924.j5NJOvLA031008@laptop11.inf.utfsm.cl>	 <42BB31E9.50805@slaphack.com>	 <1119570225.18655.75.camel@localhost.localdomain>	 <42BB7B32.4010100@slaphack.com> <1119612849.17063.105.camel@localhost.localdomain> <42BCCC32.1090802@slaphack.com> <42BCCCED.3030705@pobox.com> <42BCDE06.8080309@namesys.com>
In-Reply-To: <42BCDE06.8080309@namesys.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Hans Reiser wrote:
> Jeff Garzik wrote:
> 
> 
>>Then why not listen to authorities, all of whom are saying "it's not
>>ready yet"
> 
> 
> What exactly is not ready Jeff?  As I see it, this thread is 95%
> posturing, and almost no technical reasons for not merging.  These
> "authorities"seem perfectly content with echoing the words of someone
> who skimmed the code and shot his mouth off without understanding it,
> and now these "authorities" just echo him because they like him and
> assume he must be right.

I've already listed two rather large technical reasons.

When a vendor submits code, they know their [hardware | filesystem] 
best, but Linux kernel developers know the kernel code and kernel 
direction best.

There needs to be a meeting of the minds.  Vendors that stick to "I know 
best" line of reasoning don't get very far in Linux.

	Jeff