At some point the SCM vendor (decided|was forced) to declare he would no longer provide the system for free.
You left out an important (to me) fact here: This was triggered because a member of Linus' team that was gung-ho "everything in the world should be open-source" guy wrote a reverse-engineering of the data format for BitKeeper, violating the agreement Linus had with Larry, even over Linus' persistent and deliberate advice to the contrary.

So, part of the story is "even if you're an open-source zealot, follow the rules!"

On the other hand, from lemons came lemonade. I'm strongly considering using Git on projects because of its nice distributed creativity model. (No, I can't seem to get SVK to work on my machines, and the rest of the stuff looks even further down the scale. Git compiles and installs trivially, except for the documentation stuff.)

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

update: yes, sorry, I misheard the story. Not a "member of his team", but perhaps someone who should have understood the consequences of his act.

In reply to Re: Linux kernel Bitkeeper mess (OT) by merlyn
in thread Learning How to Use CVS for Personal Perl Coding Practices by neversaint

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.