From: Tupshin Harper <tupshin@tupshin.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Jamie Lokier <jamie@shareable.org>, linux-kernel@vger.kernel.org
Subject: Re: Is the BitKeeper network protocol documented?
Date: Fri, 17 Jan 2003 22:11:34 -0800 [thread overview]
Message-ID: <3E28F016.4050404@tupshin.com> (raw)
In-Reply-To: <20030118052919.GA22751@work.bitmover.com>
Larry McVoy wrote:
>As far as I can tell your complaint is that you can't have access to
>the up to minute source view without using something which violates
>your politics.
>
>
>
I agree with your sentiment, but you mis-characterize one thing. Jamie
was stating that his interpretation of the BitKeeper license forbade him
to use the free version of BitKeeper because of some of his non-kernel
related activities. This does seem to be a fair interpretation of the
license, according to clause 3-d, and has nothing to do with his
politics. Jamie is stating that it would be illegal for him to use
BitKeeper. Whether or not you agree with the use of BitKeeper for linux
kernel maintenance, it would seem like this is an unnecessarily onerous
clause that prevents some individuals from participating on an equal
footing with everybody else.
-Tupshin
Clause 3-d:
Notwithstanding any other terms in this License, this
License is not available to You if You and/or your employer
develop, produce, sell, and/or resell a product which con-
tains substantially similar capabilities of the BitKeeper
Software, or, in the reasonable opinion of BitMover, com-
petes with the BitKeeper Software.
next prev parent reply other threads:[~2003-01-18 6:02 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 4:33 Is the BitKeeper network protocol documented? Jamie Lokier
2003-01-18 4:57 ` David Schwartz
2003-01-18 5:10 ` Jamie Lokier
2003-01-18 7:23 ` David Schwartz
2003-01-18 7:54 ` [OFFTOPIC] Is the repository of a GPL'd program itself under the GPL? Jamie Lokier
2003-01-20 0:50 ` Richard Stallman
2003-01-18 5:02 ` Is the BitKeeper network protocol documented? Andrew Morton
2003-01-18 5:15 ` Jamie Lokier
2003-01-18 5:29 ` Larry McVoy
2003-01-18 6:11 ` Tupshin Harper [this message]
2003-01-18 6:20 ` Kevin Puetz
2003-01-18 6:39 ` Larry McVoy
2003-01-18 8:09 ` Jamie Lokier
2003-01-18 8:25 ` Andrew Morton
2003-01-18 14:22 ` Roman Zippel
2003-01-19 18:39 ` Andreas Dilger
2003-01-19 18:55 ` Jamie Lokier
2003-01-19 21:50 ` Roman Zippel
2003-01-19 23:26 ` Andreas Dilger
2003-01-19 23:57 ` David Schwartz
2003-01-20 0:20 ` Andreas Dilger
2003-01-20 0:38 ` David Schwartz
2003-01-20 15:52 ` Horst von Brand
2003-01-20 19:43 ` David Schwartz
2003-01-20 19:46 ` David Schwartz
2003-01-21 7:56 ` Horst von Brand
2003-01-20 14:18 ` Roman Zippel
2003-01-22 12:24 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2003-01-18 6:22 Jamie Lokier
[not found] <20030119235742.AAA13049%shell.webmaster.com@whenever>
2003-01-20 0:36 ` Valdis.Kletnieks
2003-01-20 1:05 ` David Schwartz
2003-01-20 14:28 ` Dana Lacoste
2003-01-20 19:00 ` David Schwartz
2003-01-20 19:31 ` David Lang
2003-01-20 20:19 ` David Schwartz
2003-01-20 20:40 ` John Bradford
2003-01-20 20:48 ` Andreas Dilger
2003-01-20 21:14 ` David Schwartz
2003-01-20 21:58 ` John Bradford
2003-01-20 21:37 ` Sam Ravnborg
2003-01-20 21:41 ` Rik van Riel
2003-01-21 16:04 ` Dana Lacoste
2003-01-21 18:34 ` David Schwartz
2003-01-21 18:49 ` John Bradford
2003-01-21 18:58 ` Sam Ravnborg
2003-01-21 19:27 ` Dana Lacoste
2003-01-21 21:04 ` David Schwartz
2003-01-21 19:51 ` Hua Zhong
2003-01-22 7:10 ` Jamie Lokier
2003-01-22 7:21 ` John Alvord
2003-01-22 15:18 ` Larry McVoy
2003-01-22 15:27 ` Dana Lacoste
2003-01-22 15:38 ` Larry McVoy
2003-01-20 1:46 ` David Lang
2003-01-20 1:52 ` Andre Hedrick
[not found] <20030120010504.AAA18836%shell.webmaster.com@whenever>
2003-01-20 1:37 ` Valdis.Kletnieks
2003-01-20 15:55 Theodore Ts'o
2003-01-20 18:53 ` David Schwartz
[not found] <20030120194430.AAA20700%shell.webmaster.com@whenever>
2003-01-20 20:32 ` Valdis.Kletnieks
2003-01-20 21:27 ` David Schwartz
2003-01-21 8:51 ` Horst von Brand
2003-01-21 0:28 Cort Dougan
2003-01-21 19:22 Larry McVoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E28F016.4050404@tupshin.com \
--to=tupshin@tupshin.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox