Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 22 Apr 2002 08:57:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 22 Apr 2002 08:57:05 -0400 Received: from dsl-213-023-039-131.arcor-ip.net ([213.23.39.131]:28826 "EHLO starship") by vger.kernel.org with ESMTP id ; Mon, 22 Apr 2002 08:57:05 -0400 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: "David S. Miller" , spyro@armlinux.org Subject: Re: BK, deltas, snapshots and fate of -pre... Date: Sun, 21 Apr 2002 14:57:38 +0200 X-Mailer: KMail [version 1.3.2] Cc: linux-kernel@vger.kernel.org In-Reply-To: <20020421044616.5beae559.spyro@armlinux.org> <20020421053143.4ef9f810.spyro@armlinux.org> <20020420.212017.22963738.davem@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sunday 21 April 2002 06:20, David S. Miller wrote: > From: Ian Molton > Date: Sun, 21 Apr 2002 05:31:43 +0100 > > Alexander Viro Awoke this dragon, who will now respond: > > > As one of the guys who doesn't use BK _and_ had submitted a lot of > > patches since Linus had started using it, I'm probably qualified to tell > > whether it hurts orSure, except no-one cares about this point. > > Sure, except no-one cares about this point. > > the documentation is the 'sticky wicket'... > > Incorrect. The argument for the documentation was that it along with > other things wrt. BK create some "barrier to entry" for Linux kernel > development and almost force someone to use BK. It was my argument, so I'm qualified to say what it was. Ian Molton is correct, your interpretation is strictly secondary. -- Daniel - 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/