From: Michael Buesch <fsdeveloper@yahoo.de>
To: rms@gnu.org
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Bitkeeper
Date: Fri, 18 Jul 2003 22:30:17 +0200 [thread overview]
Message-ID: <200307182230.17803.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <E19dbGS-00026T-9R@fencepost.gnu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 18 July 2003 21:51, Richard Stallman wrote:
> > If you are trying to copy BK, give it up. We'll simply follow in the
> > footsteps of every other company faced with this sort of thing and
> > change the protocol every 6 months. Since you would be chasing us
> > you can never catch up. If you managed to stay close then we'd put
> > digital signatures into the protocol to prevent your clone from
> > interoperating with BK.
>
> I think it would be appropriate at this point to write a free client
> that talks with Bitkeeper, and for Linux developers to start switching
> to that from Bitkeeper. At that point, McVoy will face a hard choice:
> if he carries out these threats, he risks alienating the community
> that he hopes will market Bitkeeper for him.
Hi Richard.
You're ready for a small flame-war with Larry? 8-)
First I think, this list isn't the correct place for starting
a bk-flame again.
But I also share your opinion, that it's time to write even a
free client.
But how hard will it be? How big is the knowlege of the
protocols bk uses? It'll be not easy, but for sure very interesting.
- --
Regards Michael Buesch
http://www.8ung.at/tuxsoft
Penguin on this machine: Linux 2.4.21 - i386
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/GFjZoxoigfggmSgRAs7XAJ4tZybSXfPTdk7I9cSIuUYSM72xXACfaeOZ
k2QsR3KsL6HxXXj1y/ECdn0=
=2Wzr
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-07-18 20:16 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-18 19:51 Bitkeeper Richard Stallman
2003-07-18 20:06 ` Bitkeeper Rik van Riel
2003-07-18 20:22 ` Bitkeeper nick
2003-07-18 20:40 ` Bitkeeper Shawn
2003-07-18 21:28 ` Bitkeeper Alan Cox
2003-07-19 23:45 ` Bitkeeper Pavel Machek
2003-07-20 0:23 ` Bitkeeper Jeff Garzik
2003-07-18 20:32 ` Bitkeeper Shawn
2003-07-18 20:44 ` Bitkeeper Rik van Riel
2003-07-19 18:42 ` Bitkeeper Jan-Benedict Glaw
2003-07-19 18:49 ` Bitkeeper Larry McVoy
2003-07-19 18:57 ` Bitkeeper Jan-Benedict Glaw
2003-07-19 19:05 ` Bitkeeper Larry McVoy
2003-07-19 20:02 ` Bitkeeper Jan-Benedict Glaw
2003-07-18 20:09 ` Bitkeeper Trever L. Adams
2003-07-18 20:44 ` Bitkeeper Shawn
2003-07-18 21:03 ` Bitkeeper Larry McVoy
2003-07-18 21:58 ` Bitkeeper Trever L. Adams
2003-07-18 22:17 ` Bitkeeper Mike Fedyk
2003-07-18 22:39 ` Bitkeeper Alan Cox
2003-07-19 8:20 ` Bitkeeper Eric W. Biederman
2003-07-19 15:34 ` Bitkeeper Mark Mielke
2003-07-18 22:29 ` Bitkeeper Scott Robert Ladd
2003-07-18 20:30 ` Michael Buesch [this message]
2003-07-18 20:36 ` Bitkeeper Shawn
2003-07-18 20:44 ` Bitkeeper Larry McVoy
2003-07-18 21:03 ` Bitkeeper Shawn
2003-07-18 21:08 ` Bitkeeper David Schwartz
2003-07-18 21:28 ` Bitkeeper Shawn
2003-07-18 21:23 ` Bitkeeper Alan Cox
2003-07-18 21:50 ` Bitkeeper David Lang
2003-07-18 21:54 ` Bitkeeper Valdis.Kletnieks
2003-07-18 22:16 ` Bitkeeper Alan Cox
2003-07-18 22:01 ` Bitkeeper Trever L. Adams
2003-07-18 22:27 ` Bitkeeper Larry McVoy
2003-07-19 9:45 ` Bitkeeper Marcus Metzler
2003-07-19 20:42 ` Bitkeeper Adrian Bunk
2003-07-19 21:57 ` Bitkeeper Larry McVoy
2003-07-19 22:28 ` Bitkeeper Adrian Bunk
2003-07-19 22:39 ` Bitkeeper Larry McVoy
2003-07-19 23:45 ` Bitkeeper Adrian Bunk
2003-07-20 0:02 ` Bitkeeper Larry McVoy
2003-07-20 0:10 ` Bitkeeper Tupshin Harper
2003-07-20 0:26 ` Bitkeeper Valdis.Kletnieks
2003-07-20 1:11 ` Bitkeeper Jeff Garzik
2003-07-20 0:23 ` Bitkeeper Jeff Garzik
2003-07-20 0:28 ` Bitkeeper jiho
2003-07-20 0:30 ` Bitkeeper Valdis.Kletnieks
2003-07-20 0:50 ` Bitkeeper Larry McVoy
2003-07-20 0:22 ` Bitkeeper Jeff Garzik
[not found] ` <3F19DA04.80809@c-zone.net>
[not found] ` <20030719235526.GA31428@work.bitmover.com>
2003-07-20 0:21 ` Bitkeeper jiho
2003-07-19 23:57 ` Bitkeeper Pavel Machek
2003-07-18 21:06 ` Bitkeeper Jörn Engel
2003-07-18 22:00 ` Bitkeeper Svein Ove Aas
2003-07-18 22:25 ` BK is not heaven, sure [Was: Re: Bitkeeper] J.A. Magallon
2003-07-18 23:50 ` Bitkeeper James Simmons
2003-07-19 1:05 ` offtopic crap (was Re: Bitkeeper) David S. Miller
2003-07-19 15:00 ` Jeff Garzik
2003-07-20 2:50 ` Bitkeeper Zack Brown
-- strict thread matches above, loose matches on Subject: below --
2003-07-19 16:00 Bitkeeper John Bradford
2003-07-19 16:17 ` Bitkeeper Mark Mielke
2003-07-19 10:33 Bitkeeper John Bradford
2003-02-15 8:21 BitKeeper John Bradford
2003-02-15 22:26 ` BitKeeper Pavel Machek
2003-02-16 11:40 ` BitKeeper John Bradford
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=200307182230.17803.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rms@gnu.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