Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 18 Dec 2002 19:34:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 18 Dec 2002 19:34:12 -0500 Received: from [81.2.122.30] ([81.2.122.30]:63493 "EHLO darkstar.example.net") by vger.kernel.org with ESMTP id ; Wed, 18 Dec 2002 19:34:11 -0500 From: John Bradford Message-Id: <200212190053.gBJ0rJPu008648@darkstar.example.net> Subject: Re: Freezing.. (was Re: Intel P6 vs P7 system call performance) To: alan@redhat.com (Alan Cox) Date: Thu, 19 Dec 2002 00:53:19 +0000 (GMT) Cc: lm@bitmover.com, torvalds@transmeta.com, davej@codemonkey.org.uk, vonbrand@inf.utfsm.cl, linux-kernel@vger.kernel.org, akpm@digeo.com In-Reply-To: <200212190008.gBJ08vw02314@devserv.devel.redhat.com> from "Alan Cox" at Dec 18, 2002 07:08:57 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: 1472 Lines: 34 > > 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 > No, it's my fault - I was skimming through list traffic, and not concentrating, (proof of this is the fact that I've had sendmail configured incorrectly all day, and been posting from the wrong address, and only just realised :-) ). I saw Larry mention kernel.bkbits.net, and Alan say, "We've got one - its called linux-kernel", (in a separate message without quoting anything, so it's really your fault :-) :-) :-) ), and assumed that a BK argument was imminent, and I made a joke comment that it, (an argument), was not a 2.6 required feature. Sorry about the wasted bandwidth, I'll stop posting as it's now past midnight, and I obviously need sleep. Oh, 2.4.20-pre2 compiled OK for me, I hope that proves I've done something useful tonight. John. - 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/