Slashdot Mirror
Tridge Releases BitKeeper-Compatible Tool
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.
...so goes the soap opera that has become the Linux community
Something Witty Goes Here
so let's keep it civil, eh?
Oh! Civility. I'm afraid we don't have much call for that around these parts. May I interest you in some irony?
KFG
You heard it hear first, Tridge is anti-comments. If you want GCC to continue to support comments, speak up now or forever hold your peace.
There are no trails. There are no trees out here.
A big huge middle finger!
Irony always goes astray here , Perhaps i could intrest you in some apathy.
The only things certain in war are Propaganda and Death. You can never be sure which is which though
From the source code I've seen and debugged, it seems most programmers are anti-comments.
Nobody...
Yes, you are the very very very very first first first person to come up with something THAT original.
Not today, thank you. Perhaps you could come around tomorrow, or maybe the day after? I'll check my calendar, but later, ok?
Infuriate left and right
"heard it hear first"
/. comment, and it's in my comment.
Jesus God, that's one of the dumbest fuckups I've seen in a
There are no trails. There are no trees out here.
A tool that lets you Pull stuff out of BitKeeper. How did he manage to avoid naming it BitPull?
And with the support of the community, and a lot of developer work, they'll be able to reduce Arch's 'help' text down to only 10 words, making it the most powerful source control system.
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
At least it's not
"Ewe herd it here first"
"Ewe herd it here first"
Oh. That's just baaaaad.
Time to get back on topic, that's enough subversion of this thread.
...when you're writing a game...tweak the difficulty of "Easy" to something [your mother] can cope with. -- onion2k
At least you don't get your code-reviewers moderating your code as -1,Redundant and -1,Offtopic. That's almost mean-spirited enough to make me stop submitting "Hello, World" patches.
But I shall persevere. And perhaps, I'll add some CRLFs this time.
BitTaker
Or, for a more exacting description of what their relationship is... rename both tools:
BitKeeper -> BitPitcher
SourcePuller -> BitCatcher
cyn, free software and *nix operating systems enthusiast.
Two "+5 Funny" out of the same post? I bow down to your slash-skills.
Isn't that Wendy's new Logo?
Heh. This reminds me of some of the original UNIX code, from the V6/V7 days.
The startup code was all done in DEC assembly (of course), in a file called locore.s (or something like that - it's been years since I've seen it). Either Brian Kernigham or Dennis Ritchie must have written it; I think it was the former.
Utterly obtuse assembly code, unless perhaps you've spent a good deal of time programming in DEC assembly. Then, no doubt, it was quite clear.
Anyway, about halfway down (after about 50 lines or so), was this priceless comment:
"Here's the tricky part"
Heh. Thanks guys.
The best way to predict the future is to create it. - Peter Drucker.