From: Ben Collins <bcollins@debian.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Larry McVoy <lm@bitmover.com>, Pavel Machek <pavel@ucw.cz>,
andrea@e-mind.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BitBucket: GPL-ed BitKeeper clone
Date: Sat, 1 Mar 2003 11:42:20 -0500 [thread overview]
Message-ID: <20030301164219.GV2896@phunnypharm.org> (raw)
In-Reply-To: <1046539842.23347.11.camel@irongate.swansea.linux.org.uk>
On Sat, Mar 01, 2003 at 05:30:42PM +0000, Alan Cox wrote:
> On Sat, 2003-03-01 at 16:11, Larry McVoy wrote:
> > 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.
>
> Something is wrong, I agree with Larry.
>
> He should instead say "A tool for accessing bitkeeper repositories" or
> "bitbucket compatible proprietary tools are available from .. " ;)
I can agree with that. At first though, he said not to use the name at
all, without regard to wording.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-03-01 16:33 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
2003-03-01 17:30 ` Alan Cox
2003-03-01 16:40 ` John Bradford
2003-03-01 16:42 ` Ben Collins [this message]
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=20030301164219.GV2896@phunnypharm.org \
--to=bcollins@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrea@e-mind.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--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