What Is Version Control and Why Every Developer Needs It
Version control systems like Git track every change to code, enabling collaboration, rollback, and reliable software development.
What has been corrected on this page?
Every accepted correction to this page is recorded with the exact change, so readers can see how the page improved over time.
-
Linux kernel never used CVS; it used patches/tarballs until BitKeeper in 2002 (Git from 2005).
Beforethe dominant tool for open-source development through the 1990s; the Linux kernel used CVS until 2002.
Afterthe dominant tool for open-source development through the 1990s; the Linux kernel was managed with patches and tarballs until it adopted BitKeeper around 2002.
Why: Verified the corrected text is present in the body ('the Linux kernel was managed with patches and tarballs until it adopted BitKeeper around 2002'), consistent with the later Git/BitKeeper narrative in the same article. The FAQ field does not mention this topic, so there was no stale content to fix. No changes needed.
View the full record →
Who checked this page?
1 contributor has checked "What Is Version Control and Why Every Developer Needs It" on When Notes Fly. Each name below links to that person's public CitePep profile, where every contribution they have made is listed with the exact change they proposed.