Return-Path: <linux-kernel-owner+akpm=40zip.com.au@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S314132AbSDVMLo>; Mon, 22 Apr 2002 08:11:44 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S314138AbSDVMLn>; Mon, 22 Apr 2002 08:11:43 -0400
Received: from dsl-213-023-039-131.arcor-ip.net ([213.23.39.131]:2202 "EHLO
	starship") by vger.kernel.org with ESMTP id <S314132AbSDVMLm>;
	Mon, 22 Apr 2002 08:11:42 -0400
Content-Type: text/plain; charset=US-ASCII
From: Daniel Phillips <phillips@bonn-fries.net>
To: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: [OFF TOPIC] BK license change
Date: Sun, 21 Apr 2002 14:12:16 +0200
X-Mailer: KMail [version 1.3.2]
In-Reply-To: <20020421095715.A10525@work.bitmover.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Message-Id: <E16zGCW-0001EM-00@starship>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Sunday 21 April 2002 18:57, Larry McVoy wrote:
> I'm considering a change to the BKL which says that N days after a
> changeset is made, that changeset (and its ancestory) must be available
> on a public bk server.  In other words, put a hard limit on how long
> you may hide.

More red tape is usually bad.  You want to do it to protect your commericial
interests?  Fine.  However, the GPL does not need Bitkeeper to be its robocop.
GPL violations have a way of coming to light without this sort of automated
enforcement.

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