kb/basics
Git basics and version control: what version control is, how a distributed VCS differs from a centralized one, what a repository holds, and how Git works with snapshots instead of deltas. This is the foundation. Without it the other sections will not make sense.
A VCS where every developer holds a full copy of the history, not just a snapshot. Git, Mercurial, Bazaar. The key difference from centralized systems (SVN, CVS): no single point of failure, and no network required for most operations.
The core conceptual difference between Git and SVN/CVS/Perforce. Older VCS store each version as a diff from the previous one. Git stores each version as a complete snapshot of the project, with deduplication of identical files via SHA.
A tool that stores the history of file changes, lets you return to past versions, and lets multiple people collaborate on the same project. Three generations: local, centralized, distributed.
The files and directories of your project on disk: the ones you open in your editor. One of Git's three zones, alongside the index ([[add]]) and the repository ([[commit]]).