Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S267359AbTAVHMK>; Wed, 22 Jan 2003 02:12:10 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S267366AbTAVHMK>; Wed, 22 Jan 2003 02:12:10 -0500
Received: from otter.mbay.net ([206.55.237.2]:14852 "EHLO otter.mbay.net")
	by vger.kernel.org with ESMTP id <S267359AbTAVHMJ> convert rfc822-to-8bit;
	Wed, 22 Jan 2003 02:12:09 -0500
From: John Alvord <jalvo@mbay.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: Hua Zhong <huaz@sbcglobal.net>, David Schwartz <davids@webmaster.com>,
       dana.lacoste@peregrine.com, linux-kernel@vger.kernel.org
Subject: Re: Is the BitKeeper network protocol documented?
Date: Tue, 21 Jan 2003 23:21:03 -0800
Message-ID: <cghs2vg6bnlfbjgfe52s5fe2aveob7fbb6@4ax.com>
References: <CDEDIMAGFBEBKHDJPCLDCEEKCFAA.huaz@sbcglobal.net> <20030122071028.GA3466@bjl1.asuk.net>
In-Reply-To: <20030122071028.GA3466@bjl1.asuk.net>
X-Mailer: Forte Agent 1.92/32.570
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 22 Jan 2003 07:10:28 +0000, Jamie Lokier <jamie@shareable.org>
wrote:

>Hua Zhong wrote:
>> > 	First, I would in fact prefer to have the version control
>> > information to make changes. The commit comments, for example, may
>> > explain the rationale for changes.
>> 
>> These comments are not part of the source. The source has its own comments.
>> They are helpful when you try to track the changes, but GPL doesn't require
>> releasing the tracking record of a GPL project.
>
>> It only requires releasing the whole source (or diff).
>
>No, a "diff" is _not_ sufficient when releasing a modified binary -
>you must provide, or offer to provide, the whole source used to make
>that binary.
>
>People differ in what they think the "whole source" means.  The GPL
>defines what _it_ means by the source code for a work, and that is the
>definition you are bound by, but even that definition is understood
>differently by different people.  It is the nuances of that definition
>that are being discussed in this thread.
>
>I agree with Larry that clear boundaries will be found in case law, as
>and when they are required, and that meeting minutes and repository
>metadata probably are not considered part of the source code.
>
>It is just tough luck that you miss out on useful information.
>
>In addition, even if Linus refused to work with someone who did not
>use the repository, that is also tough luck.  You have the right to
>fork the project; the GPL does not give you the right to work with Linus.
>
>However if there was a project where the repository was _essential_ to
>do any meaningful work on the project, I suspect that a court of law
>would find that the repository is considered part of the source code
>per the GPL's definition.

First you would have to find a court willing to accept jurisdiction.
One court per country you were interested in. And all the appelate
courts. Then you would have to find plaintifs and defendents willing
to pony up money to pay for thousands of hours of lawyer time. 

All for a product which is "free".

heh heh heh

john alvord

-
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/