Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 22 Apr 2002 15:59:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 22 Apr 2002 15:59:54 -0400 Received: from austin.openmic.com ([216.143.252.250]:9744 "EHLO austin.openmic.com") by vger.kernel.org with ESMTP id ; Mon, 22 Apr 2002 15:59:51 -0400 Message-ID: <3CC46B07.8020604@greshamstorage.com> Date: Mon, 22 Apr 2002 14:56:55 -0500 From: "Jonathan A. George" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020421 Debian/1.rc1-1 MIME-Version: 1.0 To: Alexander Viro CC: Jeff Garzik , linux-kernel@vger.kernel.org Subject: Re: [PATCH] Remove Bitkeeper documentation from Linux tree In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Alexander Viro wrote: >On Mon, 22 Apr 2002, Jonathan A. George wrote: > >>Not quite. Linus uses BK as a tool to facilitate kernel development. >> However, he has not made BK _part_ _of_ _the_ _kernel_. ;-) Obviously >>anyone can use any tool ON the kernel, but integrating into the kernel >>is something else. >> >>>Talk Linus out of using BitKeeper, and sure, I'll remove the doc. >>> >>No need. His tools are his choice. The kernel itself is ours not his; >> thus the distinction. >> >> > >Bullshit. His copy is his. Mine is mine. Yours is yours. Each of >us is perfectly within his rights when he adds whatever patches he >likes. > Both statements are true. Imagine that. --Jonathan-- - 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/