Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 18 Dec 2002 19:01:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 18 Dec 2002 19:01:07 -0500 Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:20440 "EHLO devserv.devel.redhat.com") by vger.kernel.org with ESMTP id ; Wed, 18 Dec 2002 19:01:06 -0500 From: Alan Cox Message-Id: <200212190008.gBJ08vw02314@devserv.devel.redhat.com> Subject: Re: Freezing.. (was Re: Intel P6 vs P7 system call performance) To: lm@bitmover.com (Larry McVoy) Date: Wed, 18 Dec 2002 19:08:57 -0500 (EST) Cc: john@bradfords.org.uk (John Bradford), lm@bitmover.com (Larry McVoy), alan@redhat.com, torvalds@transmeta.com, davej@codemonkey.org.uk, vonbrand@inf.utfsm.cl, linux-kernel@vger.kernel.org, akpm@digeo.com In-Reply-To: <20021218140845.L7976@work.bitmover.com> from "Larry McVoy" at Dec 18, 2002 02:08:45 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 696 Lines: 14 > I don't understand why BK is part of the conversation. It has nothing to > do with it. If every time I post to this list the assumption is that it's > "time to beat larry up about BK" then it's time for me to get off the list. > > I can understand it when we're discussing BK; other than that, it's pretty > friggin lame. If that's what was behind your posts, Alan, there is an > easy procmail fix for that. It wasnt me who brought up bitkeeper - 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/