Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 20 Jan 2003 16:33:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 20 Jan 2003 16:33:22 -0500 Received: from 5-116.ctame701-1.telepar.net.br ([200.193.163.116]:36996 "EHLO 5-116.ctame701-1.telepar.net.br") by vger.kernel.org with ESMTP id ; Mon, 20 Jan 2003 16:33:21 -0500 Date: Mon, 20 Jan 2003 19:41:58 -0200 (BRST) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: David Schwartz cc: david.lang@digitalinsight.com, "" , "" Subject: Re: Is the BitKeeper network protocol documented? In-Reply-To: <20030120201904.AAA25148@shell.webmaster.com@whenever> Message-ID: References: <20030120201904.AAA25148@shell.webmaster.com@whenever> X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 20 Jan 2003, David Schwartz wrote: > I submit that it is impossible to comply with the GPL and > distribute binaries if the preferred form of a work for the purposes of > making modifications to it is in a proprietary file format. This is > tantamount to encrypting the source. You'll have to find another project to prove your idea, though. Bitkeeper is using the AT&T SCCS format (plus compression) to store its data and metadata. People are working on scripts to extract the source from a bitkeeper tree without using the bitkeeper software. cheers, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://guru.conectiva.com/ Current spamtrap: october@surriel.com - 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/