From: John Bradford <john@grabjohn.com>
To: alan@lxorguk.ukuu.org.uk, Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, lm@bitmover.com, rms@gnu.org
Subject: Re: Bitkeeper
Date: Sat, 19 Jul 2003 11:33:05 +0100 [thread overview]
Message-ID: <200307191033.h6JAX5IP000918@81-2-122-30.bradfords.org.uk> (raw)
> If everyone spent the time replacing bitkeeper instead of beating up
> Larry they'd get a lot further.
Linux isn't the only free operating system in existance, and although
BK seems to suit the requirements of a lot of Linux developers, that
doesn't mean that it meets the requirements of other free OS
development teams.
I strongly suspect that we'll see a free SCM developed after a few
more years of HURD development, for example.
Doesn't mean we'll switch to it, though, we haven't switched to my bug
database, have we? :-).
John.
next reply other threads:[~2003-07-19 10:08 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 10:33 John Bradford [this message]
2003-07-19 14:00 ` [OT] HURD vs Linux/HURD Linux Kernel Mailing List
-- 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-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 ` Bitkeeper Michael Buesch
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 23:50 ` Bitkeeper James Simmons
2003-07-20 2:50 ` Bitkeeper Zack Brown
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=200307191033.h6JAX5IP000918@81-2-122-30.bradfords.org.uk \
--to=john@grabjohn.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--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;
as well as URLs for NNTP newsgroup(s).