Git: Torvalds writes the Linux kernel's own version control after losing BitKeeper

In 2002 the Linux kernel — thousands of contributors and thousands of parallel streams of change — had adopted the proprietary BitKeeper for version control. In 2005 the relationship between the kernel community and BitKeeper's maker broke down, the tool's free-of-charge status was revoked, and the world's largest collaborative software project was left without its core work tool.

A distributed VCS built for speed and thousands of parallel branches — every clone is a complete repository, designed like the kernel's own data structures.

Torvalds wrote the first version himself: the initial commit landed on April 7, 2005, with the message 'Initial revision of "git", the information manager from hell' — a handful of C files exposing seven commands. The design goals, drawn from BitKeeper's lessons, were speed, simple design, strong support for non-linear development, and full distribution. On July 26, 2005 he handed maintenance to Junio Hamano, and Git 1.0 shipped on December 21, 2005.

Git became the version control system most developers use: by 2022, nearly 95% of developers reported it as their primary VCS, and the major software forges — GitHub, GitLab, Bitbucket — are built around it. An internal tool written for one project's workflow became the substrate of collaborative software development worldwide.

The Linux kernel is developed by thousands of contributors making thousands of parallel changes, which makes version control unusually hard. In 2002 the project adopted BitKeeper, a proprietary distributed system whose maker allowed free use. In 2005 that relationship broke down and the free-of-charge status was revoked, and the kernel community — Linus Torvalds above all — had to replace the tool that held all its work.

Torvalds' answer was to write the replacement himself. The first commit, on April 7, 2005, announces itself with a wink: 'Initial revision of "git", the information manager from hell.' It was a small set of C files exposing seven low-level commands, built around the same ideas as the kernel: speed first, simple design, cheap branching for non-linear development, and full distribution so every copy of the repository carries the complete history.

It stopped being a private tool quickly. Junio Hamano joined within weeks and took over maintenance on July 26, 2005 — Torvalds had never intended to tend it forever — and Git 1.0 shipped on December 21, 2005. From there it escaped the kernel entirely: by 2022 nearly 95% of developers reported Git as their primary version control system, and the forges that organize modern open source, GitHub and GitLab among them, are Git services at their core.

It treated version control as a performance problem: speed was goal number one, because a tool people wait on is a tool people route around.

Full distribution meant every developer carried the whole history — no single point of failure and no permission gate between an idea and a local experiment.

Branching was a first-class operation rather than an expensive side effect, so parallel lines of work became the cheap, normal way to try things.

It was built against the hardest real workload available — the kernel's scale — instead of a market average, which is exactly why it generalized so well.

Losing a tool you depend on can be a gift. Torvalds built for his own hardest case — huge history, thousands of parallel branches — and a design that fits the hardest case tends to fit everyone's.

Junio Hamano has been Git's maintainer since that July 2005 handover, with Torvalds still contributing. Twenty years on, GitLab's 2025 retrospective on the first commit calls the 'information manager from hell' line what it is — the founding joke of an infrastructure layer nearly all software now runs through. BitKeeper itself was open-sourced in 2016 and is a footnote; Git is the default. The kernel project's crisis response turned out to be, by adoption, the most successful internal tool ever built.