THE LIVING ARCHIVE

From punched cards to autonomous collaborators: the ideas, people, languages and systems that taught machines to follow—and increasingly interpret—human intent.

PAST / PRESENT / NEXT

Collection

Tag: cvs

Subversion and the Attempt to Fix CVS Without Abandoning Centralized Version Control

Subversion began in 2000 as a deliberately conservative replacement for CVS, preserving centralized version-control workflows while adding atomic commits, versioned directories and a cleaner repository model.

↗

From SCCS to RCS and CVS: How Version Control Became Collaborative

Before Git, version control evolved through systems that learned to preserve file history, identify changes, lock revisions and eventually let multiple developers edit the same code concurrently.

↗