Source control vs. Revision Control?

by

  • Revision Control is the more generic term, used for source-control tools but also for other tools (Word, OpenOffice, …). It references a version.

  • Source Control offers revision control with branching and merging which are not always available in all revision tools (Word is not a Source Control, but offer revision control features)

  • Version Control is a more general term than Source Control in that it manages version of anything (sources or binaries, or any kind of documents)

Note: SCM stands for Source Code Management, but also for Software Code Management, to reflect the same idea (not just “sources” are managed).
Plus SCM introduces the notion of dependencies between group of files.
And it can also includes the notion of change lifecycle (start a change, close a change, …) which leads to change request system.

More Related Contents:

  1. When should you branch?
  2. How can I use ClearCase to “add to source control …” recursively?
  3. Why is a 3-way merge advantageous over a 2-way merge?
  4. ClearCase advantages/disadvantages [closed]
  5. Should I store generated code in source control
  6. What is the cleverest use of source repository that you have ever seen?
  7. IntelliJ IDEA 9/10, what folders to check into (or not check into) source control?
  8. What’s the best three-way merge tool? [closed]
  9. Storing third-party libraries in source control
  10. Mercurial for Beginners: The Definitive Practical Guide
  11. Named Branches vs Multiple Repositories
  12. Mercurial — revert back to old version and continue from there
  13. Is version control (ie. Subversion) applicable in document tracking? [closed]
  14. Mercurial Subrepos – How do you create them and how do they work?
  15. How to edit incorrect commit message in Mercurial? [duplicate]
  16. Mercurial: How to ignore changes to a tracked file
  17. How do I perform a recursive checkout using ClearCase?
  18. Source Control – Distributed Systems vs. Non Distributed – What’s the difference?
  19. Is there a way to keep Hudson / Jenkins configuration files in source control?
  20. Branching Strategies [closed]
  21. Comparison between Centralized and Distributed Version Control Systems [closed]
  22. Can you “ignore” a file in Perforce?
  23. Mercurial: Merging one file between branches in one repo
  24. What is the difference between hg forget and hg remove?
  25. How often to commit changes to source control? [closed]
  26. Do you continue development in a branch or in the trunk? [closed]
  27. TFS 2017 – how build/deliver only changed files?
  28. How to find untracked files in a Perforce tree? (analogue of svn status)
  29. Code version change “rules” [closed]
  30. What is the difference between all the different types of version control?

Leave a Comment