Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 21 Apr 2002 00:29:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 21 Apr 2002 00:29:20 -0400 Received: from pizda.ninka.net ([216.101.162.242]:21961 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Sun, 21 Apr 2002 00:29:19 -0400 Date: Sat, 20 Apr 2002 21:20:17 -0700 (PDT) Message-Id: <20020420.212017.22963738.davem@redhat.com> To: spyro@armlinux.org Cc: viro@math.psu.edu, torvalds@transmeta.com, linux-kernel@vger.kernel.org Subject: Re: BK, deltas, snapshots and fate of -pre... From: "David S. Miller" In-Reply-To: <20020421053143.4ef9f810.spyro@armlinux.org> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) 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 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. That someone just submitting patches is somehow "left out". Al is showing that these claims are not well founded at all. - 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/