When somebody who is different shows himself to be different in a good way, that's how development happens.

When I do programming in my free time and for my own enjoyment, I really want to have a kind of protection: knowing that when I improve a program those improvements will continue to be available to me and others in future versions of the program.

A lot of people want to have market share numbers, lots of users, because that's how they view their self worth. For me, one of the most important things for Linux is having a big community that is actively testing new kernels; it's the only way to support the absolute insane amount of different hardware we deal with.

I'm a technical manager, but I don't have to take care of people. I only have to worry about technology itself.

The idea of abstracting away the one thing that must be blindingly fast, the kernel, is inherently counter productive.

There's a few historical reasons for why git was considered complicated. One of them is that it was complicated. The people who started using git very early on in order to work on the kernel really had to learn a very rough set of scripts to make everything work. All the effort had been on making the core technology work and very little on making it easy or obvious.

I changed the Linux copyright license to be the GPL some time in the first half of 1992. Mostly because I had hated the lack of a cheaply and easily available UNIX when I had looked for one a year before.