Slashdot Mirror

← Back to Stories (view on slashdot.org)

Torvalds Unveils New Linux Control System

Posted by Zonk on from the that-was-quick dept.

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. "

3 of 527 comments (clear)

  1. Nice Timing! by MrRTFM · · Score: 0, Redundant

    What do you mean - covered this previously - have you looked at the current poll?
    The timing looks a bit strange - did the editors have inside knowledge, or is the poll guy trying to see if slashdotters can predict the future?

    --
    You can't expect to wield supreme executive power, just because some watery tart threw a sword at you
  2. Well now. by millennial · · Score: 0, Redundant

    It had to be said: Hopefully this helps Linus Git 'er done.

    --
    I am scientifically inaccurate.
  3. Bitkeeper was good because it made Linus productiv by Builder · · Score: 0, Redundant

    I keep hearing how brilliant bitkeeper was because it made Linus more productive. From what I can tell, this could have been done without bitkeeper, but due to stubornness, it tool a technical tool.

    Apoligies in advance if I get some of this wrong, but here is how I understand the issue...

    Linus was the Keeper of the Keys - no code got to the kernel but through him. The problem was that he was dropping patches. So responsibility for various areas of the kernel was delegated out to luitenants, but they actually spelled it correctly ;) These people were supposed to be the filter to make sure code was sane before it got to Linus.

    This is where my timeline gets fuzzy... Either this delegated model happened at the same time as bitkeeper, or a bit earlier. What I do remember though is that Linus was checking every single patch before accepting it to the kernel. He didn't trust his 2ICs enough to just accept their code.

    What bitkeeper did to make Linus more productive could have been done by Linus if he were more trusting. Bitkeeper took away his ability to just pick and choose individual patches, and forced him to accept entire changesets.

    By doing this, bitkeeper forced Linux to trust these other people to have vetted the code. He could now either take the entire changeset or none of it.

    This trust in these additional people stopped him doing the very time consuming job of checking each and every patch before accepting it, leaving him free to do other things.

    So what bitkeeper did to make Linus more productive, Linus could have done without a software tool.