Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 21 Apr 2002 00:35:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 21 Apr 2002 00:35:28 -0400 Received: from server0011.freedom2surf.net ([194.106.56.14]:37658 "EHLO server0011.freedom2surf.net") by vger.kernel.org with ESMTP id ; Sun, 21 Apr 2002 00:35:27 -0400 Date: Sun, 21 Apr 2002 05:42:53 +0100 From: Ian Molton To: "David S. Miller" Cc: viro@math.psu.edu, torvalds@transmeta.com, linux-kernel@vger.kernel.org Subject: Re: BK, deltas, snapshots and fate of -pre... Message-Id: <20020421054253.4803852a.spyro@armlinux.org> In-Reply-To: <20020420.212017.22963738.davem@redhat.com> Reply-To: spyro@armlinux.org Organization: The dragon roost X-Mailer: Sylpheed version 0.7.4cvs5 (GTK+ 1.2.10; ) 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 David S. Miller Awoke this dragon, who will now respond: > From: Ian Molton > Date: Sun, 21 Apr 2002 05:31:43 +0100 > 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. hmm. I take it as blatently obvious that BK isnt a barrier to entry, as the old methods still work fine. what I /do/ appreciate is that by including directions to proprietary tools in the docs, we are heading down a greased incline, so to speak. Extreme example: Include docs on 'how to avoid a pesky kernel compile' that teach how to install windows, not linux because its an 'all in one' install with 'no hassle'... see how many people compile their own kernels afer that... - 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/