Slashdot Mirror

← Back to Stories (view on slashdot.org)

BitMover Releases Open Source BitKeeper Client

Posted by CowboyNeal on from the bits-a-shakin dept.

diegocgteleline.es writes "Larry McVoy, the owner of BitKeeper (also one of the guys behind LMbench) has posted a message to linux-kernel where he announces a open source client of BitKeeper, which would only allow synching against BK trees. It looks like it's licensed under the NWL (No Whining License) that will force you to 'not whine about this product or any other products from BitMover, Inc.'"

5 of 255 comments (clear)

  1. Re:Strange by sampowers · · Score: 5, Informative

    Don't be a stupid. At least read the mailing list posting:

    Don't worry about the license, it's a joke. BSD license OK with everyone? /blockquote
  2. FTFA... by FireballX301 · · Score: 5, Informative

    Don't worry about the license, it's a joke. BSD license OK with everyone?

  3. Bitkeeper website by kihjin · · Score: 5, Informative

    "BitKeeper has made me more than twice as productive, and its fundamentally distributed nature allows me to work the way I prefer to work - with many different groups working independently, yet allowing for easy merging between them."
    -- Linus Torvalds, February 2004

    Linus did it. I can too! *jumps on the bandwagon*

    --
    This slashdot-related signature is a stub. You can help kihjin by expanding it.
  4. Presentation about BitKeeper by irabinovitch · · Score: 5, Informative

    Larry McVoy, BitMover Founder, gave a great talk about BitKeeper and the delta development model at SCALE 3x (Southern California Linux Expo) last month. Its available online here. -Ilan

  5. Re:I wonder how this bitkeeper thing compares by Anonymous Coward · · Score: 5, Informative
    It compares much better than perforce.

    With Bitkeeper it's very easy for every organization - and even every developer - to have his own "fork" of the tree which acts as a "master repository" for others to create branches off of.

    For example, within RedHat, they can have one (or many) child branches from Linus's branch (or any other developer's branches); and "reparent" the branches as needed to merge in the various pieces they need. Other employes' repositories may point to one inside RedHat; or they may point to Linus's; and of course they can "reparent" their repository to switch between the two as needed.

    Similarly, any company or group of developers can have similar structures.

    Also; it's important to note that not everyone needs access to a "master repository"; and that indeed no-one needs access to a "master repository" except when they're merging with that master.

    Bitkeeper works perfectly on my laptop in disconnected mode - and I have the full power of the source control system on my laptop even with no net access - I can create branches, merge branches, etc. If I'm traveling with someone else from the company I can merge my branches with his merely with a cable between the laptops - no connection to the home office is needed.


    We used perforce at a previous company I was at with offices in China, Taiwan,Romania, and California and it was a horrible experience. Connecting to oversees repositories was painful; and merging changes between the oversees repositories sucked even worse.

    Try BitKeeper. I'm sure you'll switch.