From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S262092AbTCLWxu>; Wed, 12 Mar 2003 17:53:50 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S262084AbTCLWwO>; Wed, 12 Mar 2003 17:52:14 -0500
Received: from [195.39.17.254] ([195.39.17.254]:19460 "EHLO Elf.ucw.cz")
	by vger.kernel.org with ESMTP id <S262092AbTCLWvL>;
	Wed, 12 Mar 2003 17:51:11 -0500
Date: Thu, 13 Mar 2003 21:00:18 +0100
From: Pavel Machek <pavel@ucw.cz>
To: Larry McVoy <lm@work.bitmover.com>, Zack Brown <zbrown@tumblerings.org>,
       "Martin J. Bligh" <mbligh@aracnet.com>,
       Roman Zippel <zippel@linux-m68k.org>,
       "Eric W. Biederman" <ebiederm@xmission.com>,
       Linus Torvalds <torvalds@transmeta.com>, Larry McVoy <lm@bitmover.com>,
       linux-kernel@vger.kernel.org
Subject: Re: BitBucket: GPL-ed KitBeeper clone
Message-ID: <20030313200018.GH6702@zaurus.ucw.cz>
References: <m14r6ck6jd.fsf@frodo.biederman.org> <Pine.LNX.4.44.0303091609440.5042-100000@serv> <8200000.1047228943@[10.10.2.4]> <20030309172045.GP4170@renegade> <20030309195852.GA6647@work.bitmover.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030309195852.GA6647@work.bitmover.com>
User-Agent: Mutt/1.3.27i
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Hi!

> Get it through your thick head that BK is something valuable to this
> community, even if you don't use it you directly benefit from its use.
> All you people trying to copy BK are just shooting yourself in the foot
> unless you can come up with a solution that Linus will use in the short
> term.  And nobody but an idiot believes that is possible.  So play nice.
> Playing nice means you can use it, you can't copy it.  You can also
> go invent your own SCM system, go for it, it's a challenging problem,
> just don't use BK's files, commands, or anything else in the process.

Eh? It is perfectly okay to look at BK's
commands, ask people how BK works
and study its docs. (Heh, anyone still
has sources of BK from the time it was
available, preferably as hardcopy,
so no license needs to be agreed to
for looking at it?)

> BK is made available for free for one reason and one reason only: to
> help Linus not burn out.  That's based on my personal belief that he is
> critical to success of the Linux effort, he is a unique resource and has
> to be protected.  I've paid a very heavy price for that belief and I'm
> telling you that you are right on the edge of making that price too high.

So go ahead and disallow no-price use of
bitkeeper. It will reduce flamewars on
l-k quite a bit...
				Pavel
-- 
				Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...