Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 20 Apr 2002 11:52:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 20 Apr 2002 11:52:34 -0400 Received: from panic.tn.gatech.edu ([130.207.137.62]:28296 "HELO gtf.org") by vger.kernel.org with SMTP id ; Sat, 20 Apr 2002 11:52:34 -0400 Date: Sat, 20 Apr 2002 11:52:33 -0400 From: Jeff Garzik To: Daniel Phillips Cc: Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: [PATCH] Remove Bitkeeper documentation from Linux tree Message-ID: <20020420115233.A617@havoc.gtf.org> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 19, 2002 at 05:12:33PM +0200, Daniel Phillips wrote: > I have up to this point been open to the use of Bitkeeper as a development > aid for Linux, and, again up to this point, have intended to make use of > Bitkeeper myself, taking a pragmatic attitude towards the concept of using > the best tool for the job. However, now I see that Bitkeeper documentation > has quietly been inserted ino the Linux Documentation directory, and that > without any apparent discussion on lkml. I fear that this demonstrates that > those who have called the use of Bitkeeper a slippery slope do have a point > after all. Guess what? You have the freedom to ignore these docs. Guess what else? You are taking away freedoms by restricting speech, making documents less available than they previously were. Take your closed mind elsewhere. I'm pretty sure Linus has more sense than to apply this patch. Jeff - 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/