Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263943AbUFKOPr (ORCPT ); Fri, 11 Jun 2004 10:15:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263984AbUFKOPr (ORCPT ); Fri, 11 Jun 2004 10:15:47 -0400 Received: from kinesis.swishmail.com ([209.10.110.86]:33294 "EHLO kinesis.swishmail.com") by vger.kernel.org with ESMTP id S263943AbUFKOPp (ORCPT ); Fri, 11 Jun 2004 10:15:45 -0400 Message-ID: <40C9C247.4070702@techsource.com> Date: Fri, 11 Jun 2004 10:31:35 -0400 From: Timothy Miller MIME-Version: 1.0 To: Hans Reiser CC: =?ISO-8859-1?Q?J=F6rn_Engel?= , Dave Jones , Chris Mason , reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org Subject: Re: [STACK] >3k call path in reiserfs References: <20040609122226.GE21168@wohnheim.fh-wedel.de> <1086784264.10973.236.camel@watt.suse.com> <1086800028.10973.258.camel@watt.suse.com> <40C74388.20301@namesys.com> <1086801345.10973.263.camel@watt.suse.com> <40C75141.7070408@namesys.com> <20040609182037.GA12771@redhat.com> <40C79FE2.4040802@namesys.com> <20040610223532.GB3340@wohnheim.fh-wedel.de> <40C91DA0.6060705@namesys.com> In-Reply-To: <40C91DA0.6060705@namesys.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1239 Lines: 31 Hans Reiser wrote: > This is all part of what responsible release management is about. I > was the junior whiz kid in professional release management teams before > starting Namesys. I listened to my elders and learned from them. My > standards for professional conduct in this arena are higher than yours > as a result of that. > You are a bunch of young kids who lack professional experience in > release management. That is ok, but don't get aggressive about it. > > I have no desire to pay for your mistakes, and as the official > maintainer it is my responsibility to ensure that neither I nor the > users pay for the mistakes of those who add bugs to stable branches > instead of adding them to the development branches where they belong. Don't get condescending. Immature people don't like to be told that they are immature. :) Anyhow, I agree with you. V3 should remain unchanged. If Linux wants ReiserFS AND 4K stacks, they're going to have to wait for V4. - 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/