Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 20 Apr 2002 22:29:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 20 Apr 2002 22:29:06 -0400 Received: from server0011.freedom2surf.net ([194.106.56.14]:39952 "EHLO server0011.freedom2surf.net") by vger.kernel.org with ESMTP id ; Sat, 20 Apr 2002 22:29:06 -0400 Date: Sun, 21 Apr 2002 03:36:33 +0100 From: Ian Molton To: Daniel Phillips Cc: torvalds@transmeta.com, garzik@havoc.gtf.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Remove Bitkeeper documentation from Linux tree Message-Id: <20020421033633.02245aa2.spyro@armlinux.org> In-Reply-To: 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 Daniel Phillips Awoke this dragon, who will now respond: > A steady slide toward proprietary tools and behind-the-scenes development > in cathedral-style is an issue. Whilst Im not sure I agree that bitkeeper is going to push things 'behind the scenes' (its a source management tool, not the source itself), I do think the basic point being made here has some merit. Think about it... - 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/