From: Larry McVoy <lm@bitmover.com>
To: Ben Collins <bcollins@debian.org>
Cc: Larry McVoy <lm@bitmover.com>, Pavel Machek <pavel@ucw.cz>,
andrea@e-mind.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: BitBucket: GPL-ed BitKeeper clone
Date: Sat, 1 Mar 2003 08:11:44 -0800 [thread overview]
Message-ID: <20030301161144.GB24536@work.bitmover.com> (raw)
In-Reply-To: <20030301160222.GS2896@phunnypharm.org>
He's not allowed to say "BitBucket is a GPL-ed clone of BitKeeper"
because that implies that BitBucket does what BitKeeper does and nothing
could be farther from the truth.
How about we not turn this into a debate? I politely requested that
people not confuse the world into thinking Product A is the same as
Product B, that's all I requested, it's a reasonable request, we don't
need to debate it. If you feel the need to do so, go for it, but do so
knowing that my silence in no way means that I agree or disagree with you.
On Sat, Mar 01, 2003 at 11:02:22AM -0500, Ben Collins wrote:
> On Sat, Mar 01, 2003 at 07:28:20AM -0800, Larry McVoy wrote:
> > BitKeeper is a trademark, please don't use the BitKeeper name when
> > describing BitBucket. Thanks.
>
> I think he's allowed to use the name so long as he only uses it to
> describe what the purpose of the tool is and recognizes in the same
> document who the holder of the trademark is. Just the same as someone
> can write an article about Windows and Microsoft, or a software product
> can claim that it runs under Windows or MacOS.
>
>
> He's allowed to say "This tool allows you to access a BitKeeper
> repository".
>
>
>
> --
> Debian - http://www.debian.org/
> Linux 1394 - http://www.linux1394.org/
> Subversion - http://subversion.tigris.org/
> Deqo - http://www.deqo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-03-01 16:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 20:02 BitBucket: GPL-ed BitKeeper clone Pavel Machek
2003-03-01 15:28 ` Larry McVoy
2003-03-01 16:02 ` Ben Collins
2003-03-01 16:11 ` Larry McVoy [this message]
2003-03-01 17:30 ` Alan Cox
2003-03-01 16:40 ` John Bradford
2003-03-01 16:42 ` Ben Collins
2003-03-02 23:40 ` Pavel Machek
2003-03-01 17:01 ` Aaron Lehmann
2003-03-01 17:19 ` Bernd Eckenfels
2003-03-01 18:05 ` BitBucket: GPL-ed KitBeeper clone Pavel Janík
2003-03-01 18:39 ` Christoph Hellwig
2003-03-01 22:43 ` Pavel Janík
2003-03-02 9:11 ` Christoph Hellwig
2003-03-02 9:30 ` John Bradford
2003-03-02 9:32 ` Christoph Hellwig
2003-03-03 12:39 ` Pavel Machek
2003-03-03 14:12 ` Alan Cox
2003-03-03 13:57 ` John Bradford
2003-03-03 14:22 ` Richard B. Johnson
2003-03-03 15:08 ` John Bradford
2003-03-03 17:50 ` David Lang
2003-03-03 19:37 ` Pavel Machek
2003-03-03 19:49 ` John Bradford
2003-03-03 14:22 ` Charles Cazabon
2003-03-02 9:57 ` Pavel Janík
2003-03-03 8:05 ` Helge Hafting
2003-03-03 8:28 ` Bernd Eckenfels
2003-03-01 20:58 ` Paul Fulghum
2003-03-02 4:52 ` Mike Galbraith
2003-03-03 0:02 ` Pavel Machek
2003-03-02 5:04 ` BitBucket: GPL-ed BitKeeper clone Ben Collins
2003-03-02 5:10 ` Ben Collins
2003-03-02 23:53 ` Pavel Machek
2003-03-03 0:53 ` Ben Collins
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=20030301161144.GB24536@work.bitmover.com \
--to=lm@bitmover.com \
--cc=andrea@e-mind.com \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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