From: Larry McVoy <lm@bitmover.com>
To: James Blackwell <jblack@linuxguru.net>
Cc: linux-kernel@vger.kernel.org, Larry McVoy <lm@bitmover.com>
Subject: Re: Listmaster request: Do not blacklist rms@gnu.org
Date: Tue, 22 Oct 2002 10:44:14 -0700 [thread overview]
Message-ID: <20021022104414.L6546@work.bitmover.com> (raw)
In-Reply-To: <E1842ls-0000yJ-00@comet.linuxguru.net>; from jblack@linuxguru.net on Tue, Oct 22, 2002 at 01:24:48PM -0400
On Tue, Oct 22, 2002 at 01:24:48PM -0400, James Blackwell wrote:
> Though I'm sure you remember what you've said, I'll summarize for those
> that somehow managed to slip into this thread out of context. You write a
> proprietary source code revision system by the name of bitkeeper. You
> offered free licences to linux kernel developers among others. Your
> motivation is that you can use linux kernel development as a showcase
> example when you hunt down people that are willing to pay you.
This is where we disagree. BitKeeper was started to help Linus.
Pure and simple. Maybe it's not a well known thing, I thought it was,
but it's true all the same. I quit my job at Cobalt, had about 4 or
5 hour design discussion with Linus, DaveM and Richard Henderson on my
living room floor and got to work.
The business side of BK came into being after it became clear it was
a much bigger job than we had originally hoped. We either had to make
BK pay for itself or drop it long before it was useable. From a free
software point of view I can see where you would wish we had dropped it.
But free software wasn't our goal, our goal was to off load Linus and
help Linux. Yeah, it would be nice if we could have somehow done that
with a free software product. When you demonstrate how to do that, I'll
be happy to follow in your footsteps. Until then, the license is how it
is because that's only known way that will produce enough money to support
the product.
Try to understand that the point is to support the kernel development
process, not make RMS or you happy, and it costs a boatload of money
to do what we are doing. There's another man year of work put into
BitKeeper every month. I don't see you volunteering to pay for that
continued development. When you do, we'll talk, until then you're
just flapping your gums.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-10-22 17:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 17:27 Listmaster request: Blacklist rms@gnu.org Christoph Hellwig
2002-10-21 17:44 ` Jon Portnoy
2002-10-21 17:57 ` Roman Zippel
2002-10-21 18:02 ` Christoph Hellwig
2002-10-21 18:16 ` Roman Zippel
2002-10-21 18:32 ` Christoph Hellwig
2002-10-21 18:58 ` Roman Zippel
2002-10-21 19:02 ` Christoph Hellwig
2002-10-21 19:23 ` Roman Zippel
2002-10-22 1:15 ` Rob Landley
2002-10-21 18:02 ` Alan Cox
2002-10-21 17:51 ` Christoph Hellwig
2002-10-21 18:28 ` Matti Aarnio
2002-10-21 18:33 ` Jason Williams
[not found] ` <20021021190244.GB21851@compsoc.man.ac.uk>
2002-10-21 19:23 ` Jason Williams
2002-10-21 21:51 ` DervishD
2002-10-22 1:40 ` Murray J. Root
2002-10-22 1:49 ` Listmaster request: Do not blacklist rms@gnu.org Jeff Garzik
2002-10-22 2:13 ` Andrew Morton
2002-10-22 2:31 ` Larry McVoy
2002-10-22 6:19 ` James Blackwell
2002-10-22 13:42 ` Hans Reiser
2002-10-22 17:50 ` James Blackwell
2002-10-22 15:00 ` Larry McVoy
2002-10-22 17:24 ` James Blackwell
2002-10-22 17:42 ` Christoph Hellwig
2002-10-22 18:12 ` James Blackwell
2002-10-22 18:15 ` Justin Guyett
2002-10-22 17:44 ` Larry McVoy [this message]
2002-10-22 17:46 ` Christoph Hellwig
2002-10-22 18:06 ` Roman Zippel
2002-10-22 18:09 ` Christoph Hellwig
2002-10-22 18:27 ` Christoph Hellwig
2002-10-22 18:06 ` Gerhard Mack
2002-10-22 1:51 ` Listmaster request: Blacklist rms@gnu.org Larry McVoy
2002-10-22 1:56 ` John Jasen
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=20021022104414.L6546@work.bitmover.com \
--to=lm@bitmover.com \
--cc=jblack@linuxguru.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.