From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261824AbVFVCrR (ORCPT ); Tue, 21 Jun 2005 22:47:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262524AbVFVCrR (ORCPT ); Tue, 21 Jun 2005 22:47:17 -0400 Received: from rwcrmhc12.comcast.net ([216.148.227.85]:48573 "EHLO rwcrmhc12.comcast.net") by vger.kernel.org with ESMTP id S261824AbVFVCrL (ORCPT ); Tue, 21 Jun 2005 22:47:11 -0400 Message-ID: <42B8D131.6060502@namesys.com> Date: Tue, 21 Jun 2005 19:47:13 -0700 From: Hans Reiser User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andi Kleen CC: Jeff Garzik , hch@infradead.org, linux-kernel@vger.kernel.org, ReiserFS List Subject: Re: reiser4 plugins References: <20050620235458.5b437274.akpm@osdl.org.suse.lists.linux.kernel> <42B831B4.9020603@pobox.com.suse.lists.linux.kernel> <42B87318.80607@namesys.com.suse.lists.linux.kernel> <20050621202448.GB30182@infradead.org.suse.lists.linux.kernel> <42B8B9EE.7020002@namesys.com.suse.lists.linux.kernel> <42B8BB5E.8090008@pobox.com.suse.lists.linux.kernel> In-Reply-To: X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Andi Kleen wrote: > Christoph does a lot of reviewing > and he is notorious for making needed linux contributors go away and not come back, and I won't say which famous person on this mailing list told me that.... >and your child definitely >is in serious need of that to be mergeable. I'm sure Christoph is able >to review inpartially even when he is involved with other FS. > > As impartial as a puppy on PCP.... Christoph is aggressive about things he does not take the time to understand or ask about first. I hate that. I wish he would go away please. He is not exactly an Ousterhout, Rob Pike, Granger, Mazieres, Frans Kaashoek, etc., in his accomplishments, so why is he reviewing other people's filesystems? Reviews are great, how about finding persons who have created filesystem innovations (and thus are less likely to reject innovations without understanding them) to do them? How about review by benchmark instead? It works, it runs faster than the competition, users like it, we addressed the core kernel patch complaints, it should go in and receive the exposure that will result in lots of useful improvements and suggestions. It seems like we are getting an unusual review process. I used a bunch of algorithms for which there was a consensus among those consulted that the algorithms were a bad idea, only the fact that I paid for the code to be written and required that it be done my way (ignoring the "you just use me as a typewriter" remarks as best I could) caused the algorithms to get implemented at all, and the benchmarks then proved the algorithms were a good idea. V3 performance sucks in major part because I listened to the consensus when I knew better. I don't really care for consensus on my FS anymore. If you guys want to understand what I am doing I am happy to talk about it extensively, but please don't require that I groupthink. I frankly think that with my benchmarks, I should be allowed to tinker on my own. Hans The Mad