Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270367AbTGRUVT (ORCPT ); Fri, 18 Jul 2003 16:21:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270368AbTGRUVT (ORCPT ); Fri, 18 Jul 2003 16:21:19 -0400 Received: from CPE-65-29-18-15.mn.rr.com ([65.29.18.15]:17280 "EHLO www.enodev.com") by vger.kernel.org with ESMTP id S270367AbTGRUVS (ORCPT ); Fri, 18 Jul 2003 16:21:18 -0400 Subject: Re: Bitkeeper From: Shawn To: Michael Buesch Cc: rms@gnu.org, linux kernel mailing list In-Reply-To: <200307182230.17803.fsdeveloper@yahoo.de> References: <200307182230.17803.fsdeveloper@yahoo.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1058560569.29910.36.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 18 Jul 2003 15:36:09 -0500 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1023 Lines: 23 In my mind it's absolutely not worth it. I believe there are non-commercial protocol gateways from which a copy of linux (complete with historical BK metadata) can be pulled and converted from. Larry has his views whether 99.9999% of people disagree with him or not. He can change the protocol as he sees fit, and we can pull the source off of BK if we want. He has stated before, it would be no skin off his balls (to paraphrase). On Fri, 2003-07-18 at 15:30, Michael Buesch wrote: > First I think, this list isn't the correct place for starting > a bk-flame again. > But I also share your opinion, that it's time to write even a > free client. > But how hard will it be? How big is the knowlege of the > protocols bk uses? It'll be not easy, but for sure very interesting. - 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/