Slashdot Mirror
Linus Tries Out BitKeeper
Flammon writes: "Linus has been overloaded
with patches for a while and recently the issue started to become hot again. In an unprecedented move, Linus has started using BitKeeper, as reported by Linux Today. The benefits of BitKeeper are already showing from the large amount of detail provided in the latest unstable kernel pre-release." eirikref adds: "Read Linus' own statement and take a look at the BK web interface."
I wonder if the nice people at Ask Jeeves are going to mind having their (presumably trademarked) logo swiped for this?
you can neuter the page-widening effect (to read honest trolls in peace, natch) by setting something like this as your default style sheet:
BLOCKQUOTE { margin: 0.1em 0 }
BLOCKQUOTE { margin-left: 5px; margin-right: 5px }
Probably screws up some other stuff, but who's really lame enough to use BLOCKQUOTE anyway?
It's high time he told the community to screw off for a bit.
It's his friggin' hobby, after all. If people don't like the way he deals with it, maybe they ought to go work for a more personable coder on another OS, like, say, Theo De Raadt.
Scary thought, hey?
--------
Bleah! Heh heh heh... BLEAH BLEAH!!! Ha ha ha ha...
Linux uses pine! Look at the selm tag!
Pine.LNX.4.31.0202051928330.2375-100000
How we know is more important than what we know.
Linus doesn't need bitkeeper,
He needs NOS on his stylish Saab!
that way he would spend less time commuting to his stupid job at suckmeta and spend more time on his hot wife, and on the kernel.
I modded my Cavalier Type-R to get me to work 85% faster so i could spend more time on ebay looking for mods. Bling!Bling!
I live my life one quarter pounder at a time -Vinh Diesel
Bitkeeper is available under two licenses. The commercial license costs money and comes with support. The non-commercial license does not cost money., but it has a requirement that all your ChangeLogs must be sent to a world-readable server controlled by BitMover.
;-)
Bitkeeper source is available, but it's illegal to redistribute a version of Bitkeeper with the mandatory open logging stripped out.
Bitmover Inc. wants to avoid the situation where people use bitkeeper like gcc, taking free software tools but not giving anything back. You can pay Bitmover money, or you can use a free-as-in-beer version that is suitable for software libre and unsuitable for closed-source software.
Hi Larry
Life's a bitch but somebody's gotta do it.
A few years ago the government convienently yanked energy out of the cpi. Does anyone find any possible correlation between this enron scam and this prior government action?
--Why ask why is a recipe for explotation
search the frickin' web
In other news Ladies and Gentlemen - it has been reported that Linus has been seen wiping his ass with kleenex instead of toilet paper. You heard it here first.
/me shuts up now.
Seriously, Linus has been exploited so bad by his very own community, that he almost stands as a pop-star rather than an OS hacker.
my sig is so witty and fun - it tickles almost everyone who reads it.
--Mike--
For your information: criterion is singular, criteria is plural. Don't screw it up next time.
In other news, demons all over Hell were seen lacing up their skates for the upcoming hockey match against the U.S. National team.
Thats not Hell! Thats Canada!
oh, wait..
An optimist believes we live in the best world possible; a pessimist fears this is true.
I don't blame Linus for trying out Bitkeeper. After using Rational (formerly Atria) Clearcase for several years, and then working on a project using CVS, I can't believe that CVS is hyped the way it is. Sure, it works for small projects.
Why nothing can beat Clearcase:
1. Clearcase is integrated into the OS and the repositories are actual filesystems. I create a "config_spec" that lists all of the branches and labels that I want to see. I don't have to checkout stuff, and copy a large project into a private directory. If I want to see another developer's change to a small set of files, I just add his/her branch to my config_spec. No recopying or anything like that.
2. Clearmake. If someone else in my organization builds the same object file (from the exact same version of the source file), I don't have to rebuild it. I love typing "clearmake" of something huge that I've never built before, and it is done in no time!! If something does have to be rebuilt, builds are distributed across a dozen or so machines.
3. Real branches. When I am developing something, I make a temporary branch on all the files. If I want to be able to let someone else use my "development" branches, I just let them know what the branch name is. When it is production-ready, we just merge the development branch into the main branch. No such thing as patch files in Clearcase world.
There is a reason that Clearcase is expensive and proprietary.
That comment really is there in the old V6 source. I went looking for it.
Fascism starts when the efficiency of the government becomes more important than the rights of the people.