References: Why git exists

Primary source

Pro Git by Scott Chacon and Ben Straub. Chapter 1 (About Version Control), specifically sections 1.1 (About Version Control), 1.2 (A Short History of Git), and 1.3 (What is Git?). Licensed under Creative Commons Attribution Non Commercial Share Alike 3.0 Unported.

Read the source online at the Git project’s official site: git-scm.com/book/en/v2/Getting-Started-About-Version-Control. The full book is also available as a free PDF, EPUB, and Mobi.

L1’s snapshot mental model and centralized-vs-distributed framing are informed by Pro Git Chapter 1. L1 is original synthesis, not derivative work, but the conceptual debt is real and worth acknowledging.

Secondary sources

Atlassian Git Tutorials, specifically the “What is Git?” overview. Licensed under Creative Commons Attribution 2.5 Australia. Available at atlassian.com/git/tutorials/what-is-git.

The Atlassian framing of “snapshot, not difference” is consistent with what L1 teaches and is independently useful for any reader who wants a second voice on the same concepts.

Further reading for the curious

For the history of git itself: the Pro Git book covers the 2005 origin story (Linux kernel development, BitKeeper licensing dispute, Linus Torvalds writing the first version in a few weeks) in section 1.2. The history is genuinely interesting and answers questions like “why is it called git” (the name has an irreverent etymology that the founder of git, Linus Torvalds, attributes to multiple sources including a self-deprecating English slang term).

For the technical comparison of version control systems: the Wikipedia article “Comparison of version-control software” lists every major version control system in current and historical use and compares their features. Useful for understanding why specific older systems were used in specific industries.

For a deeper look at distributed version control specifically: the Mercurial project (a contemporary of git) has good documentation on the design choices behind distributed version control, including some that differ from git’s choices. Reading Mercurial documentation alongside git documentation can sharpen understanding of what is essential about distributed version control versus what is git-specific.

What this lesson does not cite

L1 deliberately does not cite GitHub, GitLab, Bitbucket, or any specific hosting platform’s documentation. Those platforms are introduced in L6. L1 is about the underlying version control system, not the hosting layer.

License of this lesson

This lesson is part of the Clawdemy curriculum, licensed under Creative Commons Attribution NonCommercial Share Alike 4.0 International. Pro Git’s CC BY-NC-SA 3.0 license and Clawdemy’s CC BY-NC-SA 4.0 license are directly aligned (the 4.0 license is an approved compatible adaptation license for 3.0 source material per the 3.0 license’s later-versions provision). Commercial use is licensed separately at /legal/licensing.