Return-Path: <linux-kernel-owner+akpm=40zip.com.au@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S314685AbSDTSQY>; Sat, 20 Apr 2002 14:16:24 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S314688AbSDTSQW>; Sat, 20 Apr 2002 14:16:22 -0400
Received: from dsl-213-023-039-128.arcor-ip.net ([213.23.39.128]:58250 "EHLO
	starship") by vger.kernel.org with ESMTP id <S314685AbSDTSOm>;
	Sat, 20 Apr 2002 14:14:42 -0400
Content-Type: text/plain; charset=US-ASCII
From: Daniel Phillips <phillips@bonn-fries.net>
To: ebiederm@xmission.com (Eric W. Biederman)
Subject: Re: [PATCH] Remove Bitkeeper documentation from Linux tree
Date: Fri, 19 Apr 2002 20:15:14 +0200
X-Mailer: KMail [version 1.3.2]
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
In-Reply-To: <E16ya3u-0000RG-00@starship> <m1elha45q0.fsf@frodo.biederman.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Message-Id: <E16ycuh-0000Wg-00@starship>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

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.

-- 
Daniel
-
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/