From: Mike Galbraith <efault@gmx.de>
To: Larry McVoy <lm@bitmover.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
John Jasen <jjasen@realityfailure.org>,
Larry McVoy <lm@bitmover.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Lars Marowsky-Bree <lmb@suse.de>, Pavel Machek <pavel@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
vojtech@suse.cz
Subject: Re: Never ever use word BitKeeper if Larry does not like you
Date: Fri, 14 Mar 2003 22:12:50 +0100 [thread overview]
Message-ID: <5.2.0.9.2.20030314205747.00cdae20@pop.gmx.net> (raw)
In-Reply-To: <20030314163727.GE8937@work.bitmover.com>
At 08:37 AM 3/14/2003 -0800, Larry McVoy wrote:
> > > Check with your lawyers again, since Red Hat has posted in the past that
> > > 'similar' namings would be chased after. I think the example they
> used was
> > > 'Pink Fedora'.
> >
> > Having a product name "confusingly similar" to another one _is_ grounds
> > for trademark action. See Lindows, Mobilix etc. (And yes, of course,
> > it's a very subjective thing in many cases.)
product?
> > But simply comparing one product to another is not the same.
> >
> > I'd expect using a name like "BitBucket" to be much more at risk of
> > being a trademark infringement than merely claiming that a project "aims
> > to be BitKeeper compatible" or "can read BitKeeper repositories."
>
>But it can't read BK repositories in many cases. We support compressed
>repositories, it can't read those. We support many corner cases which
>SCCS didn't handle, it can't read those. It can't reproduce all of the
>extensions that we have added. In other words, saying what Pavel has
>is like BitKeeper is like saying cat is like Word because they both read
>data off of disk.
Trivial marketing issue then.
> That's the whole point. If we sit back and let people think that he has
>something remotely similar to BK, it devalues BitKeeper in the mind of
>those people. Since this is a very complex system with lots of subtle
>features, people easily get confused. What Pavel has doesn't approach
>the functionality of CVS, let alone BitKeeper, yet he is describing it
>as a BitKeeper clone. If we allow that, we're just shooting our brand
>name dead.
Do you really think that your customers/potential customers are that
stupid? Is your marketing department so inept that they cannot compete
with something which by your own words is not even _close_ to being
equivalent? Remember, you have repeatedly touted the man-years of effort
involved in replication of BK functionality.
You are (sadly) making a complete _ass_ of yourself. If someone comes up
with a functional clone of BK, that's tough shit. You don't have to help
them, and you are free to hinder them in any way law permits.
In closing, I must say that you aren't the only one pissing me the fsck
off. I'm sick and tired of the entire thread[s]. As long as I can get at
the source, I couldn't give a fsck less what Linus or anybody else likes to
use. As long as tarballs exist and as long as patches hit this list, I'm a
happy camper.
Bah humbug, color me disappointed. I guess I need to start filtering my mail.
-Mike
next prev parent reply other threads:[~2003-03-14 20:57 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 [this message]
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
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=5.2.0.9.2.20030314205747.00cdae20@pop.gmx.net \
--to=efault@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jjasen@realityfailure.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=lmb@suse.de \
--cc=pavel@suse.cz \
--cc=sct@redhat.com \
--cc=vojtech@suse.cz \
/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®