Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 20 Apr 2002 13:05:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 20 Apr 2002 13:05:46 -0400 Received: from dsl-213-023-039-128.arcor-ip.net ([213.23.39.128]:6794 "EHLO starship") by vger.kernel.org with ESMTP id ; Sat, 20 Apr 2002 13:05:46 -0400 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: Anton Altaparmakov Subject: Re: [PATCH] Remove Bitkeeper documentation from Linux tree Date: Fri, 19 Apr 2002 19:05:52 +0200 X-Mailer: KMail [version 1.3.2] Cc: Linus Torvalds , linux-kernel@vger.kernel.org In-Reply-To: <5.1.0.14.2.20020420170907.06e87550@pop.cus.cam.ac.uk> <5.1.0.14.2.20020420174422.00ad1390@pop.cus.cam.ac.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Saturday 20 April 2002 18:51, you wrote: > The fact that some developers use bitkeeper has no effect on other > developers. On the contrary, I think it has divided the kernel developers firmly into two classes: the "ins" and the "outs". > Well ok, it means that the bk using developers can work faster > but that is not at issue here... Oh I don't disagree at all. Bitkeeper is a big improvement over what existed before. But it is proprietary. Which other tool in the tool chain is proprietary? Heck, it's not even that proprietary. As far as I know I can still download the source. But... looking at those files sitting in the Documentation directory, it looks to me like a big old Marlbourough[TM] ad. > I don't see why there should be any kind of split or anything like that. > Everything continues as before. It's just that some developers now have a > much easier life... And some have a more difficult one. So it goes. -- 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/