Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270603AbTGTCgW (ORCPT ); Sat, 19 Jul 2003 22:36:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270604AbTGTCgW (ORCPT ); Sat, 19 Jul 2003 22:36:22 -0400 Received: from dsl081-067-005.sfo1.dsl.speakeasy.net ([64.81.67.5]:44173 "EHLO renegade") by vger.kernel.org with ESMTP id S270603AbTGTCfq (ORCPT ); Sat, 19 Jul 2003 22:35:46 -0400 Date: Sat, 19 Jul 2003 19:50:26 -0700 From: Zack Brown To: Richard Stallman Cc: linux-kernel@vger.kernel.org, arch-users@lists.fifthvision.net Subject: Re: Bitkeeper Message-ID: <20030720025026.GA3340@renegade> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2041 Lines: 44 Hi folks, On Fri, Jul 18, 2003 at 03:51:36PM -0400, Richard Stallman wrote: > > If you are trying to copy BK, give it up. We'll simply follow in the > > footsteps of every other company faced with this sort of thing and change > > the protocol every 6 months. Since you would be chasing us you can never > > catch up. If you managed to stay close then we'd put digital signatures > > into the protocol to prevent your clone from interoperating with BK. > > I think it would be appropriate at this point to write a free client > that talks with Bitkeeper, and for Linux developers to start switching > to that from Bitkeeper. At that point, McVoy will face a hard choice: > if he carries out these threats, he risks alienating the community > that he hopes will market Bitkeeper for him. I'm against Richard inflaming the situation without really helping, but since the issue's come up again, I just thought I'd put in a good word for arch here: The arch project is no longer just a bunch of shell scripts. Tom Lord has rewritten it in C (and called the C version 'tla'), and it's self-hosting. Developers are actually contributing to development using arch itself now. These seem like very big milestones to me. There's still quite a bit of work to do on it (and a steep learning curve), but personally, I think it's the project with the best chance of success. Anyone who's interested in this issue might consider contributing to arch development instead of duking it out on lkml. Be well, Zack > - > 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/ -- Zack Brown - 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/