Slashdot Mirror

← Back to Stories (view on slashdot.org)

Tridge Releases BitKeeper-Compatible Tool

Posted by Zonk on from the taking-it-to-the-next-level dept.

Peter Willis writes "Looking at Freshmeat today (a part of OSTG) it seems Andrew Tridgell has released the BitKeeper-compatible source code management client mentioned on slashdot recently, called SourcePuller. As part of the downloads available for the project you can also get dump files which detail how to pull data from BK trees without the use of libsp. From the README: 'SourcePuller is not intended to be a full replacement for BitKeeper. Instead, you should use SourcePuller as an interoperability tool for situations where you cannot use bk itself. SourcePuller is missing a large amount of core functionality from BitKeeper, and thus is not suitable as a full replacement.'" Article available about the release on The Register.

12 of 189 comments (clear)

  1. As Tridge says in the README by Anonymous Coward · · Score: 5, Informative
    Finally, I would like to point out the obvious fact that Linus was perfectly within his rights to choose bk for the kernel. I personally would not have chosen it, but it was his choice to make, not anyone elses. Linus is now in the unenviable position of changing source code management systems, which is a painful task, particularly when moving away from a system that worked as well as bk did. If you want to help, then help with code not commentary. There have been enough flames over this issue already.
    so let's keep it civil, eh?
    1. Re:As Tridge says in the README by 0x461FAB0BD7D2 · · Score: 5, Funny

      From the source code I've seen and debugged, it seems most programmers are anti-comments.

    2. Re:As Tridge says in the README by Elwood+P+Dowd · · Score: 5, Funny

      "heard it hear first"

      Jesus God, that's one of the dumbest fuckups I've seen in a /. comment, and it's in my comment.

      --

      There are no trails. There are no trees out here.
    3. Re:As Tridge says in the README by indifferent+children · · Score: 5, Funny
      it seems most programmers are anti-comments

      You're kidding right? What do you call all of that whitespace that we sprinkle around our code? Those are comments.

      If a block of code is especially self-contained or tricky, then it is surrounded by two carriage-returns before the block and two carriage-returns after the block.

      If some statements are part of a loop, then we gratuitously indent them. That's not for the compiler's benefit; those are comments.

      Don't even get me started on our extreme generosity in supplying names (not just types!) in our function and method prototypes. What, you want us to draw you a map?



      BTW, I would submit more Insightful comments in my code if only my peers with good karma had Mod Points at code review time.

      --
      Censorship is telling a man he can't have a steak just because a baby can't chew it. --Mark Twain
  2. Might come in handy now by Anonymous Coward · · Score: 5, Interesting

    with the move away from bitkeeper. :-D

    On a serious note, it's good that this apparently oh so evil piece of software is finally out in the open, so that the people can see that all the fuss was about a tool that allows you to get your data that is managed by a propietary tool. How evil...

    1. Re:Might come in handy now by LiENUS · · Score: 5, Informative

      Just a note, this tool assists in no way with the move away from bitkeeper, it was only of benefit when the linux kernel was still in bitkeeper. All this lets you do is pull source from a bitkeeper server, it does not replace the bitkeeper server. The way this benefits the open source community is now developers can begin intregrating this library into other development systems (like IDEs) and allowing bitkeeper integration.

  3. Like Grains of Sand in an Hourglass... by jeff_schiller · · Score: 5, Funny

    ...so goes the soap opera that has become the Linux community

    --
    Something Witty Goes Here
  4. Re:Why not GNU Arch? by space_dude_27 · · Score: 5, Insightful

    Perhaps because Tridge never set out to create a replacement for BK - merely a tool that would interoperate with it and enable you to get source out of a BK repository without actually running the BK client.

  5. Logo? by Anonymous Coward · · Score: 5, Funny

    A big huge middle finger!

  6. Re:Why not GNU Arch? by 0x461FAB0BD7D2 · · Score: 5, Insightful

    Flywheels has a history of linking articles at his site, PressEsc to un-related stories and comments, in order to boost his PageRank.

    He has even linked to Google to redirect to his page so that he escapes detection from mods.

    Feel free to check his history.

  7. Why the P.C name? by thehunger · · Score: 5, Funny

    A tool that lets you Pull stuff out of BitKeeper. How did he manage to avoid naming it BitPull?

    1. Re:Why the P.C name? by williw · · Score: 5, Funny

      As soon as I read your comment, I immediately thought he should have call it PitBull or KeepBitter (get it... reverse engineering reverse name, unintended consequences. har har har)