Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270295AbTGRTgo (ORCPT ); Fri, 18 Jul 2003 15:36:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270302AbTGRTgo (ORCPT ); Fri, 18 Jul 2003 15:36:44 -0400 Received: from fencepost.gnu.org ([199.232.76.164]:62146 "EHLO fencepost.gnu.org") by vger.kernel.org with ESMTP id S270295AbTGRTgo (ORCPT ); Fri, 18 Jul 2003 15:36:44 -0400 From: Richard Stallman to: linux-kernel@vger.kernel.org Subject: Bitkeeper Reply-to: rms@gnu.org Message-Id: Date: Fri, 18 Jul 2003 15:51:36 -0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 958 Lines: 16 > 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. - 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/