From: Mark Mielke <mark@mark.mielke.cc>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Never ever use word BitKeeper if Larry does not like you
Date: Fri, 14 Mar 2003 11:00:40 -0500 [thread overview]
Message-ID: <20030314160040.GB1671@mark.mielke.cc> (raw)
In-Reply-To: <20030314120604.GE3020@merlin.emma.line.org>
On Fri, Mar 14, 2003 at 01:06:04PM +0100, Matthias Andree wrote:
> If BitMover think that you're using their protected brand/trademark to
> promote your product, then they can demand that you omit doing so.
I have to disagree. What is CSSC vs SCCS, or GAIM vs AIM or any other such
thing that is regularly done.
If Larry's product truly is of the calibre that he believes it to be, the
only way for a GPL'ed clone to meet the same standards would be for the GPL
community to put in a lot of hard work. As long as no lines of code are
copied from the Bit Keeper source code, I don't see any legal grounds that
could be stood on that would not set a very horrible precidence for all other
GPL works that present compatible interfaces to proprietary code.
I respect Larry's position. He has a company invested in this. It is so much
easier for somebody to come along 5 years later, pick up all the good ideas,
and implement something better, than to actually develop a product from
scratch. This sort of 'ease' is almost anti-competitive.
But, that is why the patent system exists, and a patent is the only
real way for Larry to defend himself. He cannot demand that people not
mention the name Bit Keeper any more than the owner of SCCS demand
that Bit Keeper or CSSC not mention the name SCCS.
I don't envy Larry's position, however, from a GPL-subscriber's
perspective, Larry's product is anti-competitive and needs to be
replaced by a functionally equivalent, potentially interface
compatible, GPL version of Bit Keeper.
It is just how things work. The suggested that Red Hat could be used
as the basis for a different product, and the Red Hat lawyers would
have a field day, is moot as well, since companies like Mandrake have
already done this. "Look at us, we're Red Hat with PGCC-compiled
packages, a new install interface, and a few driver modules. Buy our
product instead."
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2003-03-14 15:42 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 10:51 Pavel Machek
2003-03-14 11:19 ` Murray J. Root
2003-03-14 11:50 ` Lars Marowsky-Bree
2003-03-14 13:35 ` Richard B. Johnson
2003-03-14 14:43 ` Larry McVoy
2003-03-14 16:10 ` Alan Cox
2003-03-14 15:14 ` Larry McVoy
2003-03-14 16:11 ` Stephen C. Tweedie
2003-03-14 16:21 ` John Jasen
2003-03-14 16:28 ` Stephen C. Tweedie
2003-03-14 16:37 ` Larry McVoy
2003-03-14 16:56 ` Linux-kernel-revision-control list (was: Re: Never ever use word BitKeeper if Larry does not like you) Christian Daudt
2003-03-15 2:29 ` Joshua Kwan
2003-03-16 7:56 ` Josef Roehrl
2003-03-14 17:09 ` Never ever use word BitKeeper if Larry does not like you Davide Libenzi
2003-03-14 18:29 ` Jeff Garzik
2003-03-14 18:48 ` Davide Libenzi
2003-03-14 17:10 ` Stephen C. Tweedie
2003-03-14 21:12 ` Mike Galbraith
2003-03-15 0:59 ` Stephen Satchell
2003-03-14 18:57 ` Wichert Akkerman
2003-03-14 20:49 ` Roger Luethi
2003-03-14 21:55 ` Eric Sandall
2003-03-15 0:56 ` Stephen Satchell
2003-03-15 3:36 ` Werner Almesberger
2003-03-15 12:20 ` Pavel Machek
2003-03-16 0:57 ` Alan Cox
2003-03-16 5:01 ` Oliver Xymoron
2003-03-14 16:29 ` Alan Cox
2003-03-14 15:29 ` Larry McVoy
2003-03-14 16:43 ` Alan Cox
2003-03-14 16:43 ` Tom Sightler
2003-03-14 16:58 ` Larry McVoy
2003-03-14 17:56 ` Tom Sightler
2003-03-14 18:34 ` Valdis.Kletnieks
2003-03-14 17:44 ` Pavel Machek
2003-03-14 20:37 ` Teodor Iacob
2003-03-14 18:29 ` Brian McGroarty
2003-03-14 20:33 ` Teodor Iacob
2003-03-14 21:32 ` Brian McGroarty
2003-03-14 12:06 ` Matthias Andree
2003-03-14 15:38 ` Alan Cox
2003-03-14 16:00 ` Mark Mielke [this message]
2003-03-14 16:03 ` Larry McVoy
2003-03-14 16:30 ` Mark Mielke
2003-03-14 23:13 ` Daniel Phillips
2003-03-14 13:42 ` Tomas Szepe
2003-03-14 14:33 ` Never ever send Pavel private mail unless you want him to publish it Vlad@geekizoid.com
2003-03-14 14:50 ` Valdis.Kletnieks
2003-03-14 16:13 ` Mark Mielke
2003-03-17 0:16 ` Stuart MacDonald
2003-03-17 0:44 ` Tim Smith
2003-03-17 8:43 ` Helge Hafting
2003-03-17 0:57 ` Vlad@geekizoid.com
2003-03-17 2:16 ` Stuart MacDonald
2003-03-17 2:16 ` David Lang
2003-03-17 4:37 ` Vlad@geekizoid.com
2003-03-17 6:21 ` Oliver Xymoron
2003-03-17 14:56 ` Vlad@geekizoid.com
[not found] <20030314184009$1b0a@gated-at.bofh.it>
[not found] ` <20030314184009$54f5@gated-at.bofh.it>
[not found] ` <20030314184009$6d9e@gated-at.bofh.it>
[not found] ` <20030314184009$548a@gated-at.bofh.it>
[not found] ` <20030314184009$69b1@gated-at.bofh.it>
2003-03-14 21:48 ` Never ever use word BitKeeper if Larry does not like you Florian Weimer
2003-03-15 0:49 ` John Alvord
2003-03-15 7:51 ` Florian Weimer
2003-03-15 14:32 ` Henning P. Schmiedehausen
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=20030314160040.GB1671@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®