View source for Comparison of version-control software

<!-- Please do not remove or change this AfD message until the discussion has been closed. -->
{{Article for deletion/dated|page=Comparison of version-control software|timestamp=20260201202623|year=2026|month=February|day=1|substed=yes}}
<!-- Once discussion is closed, please place on talk page: {{Old AfD multi|page=Comparison of version-control software|date=1 February 2026|result='''keep'''}} -->
<!-- End of AfD message, feel free to edit beyond this point -->
{{Short description|None}}
{{Dynamic list}}
{{cleanup|reason=Some of these projects may no longer be in active development and should be marked as inactive.|date=April 2014}}

The following tables describe attributes of notable [[version control]] and [[software configuration management]] (SCM) [[software system|systems]] that can be used to compare and contrast the various systems.

For SCM software not suitable for [[source code]], see [[Comparison of open-source configuration management software]].

== General information ==
<!--Entries in these lists should be "notable" with a sourced stand-alone article (see also WP:CSC and WP:GNG).-->
The following table contains relatively general attributes of version-control software systems, including: 
*Repository model, the relationship between copies of the [[source code repository]]
**[[Client–server model|Client–server]], users access a master repository via a [[Client (computing)|client]]; typically, their local machines hold only a working copy of a project tree. Changes in one working copy must be committed to the master repository before they are propagated to other users. 
**[[Distributed version control|Distributed]], repositories act as peers, and users typically have a local repository with version history available, in addition to their working copies.
*Concurrency model, how changes to the working copy are managed to prevent simultaneous edits from causing nonsensical data in the repository. 
**''Lock'', changes are disallowed until the user requests and receives an [[readers–writer lock|exclusive lock]] on the file from the master repository. 
**''Merge'', users may freely edit files, but are informed of possible conflicts upon checking their changes into the repository, whereupon the version control system may [[merge (version control)|merge changes]] on both sides, or let the user decide when [[edit conflict|conflicts]] arise. Distributed version control systems usually use a merge concurrency model.

{| class="wikitable sortable" style="text-align: center; width: auto;"
|-
! Software
! Maintainer
! Development status
! Repository model
! Concurrency model
! [[Software license|License]]
! Supported platforms
! Financial cost
|-
! {{Rh}} | [[AccuRev SCM]]
| [[Micro Focus]]
| Discontinued, merged with [[Dimensions CM]]
| [[Client–server]]
| Merge or lock
| {{proprietary}}
| Most [[Java (programming language)|Java]] Platforms ([[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]])
| {{nonfree | $350 per seat, quoted on an individual basis. | align=left}} 
|-
! {{Rh}} | [[Azure DevOps Server|Azure DevOps]]
| [[Microsoft]]
| {{active}}
| [[Client–server]], [[Distributed revision control|Distributed]] 
| Merge or lock
| {{proprietary}}
| [[Microsoft Windows|Windows]], cross-platform via [[Visual Studio Team Services|Azure DevOps Services]]
| {{Partial | Free for up to 5 users in the Azure DevOps Services or for open source projects; else at cost, licensed through [[Microsoft_Developer_Network|MSDN]] subscription or direct buy. | align=left}}
|-
! {{Rh}} | [[GNU Bazaar]]
| [[Canonical (company)|Canonical]]
| Unmaintained, forked as [[Breezy (software)|Breezy]]
| [[Distributed version control|Distributed]] and [[Client–server]]
| Merge
| {{open source|[[GNU General Public License|GPL-2.0-or-later]]}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
|{{Free|Free}}
|-
! {{Rh}} | [[BitKeeper]]
| BitMover Inc.
| Unmaintained
| [[Distributed version control|Distributed]]
| Merge
| {{open source|[[Apache License|Apache-2.0]]}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{Free|Free}}
|-
! {{Rh}} | [[IBM DevOps Code ClearCase]]
| [[IBM]]
| {{active}}
| [[Client–server]]
| Merge or lock<ref group="nb">In ClearCase, a trigger may be set to allow for the lock model, and this is done at many sites. However, ClearCase development usually takes place on private branches where each developer is given their own branch, so the lock vs. merge concurrency model doesn't matter as much. Code is merged back to the main branch once the developer is ready to deliver their code to the project.</ref>
| {{proprietary}}
| [[Linux]], [[Microsoft Windows|Windows]], [[AIX]], [[Solaris (operating system)|Solaris]], [[HP UX]], [[IBM i]], [[OS/390]], [[z/OS]],
| {{nonfree | $4600 per floating license (held automatically for 30 minutes minimum per user, can be surrendered manually) | align=left}}
|-
! {{Rh}} | [[Code Co-op]]
| Reliable Software
| Discontinued
| [[Distributed version control|Distributed]]
| Merge
| {{open source|[[MIT License|MIT]]}}
| [[Microsoft Windows|Windows]]
| {{nonfree | $150 per seat | align=left}} 
|-
! {{Rh}} | [[Concurrent Versions System]]
| The CVS Team<ref>{{citation |title=Non-GNU Savannah |chapter-url=http://savannah.nongnu.org/project/memberlist.php?detailed=1&group=cvs |chapter=CVS team member list |publisher=The GNU Project}}</ref>
| Unmaintained
| [[Client–server]]
| Merge
| {{open source|[[GNU General Public License|GPL-1.0-or-later]]}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{Free|Free}}
|-
! {{Rh}} | [[CVSNT]]
| March Hare Software<ref>{{citation |url=http://march-hare.com/cvspro/ |publisher=March Hare |title=CVS Pro}}</ref> and community members
| Unmaintained
| [[Client–server]]
| Merge or lock
| {{partial|[[GNU General Public License|GPL]] or proprietary}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]], [[IBM i]]
<!-- | {{partial| £ 425 distribution fee for older version or £85 commercial license for latest version of CVS Suite or Change Management Server | align=left}} -->
|{{nonfree| £425 distribution fee for older version or £85 commercial license for latest version of CVS Suite or Change Management Server | align=left}}
|-
! {{Rh}} | [[darcs]]
| The Darcs team
| {{active}}
| [[Distributed version control|Distributed]]
| Merge
| {{open source|[[GNU General Public License|GPL-2.0-or-later]]}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{Free|Free}}
|-
! {{Rh}} | [[Dat (software)|Dat]]
| The Dat team
| Unmaintained
| [[Distributed version control|Distributed]]
| Merge
| {{open source|[[BSD licenses|BSD-3-Clause]]}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{Free|Free}}
|-
! {{Rh}} | [[Dimensions CM]]
| [[OpenText]]
| {{active}}
| [[Client–server]]
| Merge or lock
| {{proprietary}}
| [[Microsoft Windows|Windows]], [[Linux]], [[Solaris (operating system)|Solaris]], [[AIX]], [[HP UX]], [[z/OS]]
| {{nonfree|Paid}}
|-
! {{Rh}} | [[Diversion (version control)|Diversion]]
| [[Diversion Company, Inc.]]
| {{active}}
| [[Client–server]]
| Merge or lock
| {{proprietary}}
| [[Microsoft Windows|Windows]], [[Linux]], [[macOS]]
| {{nonfree|Starting from $25/month subscription per seat; free for some uses<ref>{{cite web|url=https://www.diversion.dev/pricing |title=Pricing &#124; Diversion Version Control |website=diversion.dev |access-date=2025-12-27}}</ref>| align=left}}
|-
! {{Rh}} | [[Fossil (software)|Fossil]]
| [[D. Richard Hipp]]
| {{active}}
| [[Distributed revision control|Distributed]]
| Merge
| {{open source|[[BSD licenses|BSD-2-Clause]]}}
| [[POSIX]], [[Microsoft Windows|Windows]], [[macOS]], Other
| {{Free|Free}}
|-
! {{Rh}} | [[Git (software)|Git]]
| [[Junio Hamano]]
| {{active}}
| [[Distributed revision control|Distributed]]
| Merge
| {{open source|[[GNU General Public License|GPL-2.0-only]]}}
| [[POSIX]], [[Microsoft Windows|Windows]], [[macOS]]
| {{free|Free}}
|-
! {{Rh}} | [[GNU arch]]
| Andy Tai
| Unmaintained
| [[Distributed revision control|Distributed]]
| Merge
| {{open source|[[GNU General Public License|GPL]]}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{free|Free}}
|-
! {{Rh}} | [[IC Manage]]
| IC Manage Inc.
| {{active}}
| [[Client–server]]
| Merge or lock
| {{proprietary}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{nonfree|Paid}}
|-
| {{Rh}} | [[PTC Integrity]]
| PTC
| Discontinued
| [[Client–server]]
| Merge or lock
| {{proprietary}}
| [[Unix-like]], [[Microsoft Windows|Windows]]
| {{nonfree|Paid}}
|-
! {{Rh}} | [[Mercurial]]
| [https://www.mercurial-scm.org/ Mercurial Community]
| {{active}}
| [[Distributed revision control|Distributed]]
| Merge
| {{open source|[[GNU General Public License|GPL-2.0-or-later]]}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{Free|Free}}
|-
! {{Rh}} | [[Microsoft Visual SourceSafe]]
| [[Microsoft]]
| Discontinued
| Shared Folder
| Merge or lock
| {{proprietary}}
| [[Microsoft Windows|Windows]]
| {{nonfree | $500 per license approximately, or single license included with each [[Microsoft_Developer_Network|MSDN]] subscription. | align=left}}
|-
! {{Rh}} | [[Monotone (software)|Monotone]]
| Nathaniel Smith, Graydon Hoare
| Unmaintained
| [[Distributed revision control|Distributed]]
| Merge
| {{open source|[[GNU General Public License|GPL-2.0-or-later]]}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{Free|Free}}
|-
! {{Rh}} | [[Perforce#P4|Perforce P4]]
| [[Perforce]]
| {{active}}
| [[Client–server]] and [[Distributed version control|Distributed]] 
| Merge or lock
| {{proprietary}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{nonfree|Available as perpetual license and subscriptions; prices vary based on configurations and options<ref>{{cite web|url=https://www.perforce.com/how-buy |title=How To Buy |website=perforce.com |access-date=2018-01-18}}</ref> | align=left}}
|-
! {{Rh}} | [[PVCS]]
| [[OpenText]]
| Discontinued, merged with [[Dimensions CM]]
| [[Client–server]]
| Lock
| {{proprietary}}
| [[Microsoft Windows|Windows]], [[Unix-like]]
| {{nonfree|Paid}}
|-
! {{Rh}} |[[IBM Rational Team Concert]]
| [[IBM]]
| Discontinued
| [[Client–server]]<ref group="nb">RTC is not a distributed revision control system; but has some distributed feature that can be configured</ref><ref>{{cite web |title=What is a distributed version control system |url=https://about.gitlab.com/topics/version-control/benefits-distributed-version-control-system/ |publisher=GitLab}}</ref><ref>{{citation |url=http://jazz.net/blog/index.php/2010/11/05/countdown-to-the-next-rational-team-concert-part-ii-source-control-enhancements |publisher=Jazz Community |author=Jean-Michel Lemieux |title=Countdown to the next Rational Team Concert: Part II – Source control enhancements |access-date=2010-12-28 | archive-date=2015-09-10 | archive-url=https://web.archive.org/web/20150910141242/https://jazz.net/blog/index.php/2010/11/05/countdown-to-the-next-rational-team-concert-part-ii-source-control-enhancements/ |url-status=dead}}</ref>
| Merge or lock
| {{proprietary}}
| [[Linux]], [[Microsoft Windows|Windows]], [[AIX]], [[Solaris (operating system)|Solaris]], [[HP UX]], [[IBM i]], [[OS/390]], [[z/OS]], [[macOS]]
| {{Partial|Free for up to 10 users, else paid | align=left}}
|-
! {{Rh}} | [[Rational Synergy]]
| [[IBM]]
| {{active}}
| [[Client–server]] and [[Distributed revision control|Distributed]]
| Merge or lock
| {{proprietary}}
| [[Linux]], [[Microsoft Windows|Windows]], [[Unix-like]]
| {{nonfree|Paid<ref>{{citation |url=http://www.ibm.com/software/awdtools/synergy |publisher=IBM |title=Rational Synergy| date=9 November 2020}}</ref>}}
|-
! {{Rh}} | [[Revision Control System]]
| Thien-Thi Nguyen
| Unmaintained
| Local
| Merge or lock
| {{open source|[[GNU General Public License|GPL-3.0-or-later]]}}
| [[Unix-like]]
| {{Free|Free}} 
|-
!{{Rh}} | [[Source Code Control System]]
| [[Source Code Control System#Jörg Schilling's fork|Jörg Schilling]]<ref group="nb">Various forks of the original Unix sources exist, only one of which is actively maintained</ref>
| Unmaintained
| Local
| Lock<ref group="nb">While it is possible for multiple users to edit the same version of a file concurrently, only one of them can write back the changes.</ref>
| {{partial|[[CDDL]] – proprietary<ref group="nb">While some forks of SCCS are free software, others remain closed as parts of commercial Unix distributions.</ref>}}
| [[Unix-like]], [[macOS]]
| {{partial|Free [[CDDL]]-licensed versions or paid in some UNIX distributions. | align=left}}
|-
! {{Rh}} | [[StarTeam]]
| [[Borland]] ([[Micro Focus International|Micro Focus]])
| Discontinued
| [[Client–server]]
| Merge or lock
| {{proprietary}}
| [[Microsoft Windows|Windows]] and Cross-platform via Java based client
| {{nonfree|Paid}}
|-
! {{Rh}} | [[Apache Subversion|Subversion]]
| Apache Software Foundation<ref>{{citation |title=Apache Software Foundation |url=http://www.apache.org/}}</ref>
| maintained
| [[Client–server]]
| Merge or lock<ref group="nb">In Subversion, a file attribute enables the lock model on per-file basis. This file attribute can be set automatically using file name wildcard expressions.</ref>
| {{open source|[[Apache License|Apache-2.0]]}}
| [[Unix-like]], [[Microsoft Windows|Windows]], [[macOS]]
| {{free|Free}}
|-
! {{Rh}} | [[Surround SCM]]
| [[Perforce]]
| Unmaintained
| [[Client–server]]
| Merge or lock
| {{proprietary}}
| [[Linux]], [[Microsoft Windows|Windows]], [[macOS]]
| {{nonfree | $595 per user; $29/month subscription | align=left}}
|-
! {{Rh}} | [[Unity Version Control]]
| [[Unity Technologies]]
| {{active}}
| [[Client–server]] and [[Distributed control system|Distributed]]
| Merge or lock
| {{proprietary}}
| [[Linux]], [[Microsoft Windows|Windows]], [[macOS]]
| {{Partial|Free for up to 3 users, else starting at $7 per user per month for server-hosted, or $23 per user per month for on-premises edition. No perpetual licenses.<ref>{{citation |publisher=PlasticSCM |url=https://www.plasticscm.com/pricing |title=Licesing and pricing}}</ref> | align=left}}
|-
! {{Rh}} | [[Vault (version control system)|Vault]]
| SourceGear LLC
| {{active}}
| [[Client–server]]
| Merge or lock
| {{proprietary}}
| [[Unix-like]], [[Linux]], [[Microsoft Windows|Windows]]
| {{nonfree | $300 per user | align=left}} 
|-
! {{Rh}} | [[Vesta (software configuration management)|Vesta]]
| [[Compaq]]
| Discontinued
| [[Distributed revision control|Distributed]] NFS-protocol-emulation choice to optionally confederate [[Client–server|clients]] and/or [[Client–server|servers]]
| Lock on branch; merge branch-to-branch
| {{open source|[[GNU Lesser General Public License|LGPL]]}}
| [[Tru64]], [[Linux]]
| {{free|Free}}
|-
|- class="sortbottom"
! Software
! Maintainer
! Development status
! Repository model
! Concurrency model
! [[Software license|License]]
! Supported platforms
! Financial cost
|}

== Technical information ==

The following table shows technical details of some well-known version-control software. These are classified based on the following headers:

'''Table explanation'''
* '''''Software''''': The name of the application that is described.
* '''''Programming language''''': The coding language in which the application is being developed
* '''''Storage Method''''': Describes the form in which files are stored in the repository. A ''snapshot'' indicates that a committed file(s) is stored in its entirety—usually compressed.  A ''[[changeset]]'', in this context, indicates that a committed file(s) is stored in the form of a difference between either the previous version or the next.
* '''''Scope of change''''': Describes whether changes are recorded for individual ''files'' or for entire directory ''trees''.
* ''<span id="Revision IDs">'''Revision IDs'''</span>'': are used internally to identify specific versions of files in the repository. Systems may use ''[[pseudorandomness|pseudorandom]]'' identifiers, content hashes of revisions, or filenames with sequential version numbers (''namespace'').  With Integrated Difference, revisions are based on the Changesets themselves, which can describe changes to more than one file.
* '''''Network protocols''''': lists the [[protocol (computing)|protocols]] used for [[data synchronization|synchronization of changes]].
* '''''Source code size''''': Gives the size of the source code in megabytes.

{| class="wikitable sortable" style="text-align: center; width: auto;"
|-
! Software
! [[Programming language]]
! Storage method
! Scope of change
! [[#Revision IDs|Revision IDs]]
! [[Protocol (computing)|Network protocols]]
! data-sort-type="number" | Source code size
|-
! {{Rh}} | [[AccuRev SCM]]
| [[C++]], [[Java (programming language)|Java]]
| Changeset
| File
| Number pair NN/NN
| custom
| {{Unk}}
|-
! {{Rh}} | [[Team Foundation Server|Azure DevOps]]
| [[C++]] and [[C Sharp (programming language)|C#]]
| Changeset
| File and Tree
| Numbers
| SOAP over HTTP or HTTPS, [[Ssh]]
| {{Unk}}
|-
! {{Rh}} | [[GNU Bazaar]]
| [[Python (programming language)|Python 2]], [[Pyrex (programming language)|Pyrex (optional)]], [[C (programming language)|C]]<ref group="nb">Bazaar's critical modules are written in [[Pyrex (programming language)|Pyrex]].  They are automatically translated to pure [[C (programming language)|C]]; except for the [[patience sorting]] module, used in merge resolution, which is written directly in the [[C (programming language)|C]] language.</ref>
| Snapshot
| Tree
| Pseudorandom
| custom, custom over [[Secure Shell|ssh]], custom over [[Hypertext Transfer Protocol|HTTP]], [[Hypertext Transfer Protocol|HTTP]], [[SSH file transfer protocol|SFTP]], [[File Transfer Protocol|FTP]], email bundles,<ref group="nb">A Bazaar bundle is a summary diff, with sufficient extra information to preserve history.</ref> WebDAV (with plugin)
| data-sort-value="4.1" | 4.1 MB
|-
! {{Rh}} | [[BitKeeper]]
| [[C (programming language)|C]]
| Changeset
| Tree
| Changeset keys, numbers
| custom, [[Hypertext Transfer Protocol|HTTP]], [[Remote Shell|rsh]], [[Secure Shell|ssh]], email
| 99 MB
|-
! {{Rh}} | [[CA Software Change Manager]]
| [[C (programming language)|C]], [[C++]], [[Java (programming language)|Java]], HTML
| Changeset and Snapshot
| File and Tree{{citation needed|date=April 2012}}
| Numbers
| [[Hypertext Transfer Protocol|HTTP]], TCP/IP 
| {{Unk}}
|-
! {{Rh}} | [[Rational ClearCase|IBM DevOps Code ClearCase]]
| [[C (programming language)|C]], [[Java (programming language)|Java]], [[Perl]]
| Changeset
| File and Tree <ref>{{citation |title=IBM – Rational ClearCase – United States| date=9 November 2020| url=http://www-03.ibm.com/software/products/en/clearcase| archive-url=https://web.archive.org/web/20131111164925/http://www-03.ibm.com/software/products/en/clearcase/| url-status=dead| archive-date=November 11, 2013}}</ref>
| Numbers
| custom (CCFS), custom ([[MultiVersion File System|MVFS]] filesystem driver), [[Hypertext Transfer Protocol|HTTP]]
| {{Unk}}
|-
! {{Rh}} | [[Code Co-op]]
| [[C++]]
| Changeset
| {{Unk}}
| User ID-Ordinal
| e-mail ([[Messaging Application Programming Interface|MAPI]], [[SMTP]]/[[POP3]], [[Gmail]]), [[Local area network|LAN]]
| {{Unk}}
|-
! {{Rh}} | [[Concurrent Versions System|CVS]]
| [[C (programming language)|C]]
| Changeset
| File
| Numbers
| pserver, [[Secure Shell|ssh]]
| data-sort-value="10.3" | 10.3 MB
|-
! {{Rh}} | [[CVSNT]]
| [[C++]]
| Changeset
| File and Tree<ref>{{cite web|title=Changesets|url=http://march-hare.com/cvsnt/features/changesets/|publisher=March Hare Software Ltd.|access-date=8 May 2012}}</ref>
| Numbers
| custom over [[Secure Shell|ssh]], sspi, sserver, gserver, pserver
| data-sort-value="55" | 55 MB
|-
! {{Rh}} | [[darcs]]
| [[Haskell]]
| Changeset (Patch)<ref group="nb">Snapshots with binary files. It's discussed to have binary changesets in future (darcs 3)</ref>
| Tree
| n/a
| custom over [[Secure Shell|ssh]], [[Hypertext Transfer Protocol|HTTP]], email
| data-sort-value="1.7" | 1.7 MB
|-
! {{Rh}} | [[Dimensions CM]]
| [[C (programming language)|C]], [[C++]], [[Java (programming language)|Java]], [[C Sharp (programming language)|C#]]
| Snapshot or changeset
| File and Tree
| Numbers
| Custom, [[Hypertext Transfer Protocol|HTTP]]/[[HTTP Secure|HTTPS]]
| {{Unk}}
|-
! {{Rh}} | [[Fossil (software)|Fossil]]
| [[C (programming language)|C]]
| Snapshot or changeset <ref>{{citation |url=http://fossil-scm.org/index.html/doc/trunk/www/tech_overview.wiki |title=Fossil Technical Overview}}</ref>
| Tree
| [[SHA-1]] or [[SHA-3]] hashes <ref>{{citation |url=http://fossil-scm.org/index.html/doc/trunk/www/hashpolicy.wiki |title=Fossil Hash Policy}}</ref>
| [[Hypertext Transfer Protocol|HTTP]]/[[HTTP Secure|HTTPS]], custom over [[Secure Shell|ssh]]
| data-sort-value="7.2" | 7.2 MB<ref group="nb">4 MB of which are sqlite3.c</ref>
|-
! {{Rh}} | [[Git (software)|Git]]
| [[C (programming language)|C]], [[shell script]]s, [[Perl]]
| Snapshot
| Tree
| [[SHA-1]] or [[SHA-256]]<ref>{{cite web | title=Git 2.51 Released with Performance Optimizations and SHA-256 as Default hash Function – Cyber Web Spider Blog – News | date=20 August 2025 | url=https://cyberwebspider.com/blog/cyber-security-news/git-2-51-released-with-performance-optimizations-and-sha-256-as-default-hash-function/ }}</ref> hashes
| custom (''git''), custom over [[Secure Shell|ssh]],<ref>{{citation |url=http://www.samba.org/~jelmer/dulwich/docs/protocol.html |title=Git Server Protocol}}</ref> [[Hypertext Transfer Protocol|HTTP]]/[[HTTP Secure|HTTPS]], [[rsync]], email, bundles
| data-sort-value="23" | 23 MB <ref>{{Cite web|url=https://github.com/git/git|title=Git - fast, scalable, distributed revision control system|website=[[GitHub]]|date=2 November 2021}}</ref>
|-
! {{Rh}} | [[GNU arch]]
| [[C (programming language)|C]], [[shell script]]s
| Changeset
| Tree
| Numbers
| [[Hypertext Transfer Protocol|HTTP]], [[WebDAV]]
| {{Unk}}
|-
! {{Rh}} | [[IC Manage]]
| [[C++]], [[C (programming language)|C]]
| Changeset
| {{Unk}}
| Numbers
| custom
| {{Unk}}
|-
! {{Rh}} | [[Mercurial]]
| [[Python (programming language)|Python]], [[C (programming language)|C]]
| Changeset
| Tree
| Numbers,<ref group="nb">Mercurial revision numbers are local to a repository; they can differ from repository to repository depending on in which order merges are performed.</ref> [[SHA-1]] hashes
| custom over [[Secure Shell|ssh]], [[Hypertext Transfer Protocol|HTTP]], email bundles (with standard plugin)
| data-sort-value="20" | 20 MB
|-
! {{Rh}} | [[MKS Integrity]]
| [[C (programming language)|C]], [[Java (programming language)|Java]]
| Changeset
| File
| Numbers
| custom, [[Hypertext Transfer Protocol|HTTP]]
| {{Unk}}
|-
! {{Rh}} | [[Monotone (software)|Monotone]]
| [[C++]]
| Hybrid<ref group="nb">A Monotone's revisions represent changesets and its manifests represent snapshots, each revision is linked to some manifest. But manifests are legacy constructs, they aren't kept in the database anymore and reconstructed on the fly if needed. The real work now happen in rosters which are hybrid snapshot/changeset structures.</ref>
| Tree
| [[SHA-1]] hashes
| custom (''netsync''), custom over [[Secure Shell|ssh]], file system
| data-sort-value="4.4" | 4.4 MB
|-
! {{Rh}} | [[Perforce Software#Helix Core|Perforce Helix Core]]
| [[C++]], [[C (programming language)|C]]
| Changeset
| Tree
| Numbers
| custom
| {{Unk}}
|-
! {{Rh}} | [[PVCS]]
| [[C++]], [[C (programming language)|C]]
| Changeset
| File
| Numbers
| {{Unk}}
| {{Unk}}
|-
! {{Rh}} | [[IBM Rational Team Concert|Rational Team Concert]]
| [[Java (programming language)|Java]]
| Changeset
| Tree
| Numbers
| [[Representational State Transfer|REST]] services over [[Hypertext Transfer Protocol|HTTP]]/[[HTTP Secure|HTTPS]]
| {{Unk}}
|-
! {{Rh}} | [[Revision Control System]]
| [[C (programming language)|C]]
| Changeset
| File
| Numbers
| File system
| data-sort-value="5.3" | 5.3 MB
|-
! {{Rh}} | [[Source Code Control System]]
| [[C (programming language)|C]]
| Changeset
| File
| Numbers
| [[Network File System|NFS]]
| data-sort-value="1.3" | 1.3 MB
|-
! {{Rh}} | [[StarTeam]]
| [[C++]], [[C (programming language)|C]], [[Java (programming language)|Java]]
| Snapshot
| File and Tree
| [[MD5]] hashes
| custom, TCP/IP
| {{Unk}}
|-
! {{Rh}} | [[Apache Subversion|Subversion]]
| [[C (programming language)|C]]
| Changeset and Snapshot
| Tree
| Numbers
| custom (''svn''), custom over [[Secure Shell|ssh]], [[Hypertext Transfer Protocol|HTTP]] and SSL (using [[WebDAV]])
| data-sort-value="41" | 41 MB
|-
! {{Rh}} | [[Surround SCM]]
| [[C++]]
| Changeset
| File and Tree
| Numbers
| TCP/IP
| {{Unk}}
|-
! {{Rh}} | [[Telelogic Synergy|Synergy]]
| [[Java (programming language)|Java]]
| Changeset (text), Snapshot(binary)
| File
| Numbers
| custom, custom over [[Secure Shell|ssh]], [[Hypertext Transfer Protocol|HTTP]]
| {{Unk}}
|-
! {{Rh}} | [[Vault (revision control system)|Vault]]
| [[C Sharp (programming language)|C#]]
| Changeset
| File and Tree
| Numbers
| [[HTTP]], [[HTTPS]]
| {{Unk}}
|-
! {{Rh}} | [[Vesta (Software configuration management)|Vesta]]
| [[C++]]
| Snapshot
| Tree
| {{Unk}}
| [[Network File System|NFS]]
| data-sort-value="15.8" | 15.8 MB
|-
! {{Rh}} | [[Microsoft Visual SourceSafe|Visual SourceSafe]]
| [[C (programming language)|C]]
| Snapshot
| File
| Numbers
| [[Server Message Block|SMB]], [[Distributed Component Object Model|DCOM]]
| {{Unk}}
|- class="sortbottom"
! Software
! [[Programming language]]
! Storage method
! Scope of change
! Revision IDs
! Network protocols
! Source code size

|}

== Features ==

The following table classifies some well-known software on the basis of its features and capabilities:

'''Table explanation'''
* '''''Software''''': The name of the application that is described.
* '''''Supports Git data format''''': able to natively work on [[Git]]'s repository formats
* ''[[Atomic commit|'''Atomic commits''']]'': refers to a guarantee that all changes are made, or that no change at all will be made.
* '''''File renames''''': describes whether a system allows files to be renamed while retaining their version history.
* '''''Merge file renames''''': describes whether a system can merge changes made to a file on one branch into the same file that has been renamed on another branch (or vice versa). If the same file has been renamed on both branches then there is a rename conflict that the user must resolve.
* ''[[Symbolic link|'''Symbolic links''']]'': describes whether a system allows revision control of symbolic links as with regular files.  Versioning symbolic links is considered by some people a feature and some people a security breach (e.g., a symbolic link to /etc/passwd). Symbolic links are only supported on select platforms, depending on the software.
* '''''Pre-/post-event hooks''''': indicates the capability to trigger commands before or after an action, such as a commit, takes place.
* '''''[[digital signature|Signed]] revisions''''': refers to integrated digital signing of revisions, in a format such as [[OpenPGP]].
* '''''Merge tracking''''': describes whether a system remembers what changes have been merged between which branches and only merges the changes that are missing when merging one branch into another.
* '''''[[End of line]] conversions''''': describes whether a system can adapt the end of line characters for text files such that they match the end of line style for the operating system under which it is used.  The granularity of control varies.  Subversion, for example, can be configured to handle EOLs differently according to the file type, whereas Perforce converts all text files according to a single, per-client setting.
* ''[[revision tag|Tags]]'': indicates if meaningful names can be given to specific revisions, regardless of whether these names are called tags or labels.
* '''''International support''''': indicates if the software has support for multiple language environments and operating system
* '''''Unicode filename support''''': indicates if the software has support for interoperations under [[file system]]s using different [[character encoding]]s.
* '''''Supports large repos''''': Can the system handle repositories of around a gigabyte or larger effectively?

{{sort-under}}
{| class="wikitable sortable sort-under" style="text-align: center; width: auto;"
|-
! Software
!Supports Git data format
! [[Atomic commit]]s
! File renames
! Merge file renames
! [[Symbolic link]]s
! Pre-/post-event hooks
! [[digital signature|Signed]] revisions
! Merge tracking
! [[End of line]] conversions
! [[revision tag|Tags]]
! International support
! Unicode filename support
! Supports large repos
|-
! {{Rh}} | [[AccuRev SCM]]
|
| {{yes}}
| {{yes}}
| {{partial}}<br /><ref group="nb">Evil twins are common.[http://accurev.com/blog/2008/01/24/evil-twins-in-scm-not-hollywood/ Evil Twins in SCM, Not Hollywood] {{webarchive|url=https://web.archive.org/web/20131016074903/http://accurev.com/blog/2008/01/24/evil-twins-in-scm-not-hollywood/ |date=2013-10-16}}</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{N/A}}
| {{yes}}
| {{yes}}<br /><ref>{{cite web |url=http://www.accurev.com/download/docs/5.3.0_books/AccuRev_5_3_0_Install_Release_Notes.pdf |title=Archived copy |access-date=2012-01-12 |url-status=dead |archive-url=https://web.archive.org/web/20111113040629/http://www.accurev.com/download/docs/5.3.0_books/AccuRev_5_3_0_Install_Release_Notes.pdf |archive-date=2011-11-13}}</ref>
| {{yes}}<br /><ref>{{cite web |url=http://www.accurev.com/press-releases/20040426-AccuRev-Kronos.html |title=SCM News – Kronos Turns to AccuRev for Software Configuration Management |publisher=AccuRev |date=2004-04-26 |access-date=2014-01-26 |url-status=dead |archive-url=https://web.archive.org/web/20140202091954/http://www.accurev.com/press-releases/20040426-AccuRev-Kronos.html |archive-date=2014-02-02}}</ref><ref>{{cite web |url=http://www.accurev.com/press-releases/092308-avid-selects-accurev.html |title=Enhanced Performance and Scalability for Cross-Platform Geographically Distributed Teams |publisher=AccuRev |date=2008-09-23 |access-date=2014-01-26 |url-status=dead |archive-url=https://web.archive.org/web/20140202092247/http://www.accurev.com/press-releases/092308-avid-selects-accurev.html |archive-date=2014-02-02}}</ref>
|-
! {{Rh}} | [[Team Foundation Server|Azure DevOps]]
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! {{Rh}} | [[GNU Bazaar]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref>{{cite web |url=http://doc.bazaar-vcs.org/bzr.1.14/en/release-notes/NEWS.html#bzr-1-14 |title=EOL conversions are supported since bzr 1.14 |publisher=Doc.bazaar-vcs.org |access-date=2014-01-26 |archive-date=2009-04-13 |archive-url=https://web.archive.org/web/20090413040914/http://doc.bazaar-vcs.org/bzr.1.14/en/release-notes/NEWS.html#bzr-1-14 |url-status=dead }}</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
|-
! {{Rh}} | [[BitKeeper]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
| {{Unk}}
| {{yes}}
|-
! {{rh}} | [[CA Software Change Manager]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
|-
! {{Rh}} | [[Rational ClearCase|IBM DevOps Code ClearCase]]
|
| {{partial}}<br /><ref group="nb">Atomic commit can be enabled for individual checkin's [https://publib.boulder.ibm.com/infocenter/cchelp/v7r1m0/index.jsp?topic=/com.ibm.rational.clearcase.relnotes.doc/topics/c_cc_relnotes_features.htm ClearCase 7.1.1 release notes].</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref>[http://www.ibm.com/support/docview.wss?uid=swg21229688 Support Policy for National Languages and ClearCase] from IBM Support</ref>
| {{Unk}}
| {{yes}}
|-
! {{Rh}} | [[Code Co-op]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{partial}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{Unk}}
| {{Unk}}
| {{Unk}}
|-
! {{Rh}} | [[Concurrent Versions System|CVS]]
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{no}}
| {{partial}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{Unk}}
| {{no}}
| {{yes}}
|-
! {{Rh}} | [[CVSNT]]
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
|-
! {{Rh}} | [[darcs]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}<br /><ref group="nb">See [http://darcs.net/FAQ#can-darcs-handle-symlinks FAQ]</ref>
| {{yes}}
| {{yes}}
| {{N/A}}<br /><ref group="nb">darcs' patches each bear a unique identifier, impossible to merge twice the same patch in a repository (without destructively modifying history using "unsafe" commands).</ref>
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}<br /><ref group="nb">Although it stores (and shows by default) 8-bit filename. See [http://darcs.net/FAQ#can-i-version-control-files-with-characters-in-the-full-unicode-spectrum FAQ]</ref>
| {{Unk}}
|-
! {{Rh}} | [[Dimensions CM]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{Unk}}
| {{yes}}
| {{yes}}
| {{yes}} <ref group="nb">Using Item Revision Attributes ([http://help.serena.com/doc_center/demos/CM_Essentials_items_1.html "Working with Items" demo, covering user define attributes] {{webarchive|url=https://web.archive.org/web/20160304081203/http://help.serena.com/doc_center/demos/CM_Essentials_items_1.html |date=2016-03-04}}).</ref>
| {{no}} <ref group="nb">In the sense that its messages and graphic interfaces have English only localization, though the software is certified running fine on various language operating systems.</ref>
| {{yes}}
| {{yes}}
|-
! {{Rh}} | [[Fossil (software)|Fossil]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref>{{cite web | title=Fossil: Hooks | url=https://fossil-scm.org/home/doc/tip/www/hooks.md }}</ref>
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref group="nb">Controlled by the 'crnl-glob' setting ([http://fossil-scm.org/index.html/help/setting])</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref>{{cite web | title=Fossil: Fossil Versus Git | url=https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki#scale }}</ref>
|-
! {{Rh}} | [[Git (software)|Git]]
| {{yes}}
| {{yes}}
| {{partial}}<br/>{{Dubious|date=December 2025}}<br /><ref group="nb">Git does not explicitly track renames, because by design it does not track individual files. Renames and split of source files are detected after the fact, if the file content does not change dramatically.</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref group="nb">Since git-1.7.9 (see [http://git.kernel.org/?p=git/git.git;a=blob_plain;f=Documentation/RelNotes/1.7.9.txt;hb=HEAD release notes] {{webarchive|url=https://archive.today/20130415094950/http://git.kernel.org/?p=git/git.git;a=blob_plain;f=Documentation/RelNotes/1.7.9.txt;hb=HEAD |date=2013-04-15}}). Older versions do not sign commits, only tags (see the -s option in [http://www.kernel.org/pub/software/scm/git/docs/git-tag.html git-tag(1) Manual page])</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref group="nb">UTF-8 filenames are supported as of version 1.7.10  ([https://raw.github.com/msysgit/msysgit/f45b8ee0ef75c03c210a476db9184824ffcb33c1/share/WinGit/ReleaseNotes.rtf MSysGit release notes]).</ref>
| {{partial}}<br /><ref group="nb">Git has some issues with very large repositories. See Section ''Better big-file support'' and Section ''Designing a faster index format'' in [https://github.com/peff/git/wiki/SoC-2012-Ideas SoC 2012 Ideas].</ref>{{update inline|date=December 2025}}
|-
! {{Rh}} | [[GNU arch]]
|
| {{yes}}
| {{yes}}
| {{Unk}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
| {{Unk}}
| {{yes}}
| {{Unk}}
| {{Unk}}
| {{Unk}}
|-
! {{Rh}} | [[IC Manage]]
|
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
| {{Unk}}
|-
! {{Rh}} | [[MKS Integrity]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}<br /><ref group="nb">Integrity enabled change packages provide complete workflow and 21 CFR Part 11 compliant digital signatures against the item controlling the change package.</ref>
| {{yes}}<br /><ref group="nb">2009 SP5 added a feature to merge child development paths.</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
|-
! {{Rh}} | [[Mercurial]]
| {{partial}}<br /><ref>{{cite web | title=GitExtension - Mercurial | url=https://wiki.mercurial-scm.org/GitExtension }}</ref><ref>https://foss.heptapod.net/mercurial/mercurial-devel/-/tree/branch/default/hgext/git</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref group="nb">Mercurial includes internationalization for [https://www.mercurial-scm.org/repo/hg/file/3c3066367d72/i18n more than 10 languages] as of 2017.</ref>
| {{partial}}<br /><ref group="nb">Support depends upon host OS and is well supported under Unix, but not Windows OSs, due to lack of host support. See [https://www.mercurial-scm.org/wiki/EncodingStrategy]</ref>
| {{yes}}<br /><ref>With the [https://www.mercurial-scm.org/wiki/LargefilesExtension Largefiles Extension] in core since [https://www.mercurial-scm.org/wiki/WhatsNew/Archive#Mercurial_2.0_.282011-11-01.29 Hg Rev.:2.0 (2011)], the [https://code.facebook.com/posts/218678814984400/scaling-mercurial-at-facebook/ remotefilelog extension (2014)], the [https://www.mercurial-scm.org/wiki/FsMonitorExtension fsmonitor extension] in core since [https://www.mercurial-scm.org/wiki/Release3.8 Hg Rev.:3.8 (2016)] and the experimental sparse extension in core [https://www.mercurial-scm.org/wiki/Release4.3 since Hg Rev.:4.3 (2017)].</ref>
|-
! {{Rh}} | [[Monotone (software)|Monotone]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}<br /><ref group="nb">It could be done via user level hooks</ref>
| {{yes}}
| {{yes}}, mandatory
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
| {{yes}}
| {{Unk}}
|-
! {{Rh}} | [[Perforce Software#Helix Core|Perforce Helix Core]]
|
| {{yes}}
| {{yes}}<br /><ref>[http://www.perforce.com/perforce/doc.current/manuals/p4guide/04_files.html#1060858] {{Webarchive|url=https://web.archive.org/web/20140210122535/http://www.perforce.com/perforce/doc.current/manuals/p4guide/04_files.html#1060858 |date=2014-02-10}} from the [[Perforce]] User's Guide</ref>
| {{yes}}<br /><ref>[http://www.perforce.com/perforce/doc.current/manuals/p4guide/05_resolve.html#1068311] {{Webarchive|url=https://web.archive.org/web/20140209192552/http://www.perforce.com/perforce/doc.current/manuals/p4guide/05_resolve.html#1068311 |date=2014-02-09}} from the [[Perforce]] User's Guide</ref>
| {{partial}}<br /><ref group="nb">Perforce will version-control symbolic links themselves, but will not recognise its own version-controlled views (local file trees), if you access them via symbolic links.</ref>
| {{yes}}
| {{no}}
| {{yes}}<br /><ref>{{cite web |url=http://www.perforce.com/perforce/technotes/note009.html |title=Perforce Public Knowledge Base – Home |publisher=Perforce.com |access-date=2014-01-26 |archive-url=https://web.archive.org/web/20070814143752/http://www.perforce.com/perforce/technotes/note009.html |archive-date=2007-08-14 |url-status=dead}}</ref>
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref>{{cite web |url=http://kb.perforce.com/?article=66 |title=Perforce Knowledge Base: Internationalization and Localization |publisher=Kb.perforce.com |date=2010-10-21 |access-date=2014-01-26 |archive-url=https://web.archive.org/web/20120208133709/http://kb.perforce.com/?article=66 |archive-date=2012-02-08 |url-status=dead}}</ref>
| {{yes}}<br /><ref>{{cite web |url=http://kb.perforce.com/article/66/internationalization-and-localization#i18n |title=Perforce Knowledge Base: Internationalization and Localization |publisher=Kb.perforce.com |date=2010-10-21 |access-date=2014-01-26 |archive-url=https://web.archive.org/web/20130130095324/http://kb.perforce.com/article/66/internationalization-and-localization#i18n |archive-date=2013-01-30 |url-status=dead}}</ref>
| {{yes}}
|-
! {{Rh}} | [[IBM Rational Team Concert|Rational Team Concert]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref group="nb">Through the process behaviour components: Operation advisors and Operation participants. http://jazz.net/library/article/292</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
|-
! {{Rh}} | [[Source Code Control System]]
| {{no}}
| {{yes}}
| {{no}}
| {{N/A}}
| {{N/A}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{partial}}<br /><ref group="nb">While the source code of SCCS has been written to support internationalisation, only English message texts exist.</ref>
| {{yes}}
| {{yes}}
|-
! {{Rh}} | [[StarTeam]]
|
| {{yes}}<br /><ref group="nb">StarTeam supports atomic commits as of version 2006</ref>
| {{yes}}
| {{Unk}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{Unk}}
| {{yes}}
|-
! {{Rh}} | [[Apache Subversion|Subversion]]
| {{no}}
| {{yes}}
| {{yes}}<br /><ref group="nb">Subversion can move a file and conserve its history, if and only if the target of the move is in the same Subversion repository as the source. Cross-repository moves require third-party tools.</ref>
| {{partial}}<br /><ref group="nb">Since SVN 1.8 subversion supports improved move-tracking on the client side. On the server-side it's not supported yet.</ref>
| {{yes}}
| {{yes}}
| {{no}}<br /><ref group="nb">{{cite web|url=http://svn.haxx.se/dev/archive-2015-06/0052.shtml |title=Changeset Signing |publisher=Apache Subversion Mailing Lists |access-date=2016-08-05}}</ref>
| {{yes}}.<ref group="nb">New to SVN 1.5 <http://subversion.apache.org/docs/release-notes/1.5.html#merge-tracking>. A separate tool "svnmerge" <[https://web.archive.org/web/20180520193844/https://cracktower.blogspot.com/]> provides merge tracking for older versions.</ref>
| {{yes}}
| {{partial}}<br /><ref group="nb">In Subversion, tags are a special case of the more generic "cheap copy" concept of Subversion. Per convention, a tag is a copy into a directory named "tags". Because of this, even tags are versioned. See http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html for more information. The reason for partial support in the table is because Subversion's emulation of tags in this manner does not meet the requirement that the tag name can be used in place of any revision identifier wherever the user may be required to enter one. This column would be meaningless if the definition were to be loosened enough to encompass Subversion's approach as every version control system supports branching and would therefore support tags as well.</ref>
| {{yes}}
| {{yes}}
| {{yes}}
|-
! {{Rh}} | [[Surround SCM]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref>[http://www.seapine.com/pr.php?id=147&title=Seapine_Software_Releases_Surround_SCM_2009] – Seapine Software Releases Surround SCM 2009</ref>
| {{yes}}
| {{yes}}
| {{yes}}
|-
! {{Rh}} | [[Telelogic Synergy|Synergy]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}<br /><ref group="nb">in Asian releases (v6.6a to v7.1a) and since version 7.2 in general</ref>
| {{yes}}
|-
! {{Rh}} | [[Vault (revision control system)|Vault]]
|
| {{yes}}
| {{yes}}
| {{yes}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{Unk}}
| {{Unk}}
| {{Unk}}
|-
! {{Rh}} | [[Vesta (Software configuration management)|Vesta]]
|
| {{yes}}
| {{yes}}
| {{unk}}
| {{unk}}
| {{yes}}
| {{no}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{Unk}}
| {{yes}}
|-
! {{Rh}} | [[Microsoft Visual SourceSafe|Visual SourceSafe]]
|
| {{no}}
| {{no}}<br /><ref group="nb">Version change history is removed upon rename; old name not referenced.</ref>
| {{Unk}}
| {{no}}
| {{yes}}
| {{no}}
| {{no}}
| {{Unk}}
| {{yes}}
| {{yes}}
| {{Unk}}
| {{Unk}}
|- class="sortbottom"
! Software
!
! [[Atomic commit]]s
! File renames
! Merge file renames
! [[Symbolic link]]s
! Pre-/post-event hooks
! [[digital signature|Signed]] revisions
! Merge tracking
! [[End of line]] conversions
! [[revision tag|Tags]]
! International support
! Unicode filename support
! Supports large repos

|}

== Advanced features ==

The following are some more advanced features and capabilities available in notable version-control systems:

'''Table explanation'''
* '''''Keyword expansion''''': supports automatic expansion of keywords such as file revision number.
* '''''Interactive commits''''': interactive commits allow the user to cherrypick common lines of code used to anchor files (patch-hunks) that become part of a commit (leaving unselected changes as changes in the working copy), instead of having only a file-level granularity.
* '''''External references''''': embedding of foreign repositories in the source tree
* '''''Partial checkout/clone''''': ability to check out or clone only a specified subdirectory from a repository.
* '''''Permissions''''': tracks file permission bits in the revision history.
* '''''[[Timestamp]] preservation''''': overwrites the ''last modified'' filesystem attribute with the commit time upon checkout.
* '''''Custom automatic merge tool''''': automatic merging can be attempted by any tool of the user's choice (hopefully configurable on a per-file basis)
* '''''Supported formats''''': either read/write support or read-only (conversion, potentially repeated)
* '''''Shared build cache of derived objects''''': the ability to automatically substitute (wink-in) derived-objects that were built by other confederated clients that share exactly the same dependencies instead of rebuilding them locally

{{sort-under}}
{| class="wikitable sortable sort-under" style="text-align: center; width: auto;"
|-
! Software
! Keyword expansion
! Interactive commits
! External references
! {{verth|va=middle|Partial<br/>checkout/clone}}
! Permissions
! Timestamp preservation
! Custom automatic merge tool
! Supported formats
! {{verth|va=middle|Shared build cache<br/>of derived objects}}
|-
! [[AccuRev SCM]]
| {{yes}}
| {{unk}}
| {{yes}}
| {{yes}}
| {{partial|execution bit only}}
| {{yes}}
| {{yes}}
| git (bi-dir)<ref>{{cite web |url=http://www.accurev.com/kando |title=GitCentric &#124; AccuRevGit for the Enterprise |publisher=Accurev.com |access-date=2014-01-26 |url-status=dead |archive-url=https://web.archive.org/web/20121017043025/http://www.accurev.com/kando |archive-date=2012-10-17}}</ref>
| {{no}}
|-
! [[Team Foundation Server|Azure DevOps]]
| {{no}}
| {{yes}}
| {{unknown}}
| {{yes}}
| {{yes}}
| {{unknown}}
| {{yes}}
| {{unknown}}
| {{unknown}}
|-
! [[GNU Bazaar]]
| {{yes|Yes<ref>{{cite web |url=http://wiki.bazaar.canonical.com/KeywordExpansion |title=Bazaar keywords plugin |publisher=Wiki.bazaar.canonical.com |date=2005-09-05 |access-date=2014-01-26 |archive-date=2014-02-01 |archive-url=https://web.archive.org/web/20140201213944/http://wiki.bazaar.canonical.com/KeywordExpansion |url-status=dead }}</ref>}}
| {{yes|Yes<ref>{{cite web|url=https://launchpad.net/bzr-interactive |title=Bazaar interactive plugin |date=7 March 2008 |publisher=Launchpad.net |access-date=2014-01-26}}</ref>}}
| {{yes|Yes<ref>{{cite web|url=http://launchpad.net/bzr-externals |title=Bazaar Externals plugin |date=9 November 2009 |publisher=Launchpad.net |access-date=2014-01-26}}</ref>}}
| {{no}}
| {{partial|execution bit only}}
| {{no}}<ref group="nb">not implemented [https://bugs.launchpad.net/bzr/+bug/245170 yet]</ref>
| {{yes}}<ref>{{cite web|url=https://answers.launchpad.net/bzr/+question/103163|title=Ignore merge operation for given extension|date=4 March 2010 }}</ref>
| bzr, subversion,<ref>{{cite web|url=http://launchpad.net/bzr-svn |title=bzr-svn |date=8 May 2006 |publisher=Launchpad.net |access-date=2014-01-26}}</ref> git,<ref>{{cite web|url=http://launchpad.net/bzr-git |title=bzr-git |date=15 July 2006 |publisher=Launchpad.net |access-date=2014-01-26}}</ref> hg,<ref>{{cite web|url=http://launchpad.net/bzr-hg |title=bzr-hg |date=13 June 2006 |publisher=Launchpad.net |access-date=2014-01-26}}</ref> any that has a fastexporter
| {{no}}
|-
! [[BitKeeper]]
| {{yes|[[POSIX]] and [[Revision Control System|RCS]]}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| bitkeeper
| {{no}}
|-
! [[CA Software Change Manager]]
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{partial|execution bit only}}
| {{yes}}
| {{yes}}
| CA Software Change Manager
| {{no}}
|-
! [[Rational ClearCase|IBM DevOps Code ClearCase]]
| {{yes}}<ref>[http://www.ibm.com/developerworks/rational/library/4311.html#N10496 IBM Rational ClearCase: The ten best triggers] from IBM DeveloperWorks</ref>
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}<ref group="nb">Can not be disabled in dynamic views.</ref>
| {{yes}}
| ClearCase
| {{yes}}
|-
! [[Concurrent Versions System|CVS]]
| {{yes|[[Revision Control System|RCS]]}}
| {{no}}
| {{yes}}
| {{yes}}<ref group="nb">Using alias of the CVSROOT/modules file.</ref>
| {{partial}}<ref group="nb">CVS records executable bit when a file is added, but does not allow changing it later on.</ref>
| {{yes}}
| {{no}}
| cvs
| {{no}}
|-
! [[CVSNT]]
| {{yes|[[Revision Control System|RCS]]}}
| {{yes}}<ref group="nb">This is a GUI feature supported by TortoiseCVS and WinCVS both of which include/use CVSNT.</ref>
| {{yes}}<ref group="nb">Same as CVS, plus also the ability to have replicated repositories including 'shadow' repositories.</ref>
| {{yes}}<ref group="nb">Use the module/directory name or an alias created using CVSROOT/modules or CVSROOT/modules2 administration file.</ref>
| {{yes}}
| {{yes}}
| {{no}}
| cvs
| {{yes}}<ref group="nb">CVSNT supports this when the make/build tool used also supports it.</ref>
|-
! [[darcs]]
| {{no}}
| {{yes}}
| {{no}}
| {{no}}<ref group="nb">Darcs can do sparse checkouts from explicit checkpoints on darcs-1 repositories, but not from darcs-2 ones{{Citation needed|date=February 2009}}</ref>
| {{partial}}<ref group="nb">Darcs can automatically detect #! scripts and make them executable on checkout.</ref>
| {{no}}
| {{partial|conflicts only}}
| darcs
| {{no}}
|-
! [[Dimensions CM]]
| {{yes}}
| {{no}}
| {{yes}}<ref group="nb">Using Sub Project functionality ([http://help.serena.com/doc_center/doc_center.html#dcm Documentation Portfolio | User's Guide | Relating a Project or Stream to Other Objects]).</ref>
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| Migration from ClearCase, Subversion, CVS, PVCS, ChangeMan DS
| {{unk}}
|-
! [[Fossil (software)|Fossil]]
| {{no}}
| {{yes}}
| {{yes}}<ref group="nb">Checkouts can be nested with "fossil open –nested"</ref>
| {{no}}
| {{partial|execution bit only}}<ref>[http://www.fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki#manifest The manifest], Fossil file formats</ref>
| {{no}}
| {{no}}
| fossil (uses sqlite), any that has a fastexporter;<ref>{{cite web |url=http://www.fossil-scm.org/index.html/doc/trunk/www/inout.wiki |title=Fossil import and export |publisher=Fossil-scm.org |date=2014-01-22 |access-date=2014-01-26 |archive-url=https://web.archive.org/web/20140202093934/http://www.fossil-scm.org/index.html/doc/trunk/www/inout.wiki |archive-date=2014-02-02 |url-status=dead}}</ref> migration from git and svn<ref>
[https://fossil-scm.org/home/help/import "FossilHelp: import"]
</ref>
| {{no}}
|-
! [[Git (software)|Git]]
| {{yes}}<ref group="nb">The [https://git.wiki.kernel.org/index.php/GitFaq#Does_Git_have_keyword_expansion.3F Git FAQ] states that keyword expansion is not a good thing</ref>
| {{yes}}<ref group="nb">''add -i'' and ''add -p'', see [http://www.kernel.org/pub/software/scm/git/docs/git-add.html git-add(1) Manual Page]</ref>
| {{yes}}<ref>{{cite web|url=http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html |title=git-submodule(1) Manual Page |publisher=Kernel.org |date=2013-02-15 |access-date=2014-01-26}}</ref>
| {{yes}}<ref>{{cite web|url=http://git-scm.com/docs/git-read-tree#_sparse_checkout|title=git-read-tree(1) Manual Page|publisher=kernel.org|date=2014-08-24|access-date=2014-10-24}}</ref>
| {{partial|execution bit only}}
| {{no}}<ref group="nb">The [https://git.wiki.kernel.org/index.php/GitFaq#Why_isn.27t_Git_preserving_modification_time_on_files.3F Git FAQ] explains why preserving modification time is considered harmful</ref>
| {{yes}}
| git, cvs, subversion, hg, any that has a fastexporter
| {{no}}
|-
! [[Mercurial]]
| {{yes}}<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/KeywordExtension |title=Mercurial KeywordExtension page |publisher=Mercurial-scm.org |access-date=2014-01-26}}</ref>
| {{yes}}<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/RecordExtension |title=Mercurial RecordExtension page |publisher=Mercurial-scm.org |date=2013-08-27 |access-date=2014-01-26}}</ref>
| {{yes}}<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/Subrepository?action=show&redirect=Subrepositories |title=Subrepository – Mercurial |publisher=Mercurial-scm.org |access-date=2016-04-22}}</ref>
| {{yes}}<ref>With the sparse extension included in core since [https://www.mercurial-scm.org/wiki/Release4.3 Hg Rev.:4.3].</ref>
| {{partial|execution bit only}}
| {{partial|through (alpha) extension}}<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/TimestampExtension |title=Mercurial Timestamp Extension |publisher=Mercurial-scm.org |date=2012-04-24 |access-date=2014-01-26}}</ref>
| {{yes}}<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/MergeToolConfiguration |title=Merge Tool Configuration |publisher=Mercurial-scm.org |date=2017-03-14 |access-date=2017-09-05}}</ref>
| hg, subversion,<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/HgSubversion |title=hgsubversion page |publisher=Mercurial-scm.org |date=2013-08-28 |access-date=2014-01-26}}</ref> lossless two-way push to and pull from git,<ref>{{cite web|url=https://hg-git.github.io/ |title=Hg-Git Mercurial Plugin |publisher=Hg-git.github.com |access-date=2014-01-26}}</ref> migration from any other format supported by the Convert extension:<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/ConvertExtension |title=Mercurial ConvertExtension page |publisher=Mercurial-scm.org |date=2013-11-29 |access-date=2014-01-26}}
</ref> CVS, Darcs, Bazaar, Monotone, GNU Arch, and Perforce<ref>
[https://book.mercurial-scm.org/read/app-svn.html "Mercurial: the definitive guide: Appendix: Migrating to Mercurial"]
</ref>
| {{no}}
|-
! [[Perforce Software#Helix Core|Perforce Helix Core]]
| {{yes}}<ref name=p4guide>{{cite web|url=https://www.perforce.com/perforce/doc.current/manuals/p4guide/|title=P4 User's Guide|publisher=Perforce|access-date=19 January 2018}}</ref>
| {{no}}
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}<ref name=p4guide/>
| {{yes}}<ref name=p4guide/>
| Perforce
| {{no}}
|-
! [[IBM Rational Team Concert|Rational Team Concert]]
| {{no}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{yes}}
| {{unk}}
| {{yes}}
| {{N/A}}
| {{no}}
|-
! [[Source Code Control System]]
| {{yes}}
| {{no}}
| {{N/A}}
| {{yes}}
| {{partial|execution bit only}}
| {{partial|some variants}}{{citation needed|date=July 2016}}
| {{no}}
| sccs
| {{no}}
|-
! [[Surround SCM]]
| {{yes}}
| {{no}}
| {{no}}
| {{yes}}
| {{no}}
| {{yes}}
| {{yes}}<ref group="nb">Configurable on server as a Project Option and on the client as a User Option.</ref>
| Surround
| {{no}}
|-
! [[Apache Subversion|Subversion]]
| {{yes}}<ref>{{cite web|url=http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html |title=Keyword Substitution |publisher=Svnbook.red-bean.com |access-date=2014-01-26}}</ref>
| {{partial}}<ref group="nb">Through third-party tools such as [[Tortoise SVN]].</ref>
| {{yes}}<ref>{{cite web|url=http://svnbook.red-bean.com/en/1.0/ch07s03.html |title=Externals Definitions |publisher=Svnbook.red-bean.com |access-date=2014-01-26}}</ref>
| {{yes}}
| {{partial|execution bit only}}
| {{partial}}<ref group="nb">SVN can not preserve file modification times. On request by the client, it can restore check-in time as last-modified time. Disabled by default.</ref>
| {{yes}}<ref group="nb">MIME type of the file must be detected as a "human-readable" MIME type, even if the merge tool can work with non-human-readable files</ref>
| subversion
| {{no}}
|-
! [[Vesta (Software configuration management)|Vesta]]
| {{no}}
| {{no}}
| {{yes}} via SDL
| {{no}}
| {{unk}}
| {{yes}}
| {{no}}
| Vesta
| {{yes}}
|-
! [[Microsoft Visual SourceSafe|Visual SourceSafe]]
| {{yes}}
| {{unk}}
| {{unk}}
| {{yes}}
| {{yes}}
| {{unk}}
| {{yes}}
| {{unk}}
| {{no}}
|-
! Software
! Keyword expansion
! Interactive commits
! External references
! {{verth|va=middle|Partial<br/>checkout/clone}}
! Permissions
! Timestamp preservation
! Custom automatic merge tool
! Supported formats
! {{verth|va=middle|Shared build cache<br/>of derived objects}}
|}

== Basic commands ==

The following table provides further information about commands available in notable version-control systems.

'''Table explanation'''
* '''''Repository init''''': Create a new empty repository (i.e., version control database)
* '''''clone''''': Create an identical instance of a repository (in a safe transaction)
* '''''pull''''': Download revisions from a remote repository to a local repository
* '''''push''''': Upload revisions from a local repository to a remote repository
* '''''Local branches''''': Create a local branch that does not exist in the original remote repository
* '''''checkout''''': Create a local working copy from a (remote) repository
* '''''update''''': Update the files in a working copy with the latest version from a repository
* '''''lock''''': Lock files in a repository from being changed by other users
* '''''add''''': Mark specified files to be added to repository at next commit
* '''''remove''''': Mark specified files to be removed at next commit (note: keeps cohesive revision history of before and at the remove.)
* '''''move''''': Mark specified files to be moved to a new location at next commit
* '''''copy''''': Mark specified files to be copied at next commit
* '''''merge''''': Apply the differences between two sources to a working copy path
* '''''commit''''': Record changes in the repository
* '''''revert''''': Restore working copy file from repository
* '''''generate bundle file''''': Create a file that contains a compressed set of changes to a given repository
* '''''rebase''''': Forward-port local commits to the updated upstream head
* '''Note:''' Commands in green rectangles that are not surrounded by [square brackets] are at an interactive command-line prompt. Text in [square brackets] is an explanation of where to find equivalent functionality.

{{sort-under}}
{| class="wikitable sortable sort-under" style="width: auto;"
|-
! Software
! {{nowrap|Repository init}}
! clone
! pull
! push
! Local branches
! checkout
! update
! lock
! add
! remove
! move
! copy
! merge
! commit
! revert
! generate bundle file
! rebase
<!--property, log, diff, backout, inserve, glog, email bundle file-->
|-
! [[AccuRev SCM]]
| {{mono|mkdepot}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|mkstream}}
| {{mono|mkws}}
| {{mono|update}}
| {{mono|anchor}}
| {{mono|add}}
| {{mono|defunct}}
| {{mono|move}}
| {{mono|cp}}<br/>[then]<br/>{{mono|add – incl {{nowrap|-s}} – ln}}
| {{mono|merge}}
| {{mono|keep – promote}}
| {{mono|purge – revert}}
| {{N/A|N/A}}
| {{mono|chstream}}
|-
![[Team Foundation Server|Azure DevOps]]
|using [[Git]]
|clone using [[Git]]
|get
|commit
|shelveset
|checkout
|get
|lock
|add
|delete
|rename
|using [[Git]]
|merge
|commit
|undo
|using [[Git]]
|get
|-
! [[GNU Bazaar]]
| {{mono|init – {{nowrap|init -no-tree}}}}<ref group="nb">{{citation |url=http://wiki.bazaar.canonical.com/StandaloneBranch |title=Standalone Branch |access-date=2014-11-06 |archive-date=2016-03-04 |archive-url=https://web.archive.org/web/20160304051444/http://wiki.bazaar.canonical.com/StandaloneBranch |url-status=dead }}</ref> – {{mono|init-repo – {{nowrap|init-repo -no-trees}}}}<ref group="nb">{{citation |url=http://wiki.bazaar.canonical.com/SharedRepository |title=Shared Repository |access-date=2014-11-06 |archive-date=2016-03-04 |archive-url=https://web.archive.org/web/20160304051558/http://wiki.bazaar.canonical.com/SharedRepository |url-status=dead }}</ref>
| {{mono|branch – {{nowrap|branch -no-tree}}}}<ref group="nb">{{citation |url=http://wiki.bazaar.canonical.com/StandaloneBranch |title=Standalone Branch |access-date=2014-11-06 |archive-date=2016-03-04 |archive-url=https://web.archive.org/web/20160304051444/http://wiki.bazaar.canonical.com/StandaloneBranch |url-status=dead }}</ref>
| {{mono|pull}}
| {{mono|push}}
| {{mono|init – branch}}
| {{mono|checkout – {{nowrap|checkout -lightweight}}}}<ref group="nb">{{citation |url=http://wiki.bazaar.canonical.com/Checkout |title=Heavyweight Checkout and Lightweight Checkout |access-date=2014-11-06 |archive-date=2016-06-30 |archive-url=https://web.archive.org/web/20160630164203/http://wiki.bazaar.canonical.com/Checkout |url-status=dead }}</ref>
| {{mono|update}}
| {{N/A|N/A}}
| {{mono|add}}
| {{mono|rm}}
| {{mono|mv}}
| {{N/A|N/A}}
| {{mono|merge}}
| {{mono|commit}}
| {{mono|revert}}
| {{mono|send}}
| {{mono|rebase}}<ref group="nb">rebase plugin</ref>
|-
! [[BitKeeper]]
| {{mono|setup}}
| {{mono|clone}}
| {{mono|pull -R}}
| {{mono|push}}
| {{mono|clone}}
| {{mono|co}}
| {{mono|pull}}
| {{unk}}
| {{mono|add}}
| {{mono|rm}}
| {{mono|mv}}
| {{mono|cp}}
| {{mono|pull}}
| {{mono|commit}}
| {{mono|undo}}
| {{mono|makepatch}}
| {{mono|collapse}}
|-
! [[Rational ClearCase|IBM DevOps Code ClearCase]]
| {{mono|init}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|checkout}}
| {{mono|update}}
| {{mono|lock – unlock}}
| {{mono|mkelem}}
| {{mono|rmname}}
| {{mono|mv}}
| {{N/A|N/A}}
| {{mono|merge}}
| {{mono|checkin}}
| {{mono|uncheckout – rmver}}
| {{N/A|N/A}}
| {{mono|findmerge}}
|-
! [[Concurrent Versions System|CVS]]
| {{mono|init}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|checkout}}
| {{mono|update}}
| {{unk}}
| {{mono|add}}
| {{mono|rm}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|update -j}}
| {{mono|commit}}
| {{partial|{{mono|remove}} [then] {{mono|update}}}}
| {{N/A|N/A}}
| {{N/A|N/A}}
|-
! [[CVSNT]]
| {{mono|init}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|checkout}}
| {{mono|update}}
| {{mono|edit}}
| {{mono|add}}
| {{mono|rm}}
| {{mono|rename}}
| {{N/A|N/A}}
| {{mono|update -j}}
| {{mono|commit}}
| {{mono|update -C}}
| {{N/A|N/A}}
| {{N/A|N/A}}
|-
! [[darcs]]
| {{mono|init}}
| {{mono|clone}}
| {{mono|pull}}<ref name="darcs pull">darcs's default ''pull'' command is interactive, allowing the user to choose which patches to apply (merge) in realtime</ref>
| {{mono|push}}
| {{N/A|N/A<ref group="nb">darcs doesn't have named branches, local or not, branching is handled solely through repository cloning</ref>}}
| {{mono|clone}}
| {{mono|pull<ref name="darcs pull"/>}}
| {{unk}}
| {{mono|add}}
| {{mono|remove}}
| {{mono|move}}
| {{N/A|N/A}}
| {{mono|pull – push}}
| {{mono|record}}
| {{mono|revert}}
| {{mono|send -o}}<ref group="nb">''darcs send'' prepares a bundle of patches, defaults to sending it by mail but can send it to a file instead</ref>
| {{mono|rebase}}
|-
! [[Fossil (software)|Fossil]]
| {{mono|new – open}}
| {{mono|clone}}
| {{mono|pull}}
| {{mono|push}}
| {{mono|branch – commit –branch}}
| {{mono|clone/open}}
| {{mono|update}}
| {{N/A|N/A}}
| {{mono|add}}
| {{mono|rm/del}}
| {{mono|mv/rename}}
| {{N/A|N/A}}
| {{mono|merge}}
| {{mono|commit}}
| {{mono|revert}}
| Fossil's repository is single sqlite file itself
| {{N/A|N/A}}
|-
! [[Git (software)|Git]]
| {{mono|init – init –bare}}
| {{mono|clone – clone –bare}}
| {{mono|fetch}}
| {{mono|push}}
| {{mono|branch}}
| {{mono|checkout}}
| {{mono|pull}}
| {{N/A|N/A}}
| {{mono|add}}
| {{mono|rm}}
| {{mono|mv}}
| {{partial|{{mono|cp}}<br/>[then]<br/>{{mono|git add}}<ref group="nb">copies are detected after the fact, much like renames</ref>}}
| {{mono|merge}}
| {{mono|commit}}
| {{mono|reset –hard}}
| {{mono|bundle}}
| {{mono|rebase}}
|-
! [[Mercurial (software)|Mercurial]]
| {{mono|init}}
| {{mono|clone}}
| {{mono|pull}}
| {{mono|push}}
| {{mono|bookmark<ref group="nb">[https://www.mercurial-scm.org/wiki/Bookmarks Mercurial Bookmarks] are similar to local branches.</ref>}}
| {{mono|update – up – checkout – co}}
| {{mono|pull -u}}
| {{N/A|N/A}}
| {{mono|add}}
| {{mono|remove – rm}}
| {{mono|move – mv}}
| {{mono|copy – cp}}
| {{mono|merge}}
| {{mono|commit – ci}}
| {{mono|revert}}
| {{mono|bundle}}
| {{mono|rebase}}<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/RebaseExtension |title=Mercurial Rebase Extension |publisher=Mercurial-scm.org |date=2012-10-25 |access-date=2014-04-23}}</ref>
|-
! [[Monotone (software)|Monotone]]
| {{mono|init}}
| {{mono|clone}}
| {{mono|pull}}
| {{mono|push}}
| {{N/A|N/A}}
| {{mono|checkout}}
| {{mono|update}}
| {{unk}}
| {{mono|add}}
| {{mono|drop}}
| {{mono|rename}}
| {{N/A|N/A}}
| {{mono|merge}}
| {{mono|commit}}
| {{mono|revert}}
| {{N/A|N/A}}
| {{N/A|N/A}}
|-
! [[Perforce Software#Helix Core|Perforce Helix Core]]
| {{mono|p4 client && p4 sync}}
| {{mono|p4 sync}}
| {{mono|p4 sync}}
| {{mono|p4 submit}}
| {{partial|Requires migration to recent streams feature}}
| {{mono|edit}}
| {{mono|sync}}
| {{mono|lock – unlock}}
| {{mono|add}}
| {{mono|delete}}
| {{mono|move}}
| {{mono|copy}}
| {{mono|integrate}}
| {{mono|submit}}
| {{mono|revert}}
| {{unk}}
| {{N/A|N/A}}
|-
! [[Source Code Control System]]
| {{mono|create}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|admin -fb}}
| {{mono|get (readonly) – edit}}
| {{mono|get (readonly) – edit}}
| {{N/A|N/A}}<ref group="nb">SCCS has implicit locks, applied when checking out via <code>edit</code>, removed when creating a delta.</ref>
| {{mono|create}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|edit -i}}
| {{mono|delta}}
| {{mono|get -r}}
| {{N/A|N/A}}
| {{mono|edit -i}}
|-
! [[Apache Subversion|Subversion]]
| {{mono|svnadmin create}}
| {{mono|svnadmin hotcopy}}
| {{no|{{nowrap|[work-around]:}} {{mono|svnadmin load}}}}
| {{no|{{nowrap|[work-around]:}} {{mono|svnadmin dump}}}}
| {{N/A|N/A}}
| {{mono|checkout – co}}
| {{mono|update – up}}
| {{mono|lock}}
| {{mono|add}}
| {{mono|delete – del – remove – rm}}
| {{mono|move – mv – rename – ren}}
| {{mono|copy – cp}}
| {{mono|merge}}
| {{mono|commit – ci}}
| {{mono|revert}}
| {{N/A|N/A}}
| {{N/A|N/A}}
|-
! [[Surround SCM]]
| {{mono|mkmainline}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|mkbranch}}
| {{mono|checkout}}
| {{mono|get}}
| {{mono|checkout}}
| {{mono|add}}
| {{mono|rm}}
| {{mono|move}}
| {{N/A|N/A}}
| {{mono|merge}}
| {{mono|checkin}}
| {{mono|voidcheckout}}
| {{N/A|N/A}}
| {{mono|rebase}}
|-
! [[Vesta (Software configuration management)|Vesta]]
| {{mono|vcreate}}
| {{mono|vrepl}}
| {{mono|vrepl}}
| {{mono|vrepl}}
| {{N/A|N/A}}
| {{mono|vcheckout}}
| {{mono|vadvance}}
| {{mono|vcheckout}}
| [... then]<br/>{{mono|vcheckin}}<ref group="nb">Through any of various means, place (to-be-immutable) file in an immutable directory prior to vcheckin.</ref>
| {{mono|vrm}}
| {{mono|mv}}<br/>[then]<br/>{{mono|vcheckin}}<ref group="nb">mv(1) or link(2) the immutable file from its origin immutable directory to its destination immutable directory prior to vcheckin.</ref>
| {{mono|cp}}<br/>[then]<br/>{{mono|vcheckin}}<ref group="nb">Through any of various means, copy the immutable file from its origin immutable directory to its destination immutable directory prior to vcheckin.</ref>
| {{mono|vdiff}}
| {{mono|vcheckin}}
| {{nowrap|{{mono|vcheckin -c 0}}}}
| {{mono|vmake}} [or] {{mono|vesta}}
| {{mono|vadvance}}
|-
! [[Microsoft Visual SourceSafe|Visual SourceSafe]]
| {{dunno}}
| {{unk}}
| {{unk}}
| {{unk}}
| {{N/A|N/A}}
| {{button|Get Latest}}
| {{button|Get Latest}}
| {{button|Check Out}}
| {{button|Add Files}}
| {{button|Delete}}
| {{dunno}}
| {{unk}}
| {{dunno}}
| {{button|Check In}}
| {{button|Undo Check Out}}
| {{unk}}
| {{unk}}
|- class="sortbottom"
! Software
! Repository init
! clone
! pull
! push
! Local branches
! checkout
! update
! lock
! add
! remove
! move
! copy
! merge
! commit
! revert
! generate bundle file
! rebase
|}

== Advanced commands ==

The following table shows the commands used to execute common tasks in notable version-control systems.

'''Table explanation'''
* '''''Command aliases''''': create custom aliases for specific commands or combination thereof
* '''''Lock/unlock''''': exclusively lock a file to prevent others from editing it
* '''''Shelve/unshelve''''': temporarily set aside part or all of the changes in the working directory
* '''''Rollback''''': remove a patch/revision from history
* '''''Cherry-picking''''': move only some revisions from a branch to another one (instead of merging the branches)
* '''''Bisect''''': binary search of source history for a change that introduced or fixed a regression
* '''''Incoming/outgoing''''': query the differences between the local repository and a remote one (the patches that would be fetched/sent on a pull/push)
* '''''Grep''''': search repository for lines matching a pattern
* '''''Record''''': include only some changes to a file in a commit and not others
* '''Note''': Commands in green rectangles that are not surrounded by [square brackets] are at an interactive command-line prompt.  Text in [square brackets] is an explanation of where to find equivalent functionality.

{{sort-under}}
{| class="wikitable sortable sort-under" style="width: auto;"
|-
! Software
! Command aliases
! Lock/unlock
! Shelve/unshelve
! Rollback
! Cherry-picking
! Bisect
! Incoming/outgoing
! Grep
! Record
<!-- glog, email bundle file-->
|-
! [[AccuRev SCM]]
| {{N/A|N/A}}
| enable file locking
| {{N/A|N/A}}
| {{mono|revert -purge}}
| {{mono|promote}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{unk}}
|-
! [[Team Foundation Server|Azure DevOps]]
| {{yes}}
| {{mono|lock/unlock}}
| {{mono|shelve/unshelve}}
| {{mono|rollback}}
| {{mono|merge}}
| {{N/A|N/A}}
| {{unk}}
| {{unk}}
| {{N/A|N/A}}
|-
! [[GNU Bazaar]]
| [in '.bazaar/bazaar.conf' file]
| {{N/A|N/A}}
| {{mono|shelve/unshelve}}
| {{mono|uncommit}}
| {{mono|merge}} (non-tracking)
| {{mono|bisect}} (bisect plugin)
| missing {{nowrap|{{mono|-theirs-only}}}} / {{nowrap|{{mono|-mine-only}}}}
| {{mono|grep}} (grep plugin)
| {{N/A|N/A}}
|-
! [[BitKeeper]]
| {{unk}}
| {{unk}}
| {{mono|park/unpark}}
| {{mono|undo}}
| {{unk}}
| {{mono|bisect}}
| {{mono|changes -R/-L}}
| {{mono|grep}}
| {{unk}}
|-
! [[CVSNT]]
| [in '.cvsrc' file]
| {{mono|{{nowrap|edit -x}}/unedit}}<ref group="nb">One can also enable this as a central preference in the repository server control panel or configuration file.</ref>
| {{N/A|N/A}}
| {{mono|admin -o<ref group="nb">Requires administrator privileges. One can 'roll back' a change using '{{code|cvs update -e -j @commitid -j "@<commitid"}}' but the change and rollback evidence remain in the history.</ref>}}
| {{mono|yes<ref group="nb">yes - use TortoiseCVS or WinCVS to commit the change to the destination and select which specific files to keep</ref>}}
| {{mono|annotate<ref group="nb">bisect is also available for cvs which should work with CVSNT</ref>}}
| {{N/A|N/A}}
| {{N/A|N/A}}<ref>{{cite web|title=bug 6463 - enh: search repository|url=http://customer.march-hare.com/webtools/bugzilla/ttshow_bug.cgi?id=6463&tt=1|access-date=8 May 2012}}</ref>
| {{N/A|N/A}}
|-
! [[Darcs]]
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|revert/unrevert}}
| {{mono|unrecord}}
| {{mono|yes<ref group="nb">darcs operate on patches not revision, cherrypicking simply consists in pulling a given patch from one repository to another one as long as the dependencies are fulfilled</ref>}}
| {{mono|test -bisect}}
| {{mono|pull/push {{nowrap|-dry-run}}}}
| {{N/A|N/A}}
| {{mono|record}}
|-
! [[Fossil (software)|Fossil]]
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|stash pop/stash apply}}<ref group="nb">fossil stash supports multiple shelves with comments.</ref>
| {{mono|merge -rollback}}
| {{nowrap|{{mono|merge -cherrypick}}}}
| {{mono|bisect}}
| {{N/A|N/A}}
| {{mono|search}}
| {{N/A|N/A}}
|-
! [[Git (software)|Git]]
| [in '.gitconfig' file]
| {{N/A|N/A}}
| {{mono|stash/stash pop<ref group="nb">git stash is a multi-level shelve, it's possible to shelve several change groups at the same time</ref>}}
| {{mono|reset HEAD^}}
| {{mono|cherry-pick}}
| {{mono|bisect}}
| {{mono|cherry}}
| {{mono|grep}}
| {{mono|add -p}}
|-
! [[Mercurial (software)|Mercurial]]
| [in '.hgrc' file]
| {{N/A|N/A}}
| {{mono|shelve/unshelve}} (bundled extension<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/ShelveExtension |title=Mercurial Shelve extension page |publisher=Mercurial-scm.org |date=2013-11-07 |access-date=2014-01-26}}</ref>)
| {{mono|strip}} (bundled extension<ref>{{cite web|title=Mercurial Strip extension page|url=https://www.mercurial-scm.org/wiki/StripExtension|access-date=11 May 2016|publisher=Mercurial-scm.org}}</ref>)
| {{mono|graft}} (core<ref>{{cite web|url=http://www.selenic.com/mercurial/hg.1.html#graft |title=graft -core command (since Hg Rev.2.0) |publisher=Selenic.com |access-date=2014-01-26}}</ref>) or {{mono|transplant}} (bundled extension<ref>{{cite web|url=https://www.mercurial-scm.org/wiki/TransplantExtension |title=Mercurial Transplant extension page |publisher=Mercurial-scm.org |date=2012-05-12 |access-date=2014-01-26}}</ref>)
| {{mono|bisect}}
| {{mono|incoming/outgoing}}
| {{mono|grep}}
| {{nowrap|{{mono|commit -interactive}}}}
|-
! [[Monotone (software)|Monotone]]
| [in monotonerc]
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{mono|kill_rev_locally<ref group="nb">Only works on a local repository and only on revisions without children. The disapprove command might be an alternative.</ref>}}
| {{mono|pluck}}
| {{mono|bisect}}
| {{N/A|N/A}}
| {{N/A|N/A}}
| {{unk}}
|-
! [[Perforce Software#Helix Core|Perforce Helix Core]]
| {{mono|via broker<ref>{{cite web |url=http://www.perforce.com/perforce/r10.2/manuals/p4sag/11_broker.html |title=The Perforce Broker |publisher=Perforce.com |access-date=2014-01-26 |archive-date=2013-11-16 |archive-url=https://web.archive.org/web/20131116041152/http://www.perforce.com/perforce/r10.2/manuals/p4sag/11_broker.html |url-status=dead}}</ref>}}
| {{mono|lock/unlock}}
| {{mono|shelve/unshelve}}
| {{mono|obliterate}}
| {{mono|integ<ref>{{cite web |url=http://kb.perforce.com/article/567/ |title=Perforce Knowledge Base: "Cherry Picking" Integrations |publisher=Kb.perforce.com |date=1990-01-01 |access-date=2014-01-26 |archive-url=https://web.archive.org/web/20120309215524/http://kb.perforce.com/article/567 |archive-date=2012-03-09 |url-status=dead}}</ref>}}
| {{unk}}
| {{mono|interchanges}}
| {{mono|grep}}
| {{unk}}
|-
! [[Apache Subversion|Subversion]]
| {{N/A|N/A}}
| {{mono|lock/unlock}}
| {{mono|shelve/unshelve<ref group="nb">experimental in SVN 1.10 ([https://subversion.apache.org/docs/release-notes/1.10#shelving release notes])</ref>}}
| {{N/A|N/A}}
| {{mono|svnmerge cherry-picking}}
| Third party tool<ref group="nb">SVN Bisect tool [http://search.cpan.org/dist/App-SVN-Bisect/bin/svn-bisect svn-bisect]</ref>
| {{N/A|{{mono|status -u}}<ref group="nb">svn status lists differences between working copy and repository, not differences between two repositories</ref>}}
| {{N/A|N/A}}
| {{N/A|N/A}}
|-
! [[Surround SCM]]
| {{N/A|N/A}}
| {{mono|checkout}}
| {{mono|shelf}}
| {{mono|rollback}}
| {{mono|duplicatechanges}}
| {{N/A|N/A}}
| {{mono|diff}}
| {{mono|search}}
| {{N/A|N/A}}
|- class="sortbottom"
! Software
! Command aliases
! Lock/unlock
! Shelve/unshelve
! Rollback
! Cherry-picking
! Bisect
! Incoming/outgoing
! Grep
! Record
|}

== User interfaces ==

The following table gives Web, GUI and IDE Interface specifications for notable version-control systems.

'''Table explanation'''
* '''''Software''''': The name of the application that is described.
* '''''Web Interface''''': Describes whether the software application contains a web interface. A web interface could allow the software to post diagnostics data to a website, or could even allow remote control of the software application.
* '''''GUIs''''': A GUI is a graphical user interface. If a software product features a GUI its functionality can be accessed through application windows as opposed to accessing functionality based upon typing commands at the command prompt such as a DOS interface.
* '''''Plug-ins''''': functions are available through an [[integrated development environment]]. Minimum function should be to list the revision state of a file and check in/check out files.

{| class="wikitable sortable" style="font-size: 85%; text-align: center; width: auto;"
|-
! Software
! Web interfaces
! Stand-alone [[Graphical user interface|GUI]]s
! Integration and/or Plug-ins for [[Integrated development environment|IDE]]s
|-
! {{Rh}} | [[AccuRev SCM]]
| Yes
| [[Microsoft Windows|Windows (incl. Explorer integration)]], [[Linux]], [[Unix]], [[macOS]], [[BeOS]] available
| [[IntelliJ IDEA]], [[Eclipse (software)|Eclipse]], [[Microsoft Visual Studio|Visual Studio]]
|-
! {{Rh}} | [[Team Foundation Server|Azure DevOps]]
| {{yes2}} included (SharePoint Server used for web services)
| Windows included; macOS, Unix available
| Visual Studio. Java client for Eclipse IDE and IntelliJ IDEA (standard in Ultimate Edition)
|-
! {{Rh}} | [[GNU Bazaar]]
| can use a plain webserver
| Olive, bzr-gtk ([[GTK]]+), Bazaar Explorer ([[Qt (software)|Qt]]), QBzr ([[Qt (software)|Qt]]), [[TortoiseBzr]] (Windows)
| Eclipse (BzrEclipse, QBzrEclipse), Visual Studio (bzr-visualstudio), TextMate (TextMateBundle), [[ActiveState Komodo|Komodo IDE]], [[Wing IDE]]
|-
! {{Rh}} | [[BitKeeper]]
| included
| included (bkd)
| {{Unk}}
|-
! {{Rh}} | [[CA Software Change Manager]]
| included
| Eclipse-based GUI
| [[Eclipse (software)|Eclipse]], MS Visual Studio
|-
! {{Rh}} | [[Rational ClearCase|IBM DevOps Code ClearCase]]
| {{yes2}} included, Clearcase Web Interface
| older: MS Windows native, Motif-based GUI for [[Unix-like]] systems, [[Time Sharing Option|TSO]] client for [[z/OS]].
| [[Emacs]], Eclipse ( IBM Proprietary, Eclipse-CCase ), Visual Studio (IBM proprietary), [[KDevelop]] (standard?), IntelliJ IDEA (standard in Ultimate Edition)
|-
! {{Rh}} | [[Code Co-op]]
| Not necessary since entire project is replicated locally
| Windows
| {{Unk}}
|-
! {{Rh}} | [[Concurrent Versions System|CVS]]
| cvsweb, [[ViewVC]], others
| [[TortoiseCVS]] (Windows Explorer), TkCVS ([[Tcl (programming language)|Tcl]]/[[Tk (software)|Tk]]), [[WinCVS]], macOS, [[GTK]], Qt available
| [[Eclipse (software)|Eclipse]] (Team), KDevelop (standard), IntelliJ IDEA (standard in Community and Ultimate Editions), [[Emacs]] (standard VC), [[ActiveState Komodo|Komodo IDE]], [[BBEdit]], [[Wing IDE]]
|-
! {{Rh}} | [[CVSNT]]
| cvsweb, [[ViewVC]], others
| Windows, macOS, [[OS/400]], [[GTK]], Qt available
| All those that support CVS, plus commercial plugins for SCCI, Bugzilla, Build
|-
! {{Rh}} | [[darcs]]
| {{yes2}} <code>darcs.cgi</code> included; darcsweb, [[Trac]]
| under development; [[TortoiseDarcs]] (Windows Explorer), macOS (alpha),
| [[Eclipse (software)|Eclipse]] (eclipsedarcs), [[Emacs]] (vc-darcs.el)
|-
! {{Rh}} | [[Dimensions CM]]
| {{yes}}
| [[Microsoft Windows|Windows (incl. explorer integration)]]
| [[Eclipse (software)|Eclipse]], [[Microsoft Visual Studio|Visual Studio]], [[IntelliJ IDEA]], [[XCode]], [[Powerbuilder]]
|-
! {{Rh}} | [[Fossil (software)|Fossil]]
| {{yes2}} Embedded webserver included (ui/server mode), ability to run multiple repositories via CGI mode
| fuel-scm
| {{Unk}}
|-
! {{Rh}} | [[Git (software)|Git]]
| {{yes2}} Gitweb, wit, cgit, [[GitLab]], [[GitHub]], [[gitorious]], [[Trac]], [[Kallithea (software)|Kallithea]], [[Bitbucket]],  Stash, [[Springloops]], Bonobo Git Server, [[Gitea]], Gogs
| gitk([[Wish (Unix shell)|wish]]), git-gui ([[Tcl (programming language)|Tcl]]/[[Tk (software)|Tk]]), tig, Gitbox ([[macOS]]), [[TortoiseGit]], qgit, gitg ([[GNOME]]/[[GTK]]), (h)gct ([[Qt (software)|Qt]]), git-cola (Qt), Git Extensions (Windows), GitEye, SmartGit/Hg, Tower, SourceTree (macOS/Windows), Sprout (macOS), GitX (macOS), GitUp (macOS), [[GitKraken]], Sublime Merge
| Aptana 3 Beta (Aptana Studio 3 with Git Integration); [[Atom (text editor)|Atom]]; Eclipse (JGit/EGit); [[Perforce Software#Other products|Helix TeamHub]]; Netbeans (NbGit); [[KDevelop]]; Visual Studio (Git Extensions); [[Emacs]] (extension for standard VC, [[Magit]]); SAP Web IDE; TextMate (Git TextMate Bundle); Vim (VCSCommand plugin and fugitive plugin); IntelliJ IDEA >8.1 (standard in Community and Ultimate Editions); [[ActiveState Komodo|Komodo IDE]]; [[Anjuta]]; [[XCode]], [[Wing IDE]]; [[PyCharm]]
|-
! {{Rh}} | [[GNU arch]]
| ArchZoom
| ArchWay ([[GTK]]2), TlaLog
| [[Emacs]] (standard VC)
|-
! {{Rh}} | [[IC Manage]]
| {{yes2}} included
| Windows, Linux, Unix, macOS
| Emacs, Cadence Design Framework, Synopsys Custom Designer
|-
! {{Rh}} | [[MKS Integrity]]
| {{yes2}} Yes
| Windows, Linux, Unix, Solaris, AIX,
| Eclipse, Microsoft Visual Studio, Perforce and others. Also provides support for the industry standard Source Code Control (SCC) interface<ref>{{cite web |url=http://www.mks.com/customer-service/supported-versions-platforms-integrations/supported-integrations |title=Supported Integrations – PTC Integrity |publisher=Mks.com |date=2012-09-10 |access-date=2014-01-26 |url-status=dead |archive-url=https://web.archive.org/web/20120725110643/http://www.mks.com/customer-service/supported-versions-platforms-integrations/supported-integrations |archive-date=2012-07-25}}</ref>
|-
! {{Rh}} | [[Mercurial]]
| {{yes2}} included,<ref group="nb">hgweb for single-repository access and hgwebdir for multiple repository access from a single HTTP address</ref> [[Trac]], [[Kallithea (software)|Kallithea]]
| Hgk ([[Tcl (programming language)|Tcl]]/[[Tk (software)|Tk]]), (h)gct (Qt), TortoiseHg (Windows Explorer, Nautilus), MacHg,
MacMercurial, Murky, SourceTree (Windows/macOS), TortoiseHg, SmartGit/Hg
| IntelliJ IDEA (hg4idea 3rd party plugin), Eclipse (Mercurial Eclipse), NetBeans, Visual Studio 2008, [[Emacs]], Vim (VCSCommand plugin), [[ActiveState Komodo|Komodo IDE]], [[Eric Python IDE]], [[Wing IDE]]
|-
! {{Rh}} | [[Monotone (software)|Monotone]]
| ViewMTN, TracMonotone,
| Monotone-Viz ([[GTK]]+), Guitone ([[Qt (software)|Qt]]), Monotone Browser ([[GTK]]+, [[Perl]])
| {{Unk}}
|-
! {{Rh}} | [[Perforce Software#Helix Core|Perforce Helix Core]]
| {{yes2}} included, P4Web, P4FTP
| Windows, Linux, Mac macOS
| [[Eclipse (video game)|Eclipse]], [[Visual Studio]], [[Matlab]]; Game Engines: [[Unity (game engine)|Unity]], [[Unreal Engine|Unreal]], [[Amazon Lumberyard]]; Graphics: [[Autodesk Maya]], [[3ds max]], [[Adobe PS]]
|-
! {{Rh}} | [[IBM Rational Team Concert|Rational Team Concert]]
|{{yes2}} Yes
| Eclipse-based GUI
| Eclipse integration; MS Visual Studio integration(Limited)
|-
! {{Rh}} | [[StarTeam]]
| {{yes2}} included
| Windows, [[Java (programming language)|Java]], Eclipse, Visual Studio, BDS2006 integration, plus Java command-line
| IntelliJ IDEA (standard in Ultimate Edition), Visual Studio, JBuilder, Eclipse
|-
! {{Rh}} | [[Apache Subversion|Subversion]]
| {{yes2}} Apache 2 module included, WebSVN, ViewSVN, [[ViewVC]], [[Trac]], [[SharpForge]], sventon, [[Springloops]]
| Java, KDESVN, macOS<ref>{{Cite web |url=http://www.lachoseinteractive.net/en/community/subversion/svnx/features/ |title=La Chose : web agency and software maker – agence web et développement de logiciels<!-- Bot generated title --> |access-date=2006-09-20 |archive-url=https://web.archive.org/web/20160618161540/http://www.lachoseinteractive.net/en/community/subversion/svnx/features/ |archive-date=2016-06-18 |url-status=dead}}</ref> (including Finder integration), Nautilus, Qt, [[RabbitVCS]], [[RapidSVN]], SourceTree (macOS), [[TortoiseSVN]] (Windows Explorer)
| [[Anjuta]], [[BBEdit]], Eclipse (Subclipse, Subversive), [[Emacs]] (standard VC), IntelliJ IDEA (standard in Community and Ultimate Editions), KDevelop (standard), [[ActiveState Komodo|Komodo IDE]], [[MonoDevelop]] (standard), Netbeans, [[RabbitVCS]] (for GEdit), [[TextMate]] (SVNMate plugin), Visual Studio ([[AnkhSVN]], [[VisualSVN]]), [[Wing IDE]]. See also [[Comparison of Subversion clients]]
|-
! {{Rh}} | [[Surround SCM]]
| Yes
| Windows, macOS, Linux
| [[Eclipse (software)|Eclipse]], [[IntelliJ IDEA]], [[JDeveloper]], [[NetBeans]], [[Visual Studio]], [[WebStorm]]
|-
! {{Rh}} | [[Telelogic Synergy|Synergy]]
| {{yes2}} via Telelogic Change interface
| Windows (incl. explorer integration), Linux, Unix
| Eclipse (Telelogic proprietary), Visual Studio (Telelogic proprietary), IntelliJ IDEA (Telelogic proprietary)
|-
! {{Rh}} | [[Vault (revision control system)|Vault]]
| {{yes2}} included
| Windows, Unix-like, macOS
| Visual Studio 2003 and higher, Eclipse 3.2 and higher
|-
! {{Rh}} | [[Vesta (Software configuration management)|Vesta]]
| {{yes2}} VestaWeb
| {{no}}
| {{no}}
|-
! {{Rh}} | [[Microsoft Visual SourceSafe|Visual SourceSafe]]
|  none included; SSWI, VSS Remoting
| Windows included; Linux, macOS and Solaris using SourceOffSite; any Java VM using [[Sourceanywhere]] for VSS
| Visual Studio, IntelliJ IDEA (standard in Ultimate Edition)
|- class="sortbottom"
! Software
! Web interfaces
! Stand-alone [[Graphical user interface|GUI]]s
! Integration and/or plug-ins for [[Integrated development environment|IDE]]s
|}

== History and adoption ==

The following table provides historic background notes on various version-control systems:

'''Table explanation'''
* ''Software'': The name of the application that is described.
* ''History'': briefly describes the software's origins and development.
* ''Notable current users'': is a list of well known projects using the software as their ''primary'' revision control system, excluding the software itself, followed by a link to a full list if available.

{| class="wikitable sortable" style="font-size: 85%; text-align: center; width: auto;"
|-
! Software
! History
! Notable current users
|-
! {{Rh}} | [[AccuRev SCM]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2002|format=hide}} First publicly released in 2002
|
|-
! {{Rh}} | [[Team Foundation Server|Azure DevOps Server]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2006|03|format=hide}} First publicly released in March, 2006 as Visual Studio Team System, renamed to Team Foundation Server in 2010 and Azure DevOps Server in 2019.
| style="text-align: left; padding-left: 0.5em" | [[Microsoft]]
|-
! {{Rh}} | [[Visual Studio Team Services|Azure DevOps Services]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2012|format=hide}} First publicly released in 2012 as Team Foundation Service, renamed to Visual Studio Online in 2013, Visual Studio Team Services in 2015 and Azure DevOps in 2018.
| style="text-align: left; padding-left: 0.5em" | Microsoft
|-
! {{Rh}} | [[GNU Bazaar]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2005|03|26|format=hide}} Initial release March 26, 2005. Loosely related to [[Baz (software)|baz]]. Sponsored by [[Canonical Ltd.]]
|
|-
! {{Rh}} | [[BitKeeper]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2000|05|04|format=hide}} Initial release May 4, 2000. Influenced by [[Sun WorkShop TeamWare]]
|
|-
! {{Rh}} | [[CA Harvest Software Change Manager|CA Software Change Manager]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1995|format=hide}} Original company founded in 1977;  CA SCM (then called CCC/Harvest) first released in 1995.
|
|-
! {{Rh}} | [[Rational ClearCase|IBM DevOps Code ClearCase]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1990|format=hide}} Developed beginning in 1990 by Atria Software, following concepts developed by [[Apollo Computer]] in DSEE during the 1980s. The most recent version is 9.0.0, released in March 2016.
|
|-
! {{Rh}} | [[Code Co-op]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1997|format=hide}} The first distributed VCS, demoed in 1997,<ref>{{cite book|url=http://portal.acm.org/citation.cfm?id=716428&dl=ACM&coll=portal |title=Distributed Source Control System |publisher=Portal.acm.org |date=1997-05-18 |pages=98–107 |isbn=9783540630142 |access-date=2014-01-26}}</ref> released soon after.
| style="text-align: left; padding-left: 0.5em" |
|-
! {{Rh}} | [[Concurrent Versions System|CVS]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1986|07|03|format=hide}} First publicly released July 3, 1986; based on [[Revision Control System|RCS]]
| style="text-align: left; padding-left: 0.5em" | [[NetBSD]], [[OpenBSD]]
|-
! {{Rh}} | [[CVSNT]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1998|format=hide}} First publicly released 1998; based on [[Concurrent Versions System|CVS]].  Started by [[Concurrent Versions System|CVS]] developers with the goal adding support for a wider range of development methods and processes.
|
|-
! {{Rh}} | [[darcs]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2003|04|09|format=hide}} First announced on April 9, 2003
|
|-
! {{Rh}} | [[Dimensions CM]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1989|format=hide}} Developed by SQL Software under the name "PCMS Dimensions" during the late 1980s (PCMS standing for Product Configuration Management). Through number of company acquisitions the product was released under names "PVCS Dimensions" (1990s, Intersolv), "Dimensions" (early 2000s, Merant), "ChangeMan Dimensions" (2004, [[Serena Software]]) and finally "[[Dimensions CM]]" (since 2007, [[Serena Software]]).
|
|-
! {{Rh}} | [[Fossil (software)|Fossil]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2007|07|21|format=hide}} Fossil and SQLite have used Fossil since 21 July 2007.
|
|-
! {{Rh}} | [[Git]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2005|04|format=hide}} Started by [[Linus Torvalds]] in April 2005, following the [[BitKeeper]] controversy.<ref name=bkcontroversy>[https://www.mercurial-scm.org/wiki/Presentations?action=AttachFile&do=get&target=ols-mercurial.pdf Towards A Better SCM: Revlogs and Mercurial],  presented by Matt Mackall to the Ottawa Linux Symposium, July 2006</ref>
| style="text-align: left; padding-left: 0.5em" | [[Linux kernel]], [[Android (operating system)|Android]], [[OpenJDK]], [[Bugzilla]], [[DragonFly BSD]], [[FreeBSD]], [[GNU compiler collection|gcc]],<ref>{{cite web |url=https://gcc.gnu.org/git.html |title=GCC: Anonymous read-only Git access |access-date=24 October 2023}}</ref> [[GNOME]], [[GNU Emacs]], [[GNU Privacy Guard|GnuPG]],<ref>{{cite web |url=https://www.gnupg.org/faq/HACKING.html |title=A Hacker's Guide to GnuPG |date=11 March 2021 |access-date=24 October 2023}}</ref> [[GRUB2]], [[KDE]], [[MySQL]], [[Perl|Perl 5]],<ref>{{cite web|url=http://dev.perl.org/perl5/source.html |title=Getting and Working With the Perl Source |publisher=dev.perl.org |access-date=2014-01-26}}</ref> [[PostgreSQL]], [[Python (programming language)|Python]],<ref>{{cite web|url=https://devguide.python.org/getting-started/setup-building/ |title=Setup and building |publisher=Python.org |access-date=2023-10-24}}</ref> [[X.Org Server|X.Org]], [[Cairo (graphics)|Cairo]], [[Qt Development Frameworks]], [[Samba software|Samba]], [[OpenEmbedded]], [[Ruby (programming language)|Ruby]], [[Ruby on Rails]], [[Wine (software)|Wine]], [[Fluxbox]], [[Openbox]], [[Compiz Fusion]], [[XCB]], [[Xen]], [[ELinks]], XMMS2, [[e2fsprogs]], [[GNU Core Utilities]], [[DokuWiki]], [[Drupal]], [[LibreOffice]], [[MediaWiki]],<ref>{{cite web|url=http://www.mediawiki.org/wiki/Git|title=Git|publisher=MediaWiki|access-date=1 August 2012}}</ref> [[Mono (software)|Mono]], [[ASP.NET MVC]], [[ADO.NET Entity Framework]], [[NuGet]], [[jQuery]] and many of its plugins, [[OpenCV]], [[Twitter]], [[Netflix]], [[LinkedIn]], [[Wireshark]], [[Django (web framework)|Django]], many companies like [[Eclipse Foundation]], [[Ericsson]], [[Microsoft]],<ref>{{cite web|url= https://blogs.msdn.microsoft.com/bharry/2017/05/24/the-largest-git-repo-on-the-planet/ |title=The largest Git repo on the planet |date= May 24, 2017}}</ref> [[Huawei]], [[Apple Inc.|Apple]], [[Amazon (company)|Amazon]], [[LG]]
|-
! {{Rh}} | [[GNU arch]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2001|format=hide}} Started by Tom Lord in 2001, it later became part of the [[GNU]] project. Lord resigned as maintainer in August 2005.
|
|-
! {{Rh}} | [[IC Manage]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2003|format=hide}} Developed by IC Manage, Inc which was founded in 2003 by Shiv Sikand and Dean Drako.
|
|-
! {{Rh}} | [[PTC Integrity]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2003|format=hide}} Originally developed by MKS Software. Purchased by PTC in May 2011<ref>{{cite web |url=http://www.mks.com/about-MKS/press/press-releases/ptc-sets-new-standard-for-managing-hardware-and-software-development-lifecycles-with-mks-integrity-acquisition |title=PTC Sets New Standard for Managing Hardware and Software Development Lifecycles with MKS Integrity Acquisition – PTC Integrity |publisher=Mks.com |access-date=2014-01-26 |url-status=dead |archive-url=https://web.archive.org/web/20140722103846/http://www.mks.com/about-MKS/press/press-releases/ptc-sets-new-standard-for-managing-hardware-and-software-development-lifecycles-with-mks-integrity-acquisition |archive-date=2014-07-22}}</ref>
|
|-
! {{Rh}} | [[Mercurial]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2005|04|06|format=hide}} Started April 6, 2005 by Matt Mackall, following the [[BitKeeper]] controversy.<ref name=bkcontroversy/> First released on April 19, 2005
| style="text-align: left; padding-left: 0.5em" | [[GNU Multi-Precision Library]], [[GNU Octave]], [[Pidgin (software)|Pidgin]], [[XEmacs]]<ref>{{Citation |contribution-url=https://www.mercurial-scm.org/wiki/ProjectsUsingMercurial |contribution=Some projects that use Mercurial |publisher=Mercurial-scm.org |title=Mercurial |type=wiki}}.</ref>
|-
! {{Rh}} | [[Monotone (software)|Monotone]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2003|04|format=hide}} First released in April 2003
|
|-
! {{Rh}} | [[Perforce#Helix Core|Perforce Helix Core]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1995|format=hide}} Developed by Perforce Software, Inc which was founded in 1995 by Christopher Seiwald.
|
|-
! {{Rh}} | [[Rational Team Concert]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2008|06|format=hide}} Version 1.0 released in June, 2008
|
|-
! {{Rh}} | [[Revision Control System]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1985|07|format=hide}} July 1985
|
|-
! {{Rh}} | [[Source Code Control System]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1972|format=hide}} Started by [[Marc Rochkind]] in 1972 (binary history files, written in Snobol on IBM-370,<ref>{{Citation |last=Rochkind |first=Marc J. |url=http://basepath.com/aup/talks/SCCS-Slideshow.pdf |title=The Source Code Control System |periodical=IEEE Transactions on Software Engineering |volume=SE-1 |issue=4 |date=December 1975 |pages=364–370 |doi=10.1109/tse.1975.6312866 |bibcode=1975ITSEn...1..364R |s2cid=10006076 |access-date=2014-07-31 |archive-date=2011-05-25 |archive-url=https://web.archive.org/web/20110525193926/http://basepath.com/aup/talks/SCCS-Slideshow.pdf |url-status=dead}}</ref> SCCSv4 with text history files was published February 18, 1977.<ref>http://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/usr/news/pibs PWB UNIX product announcement</ref> The same history file format is still used in SCCS 5.0.<ref>Compare [http://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/usr/man/man5/sccsfile.5 the SCCS 4 file format] with the [http://dlc.sun.com/osol/devpro/downloads/current/devpro-sccs-src-20061219.tar.bz2 SCCS 5.0] {{webarchive|url=https://web.archive.org/web/20140819084619/http://dlc.sun.com/osol/devpro/downloads/current/devpro-sccs-src-20061219.tar.bz2 |date=2014-08-19}} file format (as manpage sccsfile(4) in {{cite web |url=http://dlc.sun.com/osol/man/downloads/20070320/man-sunosman-20070320.tar.bz2 |title=Archived copy |access-date=2014-08-17 |url-status=dead |archive-url=https://web.archive.org/web/20140819084236/http://dlc.sun.com/osol/man/downloads/20070320/man-sunosman-20070320.tar.bz2 |archive-date=2014-08-19}}</ref>
|
|-
! {{Rh}} | [[StarTeam]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1995|format=hide}} Version 1.0 1995;<ref>[https://web.archive.org/web/19980507011804/http://demo.starbase.com/WebDraw%2BOld%2BWeb%2BSite/StarTeam/StarTeam.htm Starteam®<!-- Bot generated title -->]</ref> Developed by StarBase software, acquired by Borland(which was acquired by Micro Focus).
|
|-
! {{Rh}} | [[Apache Subversion]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2000|format=hide}} Started in 2000 by [[Concurrent Versions System|CVS]] developers with goal of replacing CVS
|
|-
! {{Rh}} | [[Rational Synergy|Synergy]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1988|format=hide}} Developed beginning in 1988 by Caseware, as AmplifyControl. The company was renamed Continuus in 1994, where the product became better known as Continuus/CM. Continuus was acquired by Telelogic in 1999 shortly after going public; the product was renamed Telelogic Synergy. IBM acquired Telelogic in 2008 for integration into their Rational tool suite. The product is now known as IBM Rational Synergy.
|
|-
! {{Rh}} | [[Vault (version control system)|Vault]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2003|02|format=hide}} First publicly released in February, 2003
| {{Unk}}
|-
! {{Rh}} | [[Vesta (Software configuration management)|Vesta]]
| style="text-align: left; padding-left: 0.5em" | {{dts|2001|format=hide}} First publicly released under the LGPL in 2001
|
|-
! {{Rh}} | [[Microsoft Visual SourceSafe|Visual SourceSafe]]
| style="text-align: left; padding-left: 0.5em" | {{dts|1995|format=hide}} originally created by a company called One Tree Software, version 3.1. Company was bought by Microsoft which released version 4.0 of VSS around 1995
|
|- class="sortbottom"
! Software
! History
! Notable current users
|}

== See also ==
* [[Comparison of source-code-hosting facilities]]
* [[List of version-control software]]

== Notes ==
{{Reflist|group="nb"}}

== References ==
{{Reflist}}

{{Version control software}}

[[Category:Version control systems| ]]
[[Category:Software comparisons|Version control software]]
{{⚠️🚨COPIED from EverybodyWiki ❗❕⚠️😡😤Please respect Licence CC-BY-SA ❗}}
{{Source Wikipedia}}