Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 20 Apr 2002 14:51:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 20 Apr 2002 14:51:53 -0400 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:42323 "EHLO frodo.biederman.org") by vger.kernel.org with ESMTP id ; Sat, 20 Apr 2002 14:51:52 -0400 To: Daniel Phillips Cc: Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: [PATCH] Remove Bitkeeper documentation from Linux tree In-Reply-To:

From: ebiederm@xmission.com (Eric W. Biederman) Date: 20 Apr 2002 12:44:01 -0600 Message-ID: Lines: 34 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Daniel Phillips writes: > All of what you said, 100% agreed, and insightful, in particular: > > On Saturday 20 April 2002 19:53, Eric W. Biederman wrote: > > I can see the potential for this to break down. However we should > > not be crying wolf until this actually does break down. > > Do we want it to break down first? I don't want that. The price of freedom is continual vigilance. So when confronted by changes in practice that we aren't sure about the appropriate procedure is to ask (publicly?). If this is keeping developers from participating. Or if it is placing a significant barrier in the way of developers. If we start the conversation without condemnation of change, we won't be crying wolf. Only asking is that a wolf? Addressing the filter is doing X fun. For me working with near-free tools is not fun, because I must always be aware of the difference. I am never quite certain where I stand with the tool vendor. The tool is not free obviously because money making opportunities are more important than my ability to use and modify the tool. At the same time constant vigilance even of free software is required. A non-free tool that does a sufficiently good job that I don't feel like fixing it, is usable. It simply becomes a minor background irritant that I can ignore. Linus working more efficiently so he can accept more patches is obviously more fun :) Eric - 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/