From: Mark Mielke <mark@mark.mielke.cc>
To: Larry McVoy <lm@work.bitmover.com>,
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:30:44 -0500 [thread overview]
Message-ID: <20030314163044.GD1671@mark.mielke.cc> (raw)
In-Reply-To: <20030314160314.GD8937@work.bitmover.com>
On Fri, Mar 14, 2003 at 08:03:14AM -0800, Larry McVoy wrote:
> > 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."
> I'd suggest you hit
> http://www.mandrakesoft.com/search?query=Red+Hat&l=english and
> you'll see all of 9 instances of the term Red Hat on their web site
> and I can't find a single one where they are saying what you say
> they are saying.
Since I don't use Mandrake, I don't normally look at their web page. As I
recall, Mandrake began using the sales strategy that I mention above. Since
then (a few years later), they have branched into their own product. I would
expect any clone to do the same. Eventually people realize that "Hey, I don't
have to have the exact same interface, I can tweak this, and make it better
than the original" and other such things. This is where I put Mandrake now.
> I'm not sure why you think what you do but it's simply incorrect. Brand name
> is a well established business asset and businesses are absolutely allowed,
> and as someone else mentioned (thanks), obligated to protect.
You are allowed to defend your trademark, and out of necessity, you
are effectively obligated to protect your own trademark, however, the
question as to whether a judge would agree with you on a specific
defense claim is always up for grabs.
I suggest the non-BitKeeper supporters choose a different name, however, if
they choose to use a similar name, it is your obligation to defend your name,
and if you win, it will cost you money, and if you lose, it will fortify
the non-BitKeeper supporters' position. This is all normal business.
My position: It sucks to be you Larry. You've put in all this work,
you can't continue to pay your employees if you give your product away
for free, and since you don't give it away for free, people want to
re-invent your product so they can give it away for free. I don't think
the US laws cover your situation. They work a lot better for products such
as the automobile, or fridges, than for you. Sorry.
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 16:12 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 10:51 Never ever use word BitKeeper if Larry does not like you 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
2003-03-14 16:03 ` Larry McVoy
2003-03-14 16:30 ` Mark Mielke [this message]
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=20030314163044.GD1671@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.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