Where Git came from
Git is a little over twenty years old. It was built quickly, for one very demanding project, and its design still reflects that. Here’s the short version — kept honest, with no invented quotes or dates.
Early 2005
The BitKeeper fallout
Since 2002 the Linux kernel had been developed with BitKeeper, a proprietary distributed VCS offered to the kernel community under a free-of-charge licence. In April 2005 that arrangement broke down and the free licence was withdrawn, leaving the kernel — thousands of contributors, a huge history — with no tool that fit how it worked.
April 2005
Linus builds Git
Linus Torvalds stepped back from kernel work for a couple of weeks to write a replacement himself. Development started on 3 April 2005; within a few days Git was managing its own source code, and the first tagged commits land on 7 April 2005. The goals were explicit: speed, a simple and verifiable design, strong support for non-linear development across thousands of parallel branches, fully distributed operation, and the ability to handle a project the size of the kernel efficiently.
April 2005
About the name
Torvalds has said he tends to name projects after himself, and described 'git' — British slang for an unpleasant person — as a self-deprecating joke in the same vein as 'Linux'. Git's own documentation leans into it with a list of tongue-in-cheek expansions ('global information tracker' on a good day, less flattering ones otherwise). Any tidy backronym you see is applied after the fact.
July 2005
Junio Hamano takes over maintenance
Having proved the design, Torvalds handed day-to-day maintenance to Junio Hamano, who had quickly become the most prolific early contributor. Hamano became the project's maintainer on 26 July 2005 and shepherded the 1.0 release.
December 2005
Git 1.0
Git 1.0 was released on 21 December 2005 — roughly eight months after the first commit. The kernel had already moved its own development onto Git earlier that year.
2008
GitHub, and the network effect
GitHub launched in 2008 and made hosting and collaborating on Git repositories easy for everyone, not just kernel-scale projects. Combined with Git's speed and cheap branching, adoption accelerated sharply across open source and industry; other hosts (GitLab, Bitbucket, Gitea, and others) followed.
2020 onward
The SHA-256 transition
Git's object names were originally SHA-1 hashes. Work to support SHA-256 repositories has been in progress for years and is available experimentally; interoperability between SHA-1 and SHA-256 histories is still being finished. Most repositories in the wild remain SHA-1 for now.
Today
A community project
Git is not a single-company product. It is developed in the open by a large contributor base, coordinated on a public mailing list, with Junio Hamano continuing as the long-standing maintainer of the canonical git.git repository. Releases come out on a regular cadence — the badge elsewhere on this site tracks the current stable one.
Check the ground truth
This page is a summary written from public sources and current as of its last edit. Maintainer and contributor details change over time — for anything authoritative, go to the project itself:
Source for this project: github.com/tejastn10/git-grove