Language Selection

English French German Italian Portuguese Spanish

Interview with Linus about Git

Filed under
Linux

Linus Torvalds didn't want to change software configuration management tools; however, business and open-source philosophy problems left the Linux founder with no choice but to abandon BitKeeper and create his own system: Git.

SCM programs are used to control the flow of updates and track program changes. In a project as large as Linux-more than 17,000 files-this can be very difficult and very slow.

Because most SCMs-such as CVS (Concurrent Versions System)-are too slow for him, Torvalds built his own.

He describes Git as "a stupid (but extremely fast) directory content manager. It doesn't do a whole lot, but what it does do is track directory contents efficiently."

t also can't be used with BitMover Inc.'s BitKeeper, the controversial and proprietary SCM that Torvalds had used to manage Linux kernel development.

"Git has a totally different model of representing the source tree," said Torvalds.

The name itself really doesn't have a meaning. Torvalds joked that it can be a "random three-letter combination that is pronounceable, and not actually used by any common Unix command. The fact that it is a mispronunciation of 'get' may or may not be relevant." Or, "'stupid. contemptible and despicable. simple.' Take your pick from the dictionary of slang." Or, "global information tracker: [if] you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room."

Git has already been used for its first run of Linux: the beta of Linux 2.6.12-rc3. But Torvalds admits that Git is still a work in progress.

"The roughness really comes from two things," said Torvalds. "It's a young project, and it just takes time for things to mature. That will go on for years, assuming none of the other open-source SCMs just eventually show themselves to be capable enough that we just end up deciding that Git was a good temporary bridge."

Also, Git does some things very differently from traditional source management, Torvalds said.

Full Story.

More in Tux Machines

Why the open source community needs a diverse supply chain

Diversity and inclusivity in the technology industry—and in open source communities more specifically—have received a lot of coverage, both on Opensource.com and elsewhere. One approach to the issue foregrounds arguments about concepts that are more abstract—like human decency, for example. But the "supply chain" metaphor works, too. And it can be an effective argument for championing greater inclusivity in our open organizations, especially when people dismiss arguments based on appeals to abstract concepts. Open organizations require inclusivity, which is a necessary input to get the diversity that reduces the risk in our supply chain. Read more

Red Hat: Kerala, Amazon and More

Programming: Swift, Brilliant Jerks in Engineering, and Career Path for Software Developers

  • Swift code will run on Google's Fuchsia OS
    A few days ago, there was a flash-in-the-pan controversy over Google "forking" Apple's open-source programming language Swift. After a few minutes of speculation over whether Google was going to make its own special flavor of the language for its own purposes, Swift's creator Chris Lattner (who now works at Google) helpfully clarified the situation:
  • Brilliant Jerks in Engineering
    This are numerous articles and opinions on the topic, including Brilliant Jerks Cost More Than They Are Worth, and It's Better to Avoid a Toxic Employee than Hire a Superstar. My colleague Justin Becker is also giving a talk at QConSF 2017 on the topic: Am I a Brilliant Jerk?. It may help to clarify that "brilliant jerk" can mean different things to different people. To illustrate, I'll describe two types of brilliant jerks: the selfless and the selfish, and their behavior in detail. I'll then describe the damage caused by these jerks, and ways to deal with them. The following are fictional characters. These are not two actual engineers, but are collections of related traits to help examine this behavior beyond the simple "no asshole rule." These are engineers who by default act like jerks, not engineers who sometimes act that way.
  • [Older] The missing career path for software developers
    You started hacking on technology thrilled with every stroke of the key, making discoveries with every commit. You went about solving problems, finding new challenges. You were happy for a while, until you hit a plateau. There was a choice to be made. Continue solving the same problems or start managing others. You tried it out, and hated it. Longing to focus on technology, not people, you turned to your open source project. When it became successful, you became an open source maintainer but ended up overwhelmed and burned out. Hoping to get back to doing work that fascinates you, you went work for yourself. Lacking experience running a business, you're crushed with all the decisions you need to make. You’re nearing burnout — again. It feels like you’re on a hamster wheel.

Mastodon is Free Software, But It Does Not Respect Free Speech

Mastodon was always known to be tough on Nazis; it was known that they were strict on free speech only to a degree. After the treatment that I received yesterday, however, I can no longer recommend Mastodon. It may be Free software, but it’s very weak on free speech. Read more