From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 3Com 3cr990 driver release
Date: Sat, 15 Feb 2003 11:34:38 +0000 (UTC) [thread overview]
Message-ID: <b2l8ke$v55$1@tangens.hometree.net> (raw)
In-Reply-To: 20030214163611.GD3188@work.bitmover.com
Larry McVoy <lm@bitmover.com> writes:
>taking a half decade off to code up an SCM system good enough for
>Linus to use. Without the benefit of having one to copy, by the way.
Using this statement over and over doesn't make it more true.
Linus stated in public that he was/is unhappy with CVS. Without
Bitkeeper he might use Subversion today. But by using Bitkeeper he
made it possible that you and your company started using him as your
posterboy for the "SCM good enough for Linus Torvalds to use". This is
IMHO not correct. BK is just "the first SCM which came along and was
good enough for Linus Torvalds to use it".
I do remember Linus saying that he wants to try out BitKeeper for the
2.5 development tree and if it does not work out, switch to something
else in the 2.6, 2.7... cycle.
The rift that the whole BitKeeper/BitMover stuff has opened in the
kernel developer community IMHO justifies such a step forward . I'd
like to see SVN to be used as an alternative tool. Not because it is
better (it probably is not, but I haven't had a chance to try out BK
because I don't qualify for the free license) than BK but because it
has no strings attached to its usage.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
next prev parent reply other threads:[~2003-02-15 11:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 7:50 3Com 3cr990 driver release David Dillow
2003-02-14 8:20 ` Jeff Garzik
2003-02-14 14:33 ` Alan Cox
2003-02-14 15:19 ` Larry McVoy
2003-02-14 16:54 ` Alan Cox
2003-02-14 16:09 ` Larry McVoy
2003-02-14 17:23 ` Alan Cox
2003-02-14 16:36 ` Larry McVoy
2003-02-14 17:04 ` Tomas Szepe
2003-02-14 17:12 ` Larry McVoy
2003-02-14 18:40 ` Roman Zippel
2003-02-14 18:44 ` Larry McVoy
2003-02-14 18:59 ` Roman Zippel
2003-02-15 11:34 ` Henning P. Schmiedehausen [this message]
2003-02-14 17:28 ` Alan Cox
2003-02-14 23:01 ` Steven Cole
2003-02-14 17:20 ` David Dillow
2003-02-14 20:52 ` Alan Cox
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='b2l8ke$v55$1@tangens.hometree.net' \
--to=hps@intermeta.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.