Slashdot Mirror


Torvalds Unveils New Linux Control System

BlakeCaldwell writes "CNet reports: 'Linux founder and leader Linus Torvalds has launched a new tool, called Git, to manage his software project, after a dispute led him to drop the previous system.' He will start using Git instead of BitKeeper to control the flow of updates and track changes in the kernel." We've covered this previously. Relatedly, ChocLinux writes "Jeremy Allison, who wrote Samba with Andrew 'Tridge' Tridgell, is sticking up for his friend in the row over BitKeeper. "

111 of 527 comments (clear)

  1. how come by phreakv6 · · Score: 2, Insightful

    how come this wasnt even an option in the current poll here. let the replies like "welcome to /. flow"

    --
    fifteen jugglers, five believers
    1. Re:how come by wed128 · · Score: 4, Insightful

      it was. It was called "home grown solution"

    2. Re:how come by dragon_imp · · Score: 2, Funny

      And the poll's still up! I am psychic -- I voted for homegrown. You can, too.

  2. Git? by YrWrstNtmr · · Score: 4, Interesting
    Isn't that a bit of a disparaging name in English as it is spoken in the Olde Country?

    As in "You daft git!"

    1. Re:Git? by 0x461FAB0BD7D2 · · Score: 3, Funny

      Linus got the name from Tridge's response to McVoy.

    2. Re:Git? by PeterBrett · · Score: 5, Informative

      Yes, that's right; from the git README:

      "git" can mean anything, depending on your mood.

      - random three-letter combination that is pronounceable, and not
      actually used by any common UNIX command. The fact that it is a
      mispronounciation of "get" may or may not be relevant.
      - stupid. contemptible and despicable. simple. Take your pick from the
      dictionary of slang.
      - "global information tracker": you're in a good mood, and it actually
      works for you. Angels sing, and a light suddenly fills the room.
      - "goddamn idiotic truckload of sh*t": when it breaks
    3. Re:Git? by Saunalainen · · Score: 5, Informative

      Indeed - Linus has already explained the reasoning behind this name.

    4. Re:Git? by Arathrael · · Score: 4, Informative

      It sure is, I believe it's derived from the Scottish term get, usually used to refer to an illegitimate child. 'Git' itself is used more broadly though, in much the same way as 'bastard' is.

    5. Re:Git? by ch-chuck · · Score: 2, Funny

      that's what we appalachains holler at city slickers that'ar trespassing, usually spoken while holding a shotgun.

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
    6. Re:Git? by Striikerr · · Score: 5, Funny

      And if you're too lazy to RTF, here's the quote from the very end of the article.. "When asked why he called the new software, "git," British slang meaning "a rotten person," he said. "I'm an egotistical bastard, so I name all my projects after myself. First Linux, now git.""

    7. Re:Git? by krewemaynard · · Score: 2, Funny

      i believe the phrase is "GIT R DONE!", and has nothing to do with dogs (unless heavy drinking is involved).

      you'd do well to learn some redneck, then try again later.

      --
      I saw it on Slashdot, it must be true!
    8. Re:Git? by hawk · · Score: 2, Funny


      - random three-letter combination that is pronounceable, and not actually used by any common UNIX command.

      Well, *duh*!

      Self respecting unix commands have two letters, noto three, and, furthemore, are not pronounceable.

      That mkdir and rmdir use more than two letters is a long-standing bug--longer even than the screwy footnote/gap bug in words (which dates to Mac Word 1.0)

      hawk

    9. Re:Git? by $rtbl_this · · Score: 2, Informative

      Alternatively, it could be derived from the Arabic for a pregnant camel. As far as I know, it's one of those words whose origin is lost in the mists of time.

      --
      "Are you being weird, or sarcastic?" said Emma. I said I didn't know because I get the two feelings mixed up.
    10. Re:Git? by ewe2 · · Score: 2, Funny

      It should have been called 'dickhead' then, much more appropriate and has an Australian air to it.

      --
      insecurity asks the wrong question irritation gives the wrong answer
    11. Re:Git? by mattspammail · · Score: 5, Funny

      How about "Git Isn't Translatable"?

      --
      Now accepting PayPal donations!
    12. Re:Git? by Jose · · Score: 2, Funny

      What about "Git Isn't a TLA"

      --
      The basic sleazeware produced in a drunken fury by a bunch of UCBerkeley grad students was still the core of BIND. --PV
    13. Re:Git? by mink · · Score: 2, Interesting

      Looking at the evidence it seams thoe only sane reasonable person in the whole stupid ordeal is Tridge.

      Telnet [servername] 5000

      [servername]> help

      does not seem to me to be evil. But if it will help we can ban all forms of remote system access, to keep companies like bitkeeper safe.

      --
      Well I've wrestled with reality for thirty five years doctor, and I'm happy to say I finally won out over it.
    14. Re:Git? by GoRK · · Score: 2, Funny

      That mkdir and rmdir use more than two letters is a long-standing bug--longer even than the screwy footnote/gap bug in words (which dates to Mac Word 1.0)

      A bug which was fixed by DOS!

    15. Re:Git? by smittyoneeach · · Score: 2, Funny
      That explains a lot of things around here...
      Verily thinketh the n00b in his heart: things around here are explainable, foreasmuch as to have meaning, even unto the cusp of there being a point thereto.
      Then the depression setteth in...
      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  3. zdnet.co.uk by fish34 · · Score: 5, Informative

    What an awful zdnet article, "But now it seems that some open source developers haven't kept up their end of the bargain. " Tridge wasn't bound the by the license. "Tridgell's decision to reverse-engineering Bitkeeper. The resulting clone would violate BitMover's intellectual property -- something McVoy wasn't going to sit back and watch happen." Again, no, it wouldn't. My understanding is that reverse engineering for interoperability is legally fine. Think of Samba..

    1. Re:zdnet.co.uk by Anonymous Coward · · Score: 5, Insightful

      Tridge didn't even reverse engineer Bitkeeper, he was just trying to reverse engineer the *file format* to prevent vendor lockin.

      The Linux kernel history was being held hostage to Bitkeeper's good graces. If the business reasons for letting kernel developers do advertisement and Beta testing disappeared, the free version would inevitably disappear and kernel developers would be SOL (as they are now).

      If it weren't for the foresight to mirror *some* of the BitKeeper information in CVS, the kernel developers would have no developement history other than what they can dig up in the archives.

    2. Re:zdnet.co.uk by Naikrovek · · Score: 5, Insightful

      His "reverse engineering" was this:

      telnet bitkeepermachine
      HELP
      --seeing the list of available commands--
      clone filename.c

      seeing a bunch of garbage, then shortening it to:

      echo "clone filename.c" | telnet bitkeepermachine > filename.c

      wow that's what I call reverse engineering!

    3. Re:zdnet.co.uk by Krehbiel · · Score: 5, Insightful
      My understanding is that reverse engineering for interoperability is legally fine.

      Reverse-engineering for interoperability is legally fine, unless you're bound by a license not to do it. Those who've accepted the free BitKeeper client (or who bought BitKeeper) are subject to just such a license.

      If Tridgell never acceted the BitKeeper license, then he's not bound by it, and there's nothing illegal about what he did. But you know, you don't have to do something illegal to piss people off. :-(

      McVoy got pissed that someone did what he didn't want anyone to do, so he decided to stop maintaining the free BK client. (He's also trying to say that Tridgell should have been subject to the BitKeeper license, since he happens to be a contractor doing some work for a company that had accepted the BK license. I don't buy that one.)

      Torvalds got mad that something somebody got McVoy mad, so that now his choice source control tool isn't freely available anymore. He ranted against Tridgell, but that's misplaced, I think. Torvalds isn't fully into the "Free Software" philosophy (despite his use of the GPL for Linux), and so doesn't see any value in Tridgell's work and calls it "evil."

    4. Re:zdnet.co.uk by shaitand · · Score: 5, Insightful

      Botching the BitKeeper donation was hardly a bad thing, and it is what most wanted anyway.

      There is a reason why he reverse engineered the file format and not the source control system. BitKeeper stored the code in a proprietary data format, their IP is the only data capable of reading that format. If BitMover ever chose to revoke all licenses to use their IP to read the format it would bar the kernel developers from retrieving the kernel source code stored in the system.

      Tridge was not building a source control system to mimic BitKeeper, Tridge simply reversed the file format so that the ability for kernel developers, linus, and the world; to access the kernel source code was not subject to BitMovers good graces.

    5. Re:zdnet.co.uk by pe1rxq · · Score: 2, Insightful

      Yep. No problems here. Tridge didn't know that he was accessing something that wasn't for public access, didn't know that it was a BitKeeper daemon, and didn't know that there was a pesky license agreement that forbade what he was doing.


      Downloading something from a publicly accessable server using no authentification whatsoever is perfectly fine and has nothing to do with the bitkeeper license.
      If I download a html file from a http server the Apache foundation can say whatever they want but they couldn't stop me...

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    6. Re:zdnet.co.uk by zulux · · Score: 2, Interesting

      Tridge is not in the right. Tridge has demonstrated his immaturity by disregarding the effects of his actions on others

      Tridge displayed amazing foresight - he was the problem of Bitkeepers vendor lock-in and was doing something about it before Bitkeeper changed their format again.

      Truns out that Tridge was right not to trust the Bitkeeper people with the Linux kernal.

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    7. Re:zdnet.co.uk by LWATCDR · · Score: 2, Interesting

      "Tridge is not in the right. Tridge has demonstrated his immaturity by disregarding the effects of his actions on others. Tridge has the skill to write a source control system from scratch, and intentionally chose not to - all claims to moral superiority died with that decision."
      The problem I have with all of this is that the license that bitkeeper used was the least free I have ever heard of. If you used it you could not not "work" on a competing program! If Tridge had not signed that agreement how was what he did any more immoral than Open Office reverse enginering the Office file format? If Microsoft said that if you use outlook express you can not work on any other mail reader people would be after blood.
      Frankly Bitkeeper got more free press from Linus using it and say how great it is than they could ever have afforded to pay for. I admit that I have no problem with none free software but I do have a problem when I am being told what I can and can not work on! Think about it Bitkeeper was less free than Windows! Not only did you not have the source you where not allowed to write a competing program! I was all with using Bitkeeper until I heard about the none compete part. I feel everyone has the right not to give away there work but I have a problem when they tell me what I can write.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    8. Re:zdnet.co.uk by DrSkwid · · Score: 2, Informative

      not so hard to reverse engineer

      telnet bitkeeper 5000
      Connected to bitkeeper.
      Escape character is '^]'.
      help

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    9. Re:zdnet.co.uk by DrSkwid · · Score: 4, Insightful

      repeat after me : protocols cannot be patented / copyrighted

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    10. Re:zdnet.co.uk by Klivian · · Score: 2, Interesting

      >and it is what most wanted anyway.
      Actually Linus and many other core kernel hackers did not want this. And the kernel developers was never forced to use BK, and the few who did not like tke BK license managed just fine whitout. What Tridge did was force his political/religious agenda onto the kernel developers. Besides BitMover did not revoke their license on a whim, they tried a reasonable dialog involving Linus. However one try to present the facts one thing remains. That is Tridge is the worst case of zealot preaching freedom of sw, but not respecting other peoples freedom to choose and work with any license they want.

    11. Re:zdnet.co.uk by ttrafford · · Score: 2, Insightful
      Tridge displayed amazing foresight
      There's no prophesy like a self-fullfilling prophesy.
    12. Re:zdnet.co.uk by LordNimon · · Score: 2, Insightful
      Botching the BitKeeper donation was hardly a bad thing, and it is what most wanted anyway.

      That's ridiculous. If people didn't want to use BK, then they just wouldn't. Linus did not approve of Tridge's actions.

      If BitMover ever chose to revoke all licenses to use their IP to read the format it would bar the kernel developers from retrieving the kernel source code stored in the system.

      Now that's ironic. Tridge's actions are what caused BK to revoke the license. If he had done nothing, then we'd all still be happily using BK.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    13. Re:zdnet.co.uk by drinkypoo · · Score: 5, Insightful

      You and Linus should get together and have a big "completely missing the fucking point" party. I have always respected Linus Torvalds greatly for his technical and societal contributions until this whole flap.

      Anyway, everyone wanted a way to get ALL data in and out of the repository to make it easier to merge in third party patches. The only differences here between (say) Linus and tridge are that Linus is McVoy's buddy who is pissed off that he no longer gets to use software, and tridge is a champion of Open Source who feels that we should be in charge of our own data. Remember, Linus does not care if software is Open. He wrote Linux that way based on a pragmatic decision.

      However one try to present the facts one thing remains. That is Tridge is the worst case of zealot preaching freedom of sw, but not respecting other peoples freedom to choose and work with any license they want.

      Now, I actually pride myself on being a creative asshole, but sir, you take the prize. Tridge was trying to do one thing: INTEROPERATE WITH BITKEEPER. He was NOT writing a replacement. How could he be, he was only writing a client? This cannot possibly hurt bitkeeper; they sell a service, and there are already other clients. He was trying to develop functionality that did not exist, and that bitmover does not want to provide.

      Why do they not want to provide this functionality? Why do they want to hold the interface to YOUR DATA hostage? So that they can lock you in to bitkeeper. In other words what you and Linus are both completely missing in your ire is the fact that bitmover is entirely microsoftian in this regard. They want to lock down the standards and prevent people from using them (McVoy threatened to repeatedly change the protocol in order to stay a step ahead of tridge - I'm sure that's going to provide a lot of benefit to bitmover's customers!) so that it is extremely inconvenient to move to another SCMS. This is 100% the same as Microsoft's file format strategies; hell, if they open DOC, in some ways they'd be LESS restrictive than bitmover - fact not fiction.

      Reverse engineering for the purposes of interoperability is a time-honored tradition, and protected at least here in the U.S. by federal law including the oft-reviled DMCA. Perhaps you should adjust your attitude, I think it's poking out of your ass.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    14. Re:zdnet.co.uk by ozbird · · Score: 5, Insightful
      Oh pu-lease...

      Tridge reversed engineered BitKeeper in the same way I "reversed engineered" SMTP:
      telnet <hostname> <portnumber>
      help
      There are a bunch of developers saying "I told you so" to Linus; BitKeeper may have been a wonderful product, but it was a train wreck waiting to happen. If Tridge had done nothing, the result would have been the same except that Linus would have to find another scapegoat to take his frustration out on.

    15. Re:zdnet.co.uk by killjoe · · Score: 5, Insightful

      "Now that's ironic. Tridge's actions are what caused BK to revoke the license. If he had done nothing, then we'd all still be happily using BK."

      The problem is that Larry is an insane person. Let me draw up an analogy for you.

      Let's say there is a park close to your house and you like to walk your dog there.

      Larry one day calls your boss and says that you are ugly, your dog is ugly, and he wants your boss to fire you unless you stop walking your dog when you get home.

      OF course both of you are a little bewildered because a) you are doing something on your own time and b) what you are doing is perfectly legal. So your boss tells him that no he is not going to fire or rebuke you in any way.

      Larry then calls back and says that if you don't stop walking your dog he will beat of on his friend linus. You know linus and think he is a good guy but you figure linus can take care himself and indeed is a pretty good jodo expert so you tell him no again.

      Larry then lashes out at his friend and his friend is now mad at you!.

      This is what happened. Larry stabbed his friend in the back in order to make tridge stop doing something he had legal right to do.

      Larry is an immoral insane person and linus had no right to yell at tridge for larry's actions.

      --
      evil is as evil does
    16. Re:zdnet.co.uk by drinkypoo · · Score: 2, Insightful

      No, using software from a company run by a megalomaniac who wants to control your data and lock you into his solution is the part that is stupid. It was stupid when Linus decided to do it in the first place, and it is equally stupid today.

      Linus' refusal to admit that it was stupid to use McVoy's system is the real problem here. He says he's an egomaniac; I guess it's true. His ego won't allow him to admit that it was a ridiculous decision. He seems to be buddies with McVoy, so that may be part of it as well.

      Linus chose to use an unfree system because it provided him with certain advantages. He claims he is a pragmatist and not an open source champion, but first of all taking the easy way out and using BK was NOT pragmatic, because it was inevitable that something like this would happen eventually; Second, clearly he has the ability to write the kind of software he needs, which will necessarily have licensing terms he can live with. This makes much more sense than being locked in to proprietary software.

      The software was not self-defeating. It solved the very problem it set out to solve - being able to manipulate Linux data (which doesn't even BELONG to bitmover!) in the way that the developers need to manipulate it to be effective. Granted, it did cause many other problems, but I think it can be seen as a success for open source.

      Again, Linus says he's a pragmatist, but one of the primary goals of Linux was extensibility and redistribution. You cannot have that without Open Source! So really, by supporting closed-source software, Linus was shooting himself in the foot. Since Linus made that decision, and this is hurting all of us, Linus is shooting us ALL in the foot. Granted, the gun went off when tridge bumped Linus, but he is the one who had his hand on the grips and his finger on the trigger.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    17. Re:zdnet.co.uk by Fahrenheit+450 · · Score: 2, Insightful

      Tridge did nothing to linus. It was Larry who took away the license, not tridge.

      Tridge was just minding his business doing something he had full legal right to do.


      Last time I checked, I have the full legal right to sleep with my best friend's girlfriend. That doesn't mean that a) I should do it, or b) it won't affect my friend.

      --
      -30-
    18. Re:zdnet.co.uk by jericho4.0 · · Score: 2, Funny

      Idiot. Telneting into a service and typing 'help' is not 'h4x0r1ng', no matter how difficult the telnet manpage looks.

      --
      "A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
  4. Git? by Phidoux · · Score: 5, Funny

    I thought that's what Southerners say to their dawgs?

  5. git 'er done! by qwertphobia · · Score: 4, Funny

    git 'er done!

    --
    Never ask for directions from a two-headed tourist! -Big Bird
  6. wow, that has some rough edges alright by iggymanz · · Score: 3, Interesting

    maybe the kernel programmers should take 2 weeks and fix the basic flaws of git, like the business of not storing deltas to files

    1. Re:wow, that has some rough edges alright by PeterBrett · · Score: 3, Interesting
      ..like the business of not storing deltas to files

      Actually, that's a feature. One of Linus' main objections to existing SCMs was that they're too slow -- and most of that sluggishness comes from the time necessary to calculate and resolve deltas in the ubiquitous RCS files.

      As far as I can tell, it's actually working pretty well so far.

    2. Re:wow, that has some rough edges alright by bilgebag · · Score: 4, Insightful
      ..like the business of not storing deltas to files

      Actually, that's a feature. One of Linus' main objections to existing SCMs was that they're too slow -- and most of that sluggishness comes from the time necessary to calculate and resolve deltas in the ubiquitous RCS files.


      Obviously what needs to be taken into account is that is isn't necessary to do the delta creation at the point of check-in etc, a background process could promote 'clone' type mods into 'delta' type mods at its leisure, maybe even with a delay so only patches unlikely to get reverted are folded down to delta format.

      That way the workload gets distributed as well as the actual development.
    3. Re:wow, that has some rough edges alright by gwait · · Score: 2, Interesting

      Hard drives are cheap,
      deltas are slow
      (doesn't that seem like the roses are red thing?)
      besides, you can bet that git will turn from a quick LT hack into a full blown system within weeks, as a horde of programmers take it apart and put it back together.
      What gits me is - wow, are there really that many patches coming in? Sounds like a disaster waiting to happen :(

      --
      Bavarian Purity Law of Rice Krispie Squares: Rice Krispies, Marshmallows, Butter, Vanilla.
    4. Re:wow, that has some rough edges alright by iabervon · · Score: 2, Informative

      Someone's already written a version that supports deltas. The issue is that the deltas are each the size of the complete file, because in most filesystems a file's size is rounded up to a 4K block. So if you have a 7K source file and you change it, storing the whole thing compressed is 4K, and storing a delta is also 4K, plus you need the old version of the file to apply the delta to.

      Additionally, using deltas means that if you want to combine two commits, you need to create a new representation of the files for the combined change; with full files, you get create a commit that goes from the first tree to the last tree, both of which you're already storing.

      It's counterintuitive, but deltas aren't really efficient in practice.

  7. More tridge news here.... by gowen · · Score: 5, Informative
    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
  8. Tridge tells what he did by Anonymous Coward · · Score: 4, Informative

    I guess this is the logical place to note the newest Groklaw story, Tridge Speaks where Tridge tells his side of the story, or at least a brief overview from his perspective.

  9. Based on Monotone it seems by Carl · · Score: 4, Informative

    The monotone hackers have the same design as this new git tool. They already adapted their visualisation tools to make pretty screenshots of the kernel patches development history: http://lists.gnu.org/archive/html/monotone-devel/2 005-04/msg00183.html

    1. Re:Based on Monotone it seems by the+eric+conspiracy · · Score: 2, Insightful

      Yes, and the Kernel developers looked at monotone as the tool that best suited their development model. However it was way too slow. Hopefully monotone and git will learn from each other and the result will be a better faster open-source distributed SCM.

      I think Larry is going to be unhappy with the end result, because by cutting off the kernel developers he is triggering a lot of work on development of open SCM tools.

    2. Re:Based on Monotone it seems by Bombcar · · Score: 4, Interesting
      Heh. A quote:


      And rsync takes care of the network replication.


      So git, which had to be written because of something Tridge did, uses one of Tridge's programs. Whee!
  10. What GIT Means. by chkorn · · Score: 4, Informative
    Linus definition of GIT:
    "git" can mean anything, depending on your mood. - random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronounciation of "get" may or may not be relevant. - stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang. - "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room. - "goddamn idiotic truckload of sh*t": when it breaks
    --
    chris
  11. Re:Nice Timing! by jdmetz · · Score: 5, Informative

    If you follow the Linux Kernel mailing list at all, it has been fairly apparent for the past week at least that Linus would be using "git" to manage the kernel. He has been putting a lot of time into it. So, my guess is, yes - the editors had "inside" knowledge

  12. Obligatory by mcrbids · · Score: 4, Interesting
    Now, expect a thundering herd of comments like:
    Great! Now, Linus can be helping to build OSS counterparts to commercial software that can be truly trusted, rather than rely on the whims of a commercial vendor.
    and
    This is just another example of where OSS software is MORE RELIABLE than their commercial counterparts.
    The thing is, they'd be right.

    The only thing is to remember: The terms of Linus' use of BK was noncommercial which is poison to a commercial entity. The combination of closed-source + no charge == noncommercial. If it was OSS, with a GPL-like license, at least the OSS community could give something back to BK that wasn't money, but it wasn't, and BK had no opportunity to profit in ANY WAY from this move.

    I'm not surprised this didn't work out well.
    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
    1. Re:Obligatory by wed128 · · Score: 4, Insightful

      yea, but the fact that BitKeeper was used was basically free advertising for the target audience of BK. System Designer #1:
      "Well, after looking it over, we've decided to buy a Bitkeeper liscence. it seems more robust than the competition, plus linus uses it!"

    2. Re:Obligatory by Barsema · · Score: 5, Insightful

      Saying BK did not profit in ANY WAY from providing Linus with Bitkeeper for no charge, is like saying Nike does not profit in ANY WAY from the fact they are giving Tiger Woods golf-gear for no charge.
      In fact I think BK got a bargain and they've gone and thrown it away.

  13. git, by jago25_98 · · Score: 2, Funny

    Linguistic genius!

  14. Re:Newsflash! by Anonymous Coward · · Score: 3, Informative

    GIT is under active development and the fact that exist doesn't mean it will be the "definitive" tool, althought it will probably do. I think it can be considered a "0.1 version". There has not been "official release" of git, they're just testing it

  15. Tridge Speaks by anandpur · · Score: 5, Informative

    From Groklaw

    Groklaw's stevem heard Tridge's speech today at the LCA 2005 conference, Australia's national Linux conference, and he has a report for us:

    This was taken from my memory of Dr. Andrew Tridgell's keynote at this years LCA2005 Conference.
    Essentially Tridge did *NOT* do anything that anyone could ever possibly ever take as breaking a BitKeeper licence, as far as I can see. How was it done? He, like any good sysadmin would, first off telnetted to the BitKeeper port on a BitKeeper server.

    $ telnet thunk.org 5000
    WhooHoo! Connection! So, next obvious step that we *all* do is type in the obvious:

    help
    Back came a list of commands to manipulate the BitKeeper server and ask things of it. Well, according to Tridge, a bit of reading of the LKML (Linux Kernel Email List) shows that the "clone" command is the way to checkout someones source code repository.

    So Tridge's massive "reverse engineering" project came down to a single line of shell script:

    $ echo clone | nc thunk.org 5000 > e2fsprogs.dat
    Hey presto, Tridge has just checked out from a BitKeeper repository into the file e2fsprogs.dat.

    The audience was laughing and cheering Tridge on as he explained just what a Mountain had been made of this Molehill. And I mean made by both sides of the issue -- those who he said he was some Uber Reverse Engineering Wizard and those who claimed that he MUST have used a BK client.

    Funny report, isn't it? Anyway, now you know Tridge's side of the story.

    1. Re:Tridge Speaks by Anonymous Coward · · Score: 2, Interesting

      The problem with your method is that you can't script it. Netcat allows you to pipe input over a socket.

      Netcat is an excellent tool, incidentally. In addition to piping input it's possible to write rudimentary servers with just a shell script. It's well worth taking the 10 minutes or so needed to learn it.

    2. Re:Tridge Speaks by stevey · · Score: 5, Informative

      nc is netcat, and it's a very useful tool. It does way more than telnet.

      I wrote an introduction to netcat if you're interested in exploring it.

    3. Re:Tridge Speaks by jambarama · · Score: 2, Insightful

      When you actually think about it, those who develop the linux kernel are about as sophisticated (computer wise) as you can get. The OSS community has reverse engineered dozens of proprietary formats, locked down much better than that of bitkeeper, for compatibility. BK had to know that:
      1. OSS community doesn't like proprietary formats/software.
      2. The OSS community is very good at reverse engineering formats.

      And ultimately yes, the BK format would be reverse engineered for more freedom. It is like giving a beer to Homer Simpson and expecting him not to drink it.

      That is all.

    4. Re:Tridge Speaks by wct · · Score: 3, Interesting

      He has only claimed to not use the bitkeeper client. There is no EULA governing his use of the publicly facing server. The argument has been that if he used the bitkeeper client to reverse engineer the protocol, he was breaking the terms of using the client. Clearly he wasn't.

      Whether it is an abuse of Bitkeeper's servers to try and interact with them without permission is another debate altogether. Does putting a server on the internet with no access restriction mechanism qualify you for legal protection against access?

  16. The ZDNet article gets it wrong by slavemowgli · · Score: 5, Informative

    There's two major flaws in the ZDNet article, really - outside of the fact that they unfortunately buy into McVoy's lies and FUD, they get two things outright wrong.

    1) BitKeeper's "free" license does not say that you can't use BK to work on a competing product - it says that you cannot work on a competing product AT ALL, no matter whether you use BK for it or not.

    2) It's not true that Tridge hasn't "kept up their end of the bargain". He never used BK at all, so why would he be bound by BK's license? McVoy may not like what Tridge did, but let's face it, reverse engineering for compatibility is perfectly acceptable - even the much-maligned DMCA explicitely allows it, because lawmakers realized that it's important.

    So, McVoy can rant and rave all he wants - the fact remains that HE is the one who did not keep up his end of the "bargain". The bargain was that kernel developers get to use BK for free, and BitMover gets free advertising - now that the company has established itself, it doesn't need that sort of advertising anymore, so they're just looking for a convenient excuse to pull the plug on the "free" BK.

    The fact that McVoy doesn't admit that is probably to be expected, but still, it doesn't change the fact that he spreads just as much FUD and lies as Darl McBride, Laura DiDio, Maureen O'Gara, Steve Balmer and so on.

    I, for one, sure hope he gets what he deserves.

    --
    quidquid latine dictum sit altum videtur.
    1. Re:The ZDNet article gets it wrong by kyb · · Score: 2, Interesting
      Now this confuses me. The BitKeeper "free" license says that you can't use BK to work on a competing product after using BK. Isn't this exactly what Linus has just done?

      Will McVoy ask Linus's employer to sack him? He should at least threaten legal action.

    2. Re:The ZDNet article gets it wrong by pe1rxq · · Score: 4, Insightful

      In most jurisdictions connecting to a server and simply requesting data (e.g. sending a GET to a HTTP server) is perfectly legal regardless what license the http daemon was distributed with.
      Only when you have to circumvent authentification (i.e. pretend to be someone else) it gets nasty.

      If you connected to my system and got some stuff off my webserver it would be perfectly fine. If you used a rootkit to get a shell you would be in trouble.

      Jeroen

      --
      Secure messaging: http://quickmsg.vreeken.net/
    3. Re:The ZDNet article gets it wrong by dheltzel · · Score: 2, Funny
      but . . ., but . . .

      Larry said very clearly that his company is the most open source friendly company in existance. Surely he wouldn't lie about that would he?

      Seriously, I'd have modded you up, but you were already at the max.

    4. Re:The ZDNet article gets it wrong by barawn · · Score: 4, Insightful

      Tridge flat out admits that he telnetted to a live server on the bitkeeper port and interacted with the daemon that monitors that port.

      Where's the agreement that Tridge had to sign to use it? The port's open to the public. After all, the BitKeeper server could've "closed the door". It didn't. It could've required authentication. It could've been encrypted. It wasn't.

      I don't have to sign an agreement to telnet to www.slashdot.org, port 80. If they suddenly put up something on the web that said "You have to sign this license and agree to these terms in order to do this", and I never see that license, how can I be bound by it? Given that there's a thousand ways to prevent unlicensed access, and they did't do any of them, how can it be negligence on my part, and not theirs?

      If that isn't either illegal or in violation of a license, then be a man and post your IP. I'll "reverse engineer" your machine and see what interesting thing I can do.

      If you think that's illegal, you're out of your mind. You don't have to sign a license agreement to "use" a server just because the server exists. He wasn't presented with a license, he didn't agree to a license. The fact that you're trying to claim someone toying around with a random port is 'illegal' or 'in violation of a license' is just ludicrous.

  17. What is bad with copying funcionality?? by xtracto · · Score: 5, Insightful

    from one of TFAs:
    But that's not what Tridge did... He didn't create something new and impressive. He just tore down something new (and impressive) because he could, and rather than helping others, he screwed people over. And you expect me to respect that kind of behaviour?" wrote Torvalds

    Come on!, so what if someone makes a program that implements a cool funcionality from another?? I see it in every game that has been developed in the last 20 years!, thats why whe have genres!, also, that would mean that OpenOffice is bad! or what about the same Linux (Unix clone??) or all the BSD's.

    I think Linus went to far with that, so also to do SAMBA was a "non respectable behaviour" to him? wtf without SAMBA I bet they would be a really, REALLY big amount of people (and companies) not using Linux these days.

    If he does not want to use it, then do not do it, but do not flame the author for doing it, and tell that is not a respectable behaviour! it seems that the most notable figure of Open Source has acquired a Not-So-Open State of Mind.

    my 2C

    --
    Ubuntu is an African word meaning 'I can't configure Debian'
    1. Re:What is bad with copying funcionality?? by argent · · Score: 4, Insightful

      Its a heroic undertaking when OSS does it and its stealing when Microsoft do it.

      I'm sorry, where exactly has Microsoft been accused of stealing when they copied functionality?

      They've been accused of stealing when they've actually used other people's code. They've been accused of embrace-and-extend when they've copied functionality and modified it so the original product they copied no longer interoperates with them. Stealing ideas? Sure, everyone gets accused of that, but nobody in the OSS community with any credibility is going to use that kind of phrase except in jest. And when Microsoft "steals" ideas and they're good ones they often get praised and encouraged for it... all the way back to hierarchical file systems and UNIX style system calls in DOS 2.11...

      So you can keep your "double standard" banner under your hat today, it's not happening.

    2. Re:What is bad with copying funcionality?? by argent · · Score: 2, Interesting

      Uh, how about every time they implement something that Apple implemented first?

      Did you miss "Stealing ideas? Sure, everyone gets accused of that, but nobody in the OSS community with any credibility is going to use that kind of phrase except in jest"?

      The only example that I can think of that might fit your claim is Windows, and the real problem with Windows was not that it was a GUI, or that it could be made to look like the Mac, since both Apple and Microsoft got the idea from Xerox. The problem with Windows (and this doesn't get nearly enough publicity) is that it duplicated the internal structure of Mac OS, even where Mac OS was doing things the wrong way. The original design of Windows, for example, was going to have preemptive multitasking from the get go. It was changed under Bill Gates' urging to use cooperative multitasking. Eller's book documents how Bill Gates acted as a hole in the "chinese wall" between the applications group (who were developing software for the Mac) and the OS group (who weren't contractually allowed to know anything about the Mac), bopping over and telling them to do what turned out to be apallingly stupid things (like said cooperative multitasking) because that's what the Mac did. THAT could be described as theft, because it involved Microsoft violating the NDA they signed when they contracted with Apple to develop applications (like Word) for the Mac.

      It was also a disaster in the long term for Microsoft, if they hadn't done it Windows might have become a viable desktop OS in the '80s instead of having to wait for Windows for Workgroups and Windows 3.11, where they were able to field the first Win32 (Win32s) APIs that let them haul themselves a bit out of the mess they'd made of the 16 bit Windows.

      All your other examples are what's technically known as "irony". It's like "Nobody wanted Multitasking until Microsoft stole it from UNIX"... nobody who says that literally means any illegal activity occurred. It's what we in the industry call humor.

  18. Torvalds was then quoted as saying by dfn5 · · Score: 2, Funny
    "Hey BitKeeper, you Git"

    --
    -- Thou hast strayed far from the path of the Avatar.
  19. Bitkeeper was a great descision by MajorDick · · Score: 3, Insightful

    If it allowed him to work efficently (and it did) for quite some time

    Very simply that time has passed, and NO-ONE other than Linus himself knows what works best for HIM and his direct team

    The flaming is useless hes "The Man" and what he wants for us in Linux land is pretty much Law, besides, how many of YOU psting all these nasty comments about his original BitKeeper descision actually were granted access to it directly, NONE.

    Linus is a pragmatist not a rabid OS advocate but willing to use closed source tools if its a winning situation for him.

    1. Re:Bitkeeper was a great descision by argent · · Score: 2, Insightful

      Linus is a pragmatist not a rabid OS advocate

      *snort*

      Linux is a great guy, who's got both strong technical and strong "people" skills - a rare combination that's made Linux what it is today. But he does get bent out of shape over operating systems awfully easily.

    2. Re:Bitkeeper was a great descision by m50d · · Score: 5, Insightful

      His word is not law, that's the whole point of OSS. We can fork it when he does stupid things. We don't want to waste effort, so we flame him first.

      --
      I am trolling
  20. So is most of the world. by Anonymous Coward · · Score: 4, Insightful

    "Jeremy Allison, who wrote Samba with Andrew 'Tridge' Tridgell, is sticking up for his friend in the row over BitKeeper."

    Yeah, well, so is nearly all the world, except for Linus and Larry McVoy. I'm sorry, Linus' actions are just plain hypocritical here. I can understand how he was pissed at losing a useful tool. I can't understand how he can promote McVoy at the expense of our freedoms, especially to reverse Engineer.

    Mod me down, but Linus has too big of a head on his shoulders. He is NOT indespensible, thanks to the GPL. What does go around, comes around. And this action won't be forgotten. With all due respect to him, I think it's one of his biggest blunders in the history of Linux.

    1. Re:So is most of the world. by ScumericanNazi · · Score: 2, Insightful

      Linus is really really angry cos he was forced to publicly piss on the commercial work (bk) of HIS good friend Larry McVoy and to create an open-source competitor to McVoy's bitkeeper and thereby kick his friend in the face.

      This chain of events was triggered by Tridge's work. That explains the intensity of the venom spat out at Tridge.

      Tridge did nothing wrong cos globally, reverse engineering is completely ethical and legal for interoperability.

      McVoy is a scumbone who has abused everyone involved including his friend Linus, in order to get free publicity for his bitkeeper product.

      Linus is a fool to get manipulated so easily by McVoy. It is Linus' inability to distrust his "friend" that is making him say all these weird things.

      --
      Sig Heil: Scumerica - Land of the Free* (* 18+, valid papers, health insurance, some restrictions apply)
    2. Re:So is most of the world. by slashdot_commentator · · Score: 3, Interesting
      I'm sorry, Linus' actions are just plain hypocritical here. I can understand how he was pissed at losing a useful tool. I can't understand how he can promote McVoy at the expense of our freedoms, especially to reverse Engineer.

      How is Linus being a hypocrite? He does not introduce himself as an official F/OSS spokesman. He never said proprietary software was intolerable that it never should be used in any circumstance.

      I can't understand how he can promote McVoy at the expense of our freedoms, especially to reverse Engineer.

      Because you're a Stalinist Communist. You are too mentally limited to listen to other points of view. Linus never attacked Tridgell's right to reverse-engineer. Torvalds attacked Tridgell's unilateral decision to scuttle the agreement he had with McVoy. I have the right to own a firearm (in the US). It doesn't mean I would be justified to conduct target practice at a shopping mall or woods near a highway. You are so concerned about your rights, you think nothing of abrogating Torvald's right to choose what software he wishes to use. Much like a Communist would.

      He is NOT indespensible, thanks to the GPL.

      Then fork, you loud-mouthed Communist.

      With all due respect to him, I think it's one of his biggest blunders in the history of Linux.

      Nope, I think his biggest blunder was prematurely releasing 2.4 before he had a stable memory manager. I think it really illustrated the amateur nature or limitations of Linux kernel development philosophy. And I'm not thrilled about many minor decisions he has made. But I equate Torvalds to Democracy. And I'll take him before you anytime, Communista.

      --
      There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
  21. Eh? by Aldric · · Score: 5, Interesting
    Although Torvalds is revered by many within the open source community as the founder of Linux, he also has detractors among the free software movement. There is even a conspiracy theory on news site Slashdot that the anti-Torvalds rhetoric may have the underlying aim of persuading the open source community to switch to Hurd -- an alternative to the Linux kernel that is being developed by the Free Software Foundation.

    Did I miss something? I saw some comments to that effect in the stories, mostly as a joke except for the usual random nutcases that see conspiracies in everything that happens. Terrible journalism from zdnet here.

    The rest of the article wasn't any better, being the most heavily biased piece of crap I've read since the last TCO study by Microsoft. Linus and Tridge both have valid points but the article paints Tridge as a villain breaking BitKeeper copyright (which he didn't) and terms of service (which he didn't agree to).

    1. Re:Eh? by Linux_ho · · Score: 5, Informative
      Yeah, my favorite line in the article:
      There is even a conspiracy theory on news site Slashdot that the anti-Torvalds rhetoric may have the underlying aim of persuading the open source community to switch to Hurd -- an alternative to the Linux kernel that is being developed by the Free Software Foundation.
      It was a JOKE. Note the (Score:5, Funny) tag. Just an FYI for all you non-geek journalists reading Slashdot: if you're not laughing, you should interpret (Score:5, Funny) as a clue that some piece of geek humor may have just gone way over your head. Do not take comments on Slashdot seriously, especially if you see (Score:5, Funny). This would be a mistake.

      This has been a public service announcement from the Geek Nation Communication Explanation Foundation.
      --
      include $sig;
      1;
  22. Maybe Linus is tired of the FOSS God mantle by SQUAG · · Score: 2, Funny

    And this is his way of saying fork you.

    --
    Think for yourself.
  23. Re:License anyone? by pe1rxq · · Score: 2, Informative

    Yep, GPL (v2)...

    Its in the file called 'COPYING'.....

    --
    Secure messaging: http://quickmsg.vreeken.net/
  24. Doubled file size!? by Anonymous Coward · · Score: 3, Interesting
    From TFA:
    Among the differences: Git can't rename a file; users must instead delete one and recreate it elsewhere with the new name, McVoy said. And it doesn't handle space efficiently; a tiny one-character change to a 1MB file in Git will result in a 2MB file, whereas BitKeeper's file will grow only by one byte.
    Does anyone know why diff wasn't used here? 1 byte difference (BitKeeper) is excellent, a 100 bytes (diff) is alright, but doubling the file size (Git) seems really insane to the untrained eye..
    1. Re:Doubled file size!? by randomencounter · · Score: 3, Insightful
      Trade space for time is my guess.

      Linus explicitly mentioned that time for commits was a primary consideration, and 'mv' is a lot faster than 'diff'.

      --
      Forget diamonds, copyright is forever.
  25. Up and running! by anpe · · Score: 5, Informative
    Today in the lkml

    Subject:Linux 2.6.12-rc3
    Linus Torvalds
    Wed, 20 Apr 2005 18:00:21 -0700

    Ok,
    you know what the subject line means by now, but this release is a bit
    different from the usual ones, for obvious reasons. It's the first in a
    _long_ time that I've done without using BK, and it's the first one ever
    that has been built up completely with "git".


    Complete message here
  26. Re:Politics is bullshit by argent · · Score: 2, Insightful

    Linus has always been consistent about one thing: you use the best available tool and screw the politics.

    That's why he quit developing his shaky kernel (and the Linux kernel WAS pretty shakey back then) when BSD-Lite was released and jumped on the BSD bandwagon.

    Whoops, wrong universe.

  27. AT&T Press Release by mrwiggly · · Score: 4, Funny


    "Torvalds could have done something constructive: he could have written the best damn OS [Operating System] on the planet, and believed that open source generates better things, and competed against AT&T that way," says a Bell Labs Spokespers in the posting.

  28. Blue Collar Linux Development by dubious9 · · Score: 4, Funny

    I can see it now...

    "There's damn bug som'er in mem.c, can you see if you squish that son'va'bitch?"

    "Public? I made it a private construct. Torvalds threw it in public."

    "If you construct your own low level CMS when the other one runs away,you just might be a redDevneck."

    --
    Why, o why must the sky fall when I've learned to fly?
  29. The Great Rift by rumblin'rabbit · · Score: 2, Insightful
    Your comment only makes sense if you believe proprietary software and private businesses to be "evil".

    I think that attitude marks a great rift between open source (OS) advocates. There are those who support both OS and proprietary software (PS), and those who think all PS is wrong. Judging from their public statements, Linus is in the first camp, and Richard Stallman is in the second.

    Myself, I think free people should be able to to choose whatever approach they want, and good luck to them. And I'm bloody tired of all the fanatics in the world who take a good cause and elevate it to a mindless religion.

    There is no "appeasment" here because there is no enemy.

    It will be interesting to see how it all plays out.

  30. Erm, name change... by Xarius · · Score: 5, Interesting

    There is a package manager, make-based one at that, out there called git. Site in german, package in English.

    It's a good tool, which basically monitors source-built programs and creates an uninstallation script for them.

    Won't this mean Linus' new tool will have to have a name change?

    --
    C17H21NO4
    1. Re:Erm, name change... by Anonymous Coward · · Score: 5, Funny

      I suggest Firebird.

  31. Based on the screenshot of the visualization... by Svartalf · · Score: 4, Interesting

    I'd say that they are. In fact, several SCM tools are looking at what Linus has been doing with git and are giving the stuff due consideration (ARCH is going to pull all the "good" ideas coming from this- I think several other SCM projects are going to do the same...).

    Yeah, I think Larry just stepped in a hornet's nest here- my only complaint about the whole thing is Linus' going on and on about bad ideas, etc. The only bad idea that was going on was his use of BitKeeper in the first place.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    1. Re:Based on the screenshot of the visualization... by Deusy · · Score: 2, Interesting

      I'd go as far as to say that really Linus has been irresponsible here by starting Git.

      Git is a hack to suit his needs, which is fine. But Git is pulling in all this publicity and development time from other people - there is basically a team of developers hacking on this hack of an SCM while more proven and mature solution (years in the making) which are only a little bit of dedication away from being ready to host a project as large as Linux are struggling to accomodate Git rather than focus on their (few) shortcomings.

      A good example is Darcs. When this BK storm came about, the author David Roundy started on an efficiency crusade because the main obstacle to Darcs being an effective SCM for Linux was it's performance. This resulted in a number of improvements (due in the next release) and brought Darcs most of the way to being suitable for hosting the Linux source (it's distributed, easy to use, easy to merge). But now this whole Git thing has pulled everybody in different directions and recent list discussion is focused on how to accomodate Git as the backend storage mechanism for files even though it's really totally unsuited to the Darcs SCM methodology.

      If Linus had said, "Well we're ditching BK as soon as possible. I want to use either Foo or Bar but needs X and Y in them addressing first." This would have brought about the necessary improvements without this Git diversion which may turn out to be permanent to the detriment of general progress.

      He could have gone with Darcs or Monotone or even Arch and brought about their emergence as great distributed SCM tools. Instead he spent days - even weeks - hacking on Git and coordinating things through Git with manual merging. So he's wasted a lot of his own time and the time of others [hacking the hack] for the sake of creating something home grown rather than adopting something that was close to being an adequate replacement for BitKeeper.

      Great men don't always make great choices.

      --

      Free Gamer - Free games list and commentary

  32. Found its directory on Kernel.org's ftp by Newtonian_p · · Score: 2, Informative

    I found this on kernel.org:
    ftp://ftp.kernel.org/pub/software/scm/git/

    It's empty at the moment but we'll probably be seeing the source code appearing in it soon.

    --

    There are 2 kinds of people in this world: Those who write in decimal and those who don't

  33. Re:Please by squiggleslash · · Score: 2, Insightful
    Wouldn't this make it Linus's or McVoy's fault?

    Linus Torvalds chose to use it knowing the bizarre conditions McVoy had stipulated. McVoy stipulated it couldn't be used to develop Free Software alternatives (and, it appears, has extended this stipulation to cover "having a vague connection with someone who develops a Free Software alternative")

    --
    You are not alone. This is not normal. None of this is normal.
  34. Linus reovers his sense of humor by Herschel+Cohen · · Score: 2, Interesting

    Read the last couple of lines on this link: http://www.computerworld.com/softwaretopics/os/lin ux/story/0,10801,101207,00.html
    Indeed, it might be good to read the entire article, much better than I remember Computer World particularly when compared to other articles on this topic seen elsewhere.

    I found this on LXer.com this morning.

  35. Re:Is this for real? by Fizzl · · Score: 3, Insightful
    ...hasn't this thing sort of sprung out of thin air in just a week?
    Yes, now stand aside in awe of a real hacker! ;)
  36. Perhaps it's all about ego by metamatic · · Score: 3, Insightful

    If Linus adopted Arch or Monotone, he would basically be admitting that he could have adopted open source tools in the first place and avoided the whole BitKeeper stupidity. So for ego reasons, he has to build a new tool.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    1. Re:Perhaps it's all about ego by bcd · · Score: 2, Insightful

      Arch and Monotone have progressed a lot since the decision to use BK. That might have been a good decision to avoid them back then. That doesn't mean they shouldn't be considered at all today.

      I really don't see why a brand new tool had to be written for this purpose. I bet any of the OSS tools' development teams would be eager to jump in and work on any of Linus' gripes. I wonder how much time the kernel guys will spend working on git when they could be working on new kernel features/fixing bugs. Starting *completely* over is rarely the right decision in the long run.

      My hope is that git serves useful in the short run to keep the kernel from completely stalling, but that a switch to something more standard happens within the next 6-12 months.

  37. Patents on protocols by tepples · · Score: 2, Interesting

    Communication protocols are methods, not works of authorship. Methods cannot be copyrighted, but they can be patented. What is your evidence otherwise?

  38. The CalvinBall License by dmaxwell · · Score: 4, Insightful

    Nobody except maybe McVoy should have gotten upset over this anyway. It seems to me that at least the free version of Bitkeeper was subject to the CalvinBall License. The problem is that Tridge doesn't seem to play CalvinBall. Something like this happening was inevitable.

  39. Darcs embraces GIT too by sleepingsquirrel · · Score: 4, Informative

    Might as well mention that it looks like Darcs is getting the git religion also.

  40. NAME CLASH !!!!!!! by psergiu · · Score: 4, Informative

    A software package named git - also known as the 'Gnu Interactive Tools' - allready exists.

    http://www.gnu.org/software/git/git.html

    Think at it as a combination on Midnight Commander with emacs keybindings & config. Me and a lot of people use this usefull shell.

    So please change the name of this source versioning package.

    --
    1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
  41. Re:I thought... by brett_sinclair · · Score: 3, Informative
    a (better) frontend must be coded

    A better frontend is already coded. See git-pasky.

    It is early days, of course, but this git should be easy enough to use for anyone who's been using cvs, subversion or the others. You do "git commit", "git commit", "git log", etc. And it's fast. On my poor laptop, "git diff" takes 0.1 second over the entire 235M kernel source.

    This is the frontend to Linus' git stuff, and may be renamed Cogito to prevent confusion.

  42. You missed some of the viewpoints. by khasim · · Score: 5, Insightful

    #1. BitKeeper is McVoy's code and he is allowed to do anything he wants with it. You're right that he could have pulled the "free" client at anytime and held the kernel source as "hostage".

    #2. Linus chose to use BitKeeper knowing all of that. He still chose it because it seemed to be the best product around that would meet his needs. Linus did not seem overly concerned about the potential for losing the "free" client.

    #3. Tridge did not break any laws when he started to reverse engineer the packets.

    So ... no one did anything ILLEGAL and they all made decisions based upon their stated values.

    Where's the problem?

    Well, Tridge should have known that his work would piss off McVoy and that it could result in the loss of the "free" client. Yet he did it anyway WITHOUT writing a SCM that was as good or better than BitKeeper.

    So, the only thing that Tridge is guilty of is not having a replacement ready for when everything blew up.

    McVoy decided that he didn't want to deal with Tridge's work and just pulled the "free" client to stop what he viewed as a threat to BitKeeper.

    So the only thing McVoy is guilty of is attempting to protect his own project.

    Which leaves Linus suddenly without an SCM and he blames Tridge for wreaking a working situation without having a replacement ready.

    So, the only thing Linus is guilty of is venting publicly.

    So why is everyone picking sides? That comes down to each person's values.

    A.) Those who value Open'ness more than functionality support Tridge because they believe Linus was wrong to push a proprietary product.

    B.) Those who value functionality more than Open'ness support Linus because the system was working and it was helping development and there isn't an equivalent system to replace it yet.

    But those are simply judgement calls based upon each individual's value set. Neither is more "right" or "wrong" than the other, except in your opinion.

    1. Re:You missed some of the viewpoints. by drinkypoo · · Score: 2, Insightful

      What about those of us who value Openness AND functionality? I value functionality, so I think tridge should have been able to develop his addon, which does NOT replace or compete with BK (McVoy is primarily guilty of being a whiny baby who wants the world to be different than it really is) to provide that functionality. I also value Openness, so I doubly think that he should have been able to develop his tool.

      Plain and Simple, McVoy claims to be upset that tridge was creating a BK replacement. He was doing nothing of the sort. He was trying to use the existing system, but develop additional functionality. McVoy took his toys and went home; There is no way in hell I would do business with bitmover knowing what I now know about McVoy.

      I will agree that it is not pragmatic to piss off the person giving you software. However, if you need functionality, you develop it.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:You missed some of the viewpoints. by iamwahoo2 · · Score: 2, Insightful

      I see things quite differently. Blame can be assigned and it falls squarely on the shoulders of Torvalds. It was his decision to use BitKeeper and use of a software should not just involve the best tool for the job, but also cost of ownership and risk. Most of the people wanting him to not use bitkeeper were against it because it put so much trust in a company. Linus took the risk of using BitKeeper and got burned. It was his decision and it is his fault. He may be stubborn and not want to own up to having made a mistake (none of us like to do that), but it was a mistake. The fact that McVoy and Tridgell acted like clowns is entirely ancillary.

  43. why not use subversion? by HelloKitty · · Score: 2, Interesting

    Subversion is awsome:

    I started using the Subversion (SVN) source control tool at home instead of CVS (they have convert scripts to convert the old CVS repos)... I use it to store about 2GB of sound and art data as well as source code and configuration files for my system, basically anything I might want to get a previous version.

    My frontend is TortoiseCVS, which is integrated in the explorer windows - which makes for a really easy and intuitive interface.... No more synchronizing two separate windows. Just use explorer, very simple.

    It handles binary files automatically (by autodetection using heuristics on the data and through configurable mime types), and stores binary diffs so your database doesn't get bloaty. In the recent 1.2 version of SVN they've added locking to the databgase in case you're working with others on binary (not-mergable) files.

    For linux there's GUIs as well if any of you do that thing... And there's other options than just Tortoise on Windows...

    They support several database formats including Berkley DB, as well as a filesystem database (similar to what cvs used)...

    Access can be local filesystem, or remote over WebDAV (http) or over SSH (what I'm using, it's secure, encrypted, good!)...

    TortoiseSVN even comes with a graphical merge tool (TortoiseMerge).

    If you're looking for source control, I recommend Subversion. It's free, cross platform, and awesome... I would almost recommend to everyone, but I still have some features I still want to test before going that far... They still need to release 1.2 final (write-locking for binary files), and TortoiseSVN needs to support the locking feature in the 1.2 client...

  44. Greeeat. by gmatyola · · Score: 2, Funny

    Now we'll have other people who make:

    GitTorrent

    Gimp-Git

    Kgit

    Gititude

  45. It's a shame... by [Xorian] · · Score: 3, Interesting

    ...Linus didn't discover Vesta before he started implementing git. The core of the two are very similar.

    • Linus said "git is not an SCM. it's a filesystem designed to host an SCM". The Vesta repository is a filesystem. It has a versioning system (and a builder) built on top of it.
    • git's backing store is indexed by a hash of the file contents, just like Vesta's.
    • git stores complete copies of files, but only one copy of each file, just like Vesta.

    Of course there are some important differences. Like the fact that Vesta's been around for over a decade, and has been in production use for microprocessor design at Compaq and Intel for over 6 years.

    --
    CVS is teh suck. Use Vesta instead.
    1. Re:It's a shame... by [Xorian] · · Score: 2, Informative

      I probably should have included a link to the post I made to the git mailing list with some more details.

      --
      CVS is teh suck. Use Vesta instead.