Comparison of Version Control Software: History
View Latest Version
Please note this is an old version of this entry, which may differ significantly from the current revision.
Subjects: Computer Science, Software Engineering
Contributor:
HandWiki

The following is a comparison of version control software. The following tables include general and technical information on notable version control and software configuration management (SCM) software. For SCM software not suitable for source code, see Comparison of open source configuration management software.

  • configuration management
  • open source
  • scm

1. General Information

Table explanation

  • Repository model describes the relationship between various copies of the source code repository. In a client–server model, users access a master repository via a 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. In a distributed model, repositories act as peers, and users typically have a local repository with version history available, in addition to their working copies.
  • Concurrency model describes how changes to the working copy are managed to prevent simultaneous edits from causing nonsensical data in the repository. In a lock model, changes are disallowed until the user requests and receives an exclusive lock on the file from the master repository. In a merge model, 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 changes on both sides, or let the user decide when conflicts arise. Note that distributed version control almost always implies a merge concurrency model.
Software Maintainer Development status Repository model Concurrency model License Platforms supported Cost
AccuRev SCM Micro Focus International Active Client–server Merge or lock Proprietary Most Java Platforms (Unix-like, Windows, OS X) Non-free Quoted on an individual basis. $350 /seat
GNU Bazaar Canonical Ltd. Active Distributed and Client–server Merge GNU GPL Unix-like, Windows, OS X Free
BitKeeper BitMover Inc. Active Distributed Merge Apache Unix-like, Windows, OS X Free
ClearCase IBM Rational Active Client–server Merge or lock[1] Proprietary Linux, Windows, AIX, Solaris, HP UX, i5/OS, OS/390, z/OS, Non-free $4600 per floating license (held automatically for 30-minutes minimum per user, can be surrendered manually)
Code Co-op Reliable Software Active Distributed Merge Proprietary Windows Non-free $150 per seat
Codeville Ross Cohen official site offline; latest release July 13, 2007 (2007-07-13) Distributed precise codeville merge BSD Unix-like, Windows, OS X Free
CVS The CVS Team[2] maintained but new features not added Client–server Merge GNU GPL Unix-like, Windows, OS X Free
CVSNT March Hare Software[3] and community members maintained and new features under development Client–server Merge or lock GPL or proprietary Unix-like, Windows, OS X, i5/OS Free (with £425 distribution fee) for older version or £85 commercial license for latest version of CVS Suite or Change Management Server
darcs The Darcs team Active Distributed Merge GNU GPL Unix-like, Windows, OS X Free
Dimensions CM Serena Software Active Client–server Merge or lock Proprietary Windows, Linux, Solaris, AIX, HP UX, z/OS Non-free
Endevor CA Technologies[4] Active Client-server Merge or Lock Proprietary z/OS Non-free
Fossil D. Richard Hipp Active Distributed Merge BSD POSIX, Windows, OS X, Other Free
Git Junio Hamano Active Distributed Merge GNU GPL POSIX, Windows, OS X Free
GNU arch Andy Tai unmaintained Distributed Merge GNU GPL Unix-like, Windows, OS X Free
IC Manage IC Manage Inc. Active Client–server Merge or lock Proprietary Unix-like, Windows, OS X Non-free Commercial
PTC Integrity PTC Active Client–server Merge or lock Proprietary Unix-like, Windows Non-free
Mercurial Matt Mackall Active Distributed Merge GNU GPL Unix-like, Windows, OS X Free
Monotone Nathaniel Smith, Graydon Hoare Active Distributed Merge GNU GPL Unix-like, Windows, OS X Free
Perforce Helix Core Perforce Software Inc. Active Client–server and Distributed Merge or lock Proprietary Unix-like, Windows, OS X Available as perpetual license and subscriptions; prices vary based on configurations and options[5]
pijul   Active Distributed Merge GNU GPL Unix-like, Windows, OS X Free
Plastic SCM Codice Software Active Client–server and Distributed control systemDistributed Merge or lock Proprietary Linux, Windows, OS X Free for up to 15 users; else starting at $595 per seat, or $3,500 per 25 developers per year[6]
PVCS Serena Software Active Client–server Lock Proprietary Windows, Unix-like Non-free
Rational Team Concert IBM Rational Active Merge or lock Proprietary Linux, Windows, AIX, Solaris, HP UX, i5/OS, OS/390, z/OS, OS X Free for up to 10 users; else non-free
Revision Control System Thien-Thi Nguyen Active local Merge or lock GNU GPL Unix-like Free
SCM Anywhere Dynamsoft Corporation Active Client–server Merge or Lock Proprietary Unix-like, Windows, OS X Non-free Single user free; $299 per user, bulk discount available
Source Code Control System Jörg Schilling[7] Active local lock[8] CDDL / proprietary[9] Unix-like, Windows, OS X While SCCS has traditionally been bundled in commercial UNIX distributions, free CDDL-licensed versions exist
StarTeam Borland (Micro Focus) Active Client–server Merge or lock Proprietary Windows and Cross-platform via Java based client Non-free Quoted on an individual basis.
Subversion (SVN) Apache Software Foundation[10] Active Client–server[11] Merge or lock[12] Apache Unix-like, Windows, OS X Free
Surround SCM Seapine Software Active Client–server Merge or lock Proprietary Linux, Windows, OS X Non-free $595 per named user; $29/month subscription
SVK Best Practical unmaintained Client–server, decentralized Merge Artistic/GPL Unix-like, Windows, OS X Free
Team Foundation Server (TFS) Microsoft Active Client–server, Distributed Merge or lock Proprietary Windows, cross-platform via Visual Studio Team Services Free for up to 5 users in the Visual Studio Team Services or for open source projects through codeplex.com; else non-free, licensed through MSDN subscription or direct buy.
Synergy IBM Rational Active Client–server and Distributed Merge or lock Proprietary Linux, Windows, Unix-like Non-free Contact IBM Rational[13]
Vault SourceGear LLC Active Client–server Merge or lock Proprietary Unix-like, Linux, Windows Non-free $300 per user
Veracity SourceGear LLC web site appears unmaintained; latest release March 25, 2013 (2013-03-25) Distributed Merge or lock Apache Unix-like, Linux, Windows Free
Vesta Kenneth Schalk; Tim Mann,[14][15] web site not updated since 2006; latest release February 15, 2009 (2009-02-15) Distributed NFS-protocol-emulation choice to optionally confederate clients and/or servers lock on branch; merge branch-to-branch LGPL Tru64, Linux Free
Visual SourceSafe (VSS) Microsoft serious bug fixes only Shared Folder Merge or lock Proprietary Windows Non-free ~$500 per license or single license included with each MSDN subscription.
Visual Studio Team Services Microsoft Active Client–server, Distributed Merge or lock Proprietary Windows, cross-platform via Visual Studio Team Services Free for up to 5 users in the Visual Studio Team Services or for open source projects through codeplex.com; else non-free, licensed through MSDN subscription or direct buy.
Software Maintainer Development status Repository model Concurrency model License Platforms supported Cost

2. Technical Information

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.
  • Revision IDs: are used internally to identify specific versions of files in the repository. Systems may use 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 protocols used for synchronization of changes.
  • Source code size: Gives the size of the source code in megabytes.
Software Programming language Storage method Scope of change Revision IDs Network protocols Source code size
AccuRev SCM C++, Java Changeset File Number pair NN/NN custom Unknown
GNU Bazaar Python 2, Pyrex (optional), C[16] Snapshot Tree Pseudorandom custom, custom over ssh, custom over HTTP, HTTP, SFTP, FTP, email bundles,[17] WebDAV (with plugin) 4.1 MB
BitKeeper C Changeset Tree Changeset keys, numbers custom, HTTP, rsh, ssh, email 99 MB
CA Software Change Manager C, C++, Java, HTML Changeset and Snapshot Numbers HTTP, TCP/IP Unknown
ClearCase C, Java, Perl Changeset File and Tree [18] Numbers custom (CCFS), custom (MVFS filesystem driver), HTTP Unknown
Code Co-op C++ Changeset Unknown User ID-Ordinal e-mail (MAPI, SMTP/POP3, Gmail), LAN Unknown
Codeville Python Unknown Unknown Unknown Unknown Unknown
CVS C Changeset File Numbers pserver, ssh 10.3 MB
CVSNT C++ Changeset File and Tree[19] Numbers custom over ssh, sspi, sserver, gserver, pserver 55 MB
darcs Haskell Changeset (Patch)[20] Tree n/a custom over ssh, HTTP, email 1.7 MB
Dimensions CM C, C++, Java, C# Snapshot or changeset File and Tree Numbers Custom, HTTP/HTTPS Unknown
Fossil C Snapshot or changeset [21] Tree SHA-1 or SHA-3 hashes [22] HTTP/HTTPS, custom over ssh 7.2 MB[23]
Git C, shell scripts, Perl Snapshot Tree SHA-1 hashes custom (git), custom over ssh,[24] HTTP/HTTPS, rsync, email, bundles 23 MB [25]
GNU arch C, shell scripts Changeset Tree Numbers HTTP, WebDAV Unknown
IC Manage C++, C Changeset Unknown Numbers custom Unknown
Mercurial Python, C Changeset Tree Numbers,[26] SHA-1 hashes custom over ssh, HTTP, email bundles (with standard plugin) 20 MB
MKS Integrity C, Java Changeset File Numbers custom, HTTP Unknown
Monotone C++ Hybrid[27] Tree SHA-1 hashes custom (netsync), custom over ssh, file system 4.4 MB
Perforce Helix Core C++, C Changeset Tree Numbers custom Unknown
PVCS C++, C Changeset File Numbers Unknown Unknown
Rational Team Concert Java Changeset Tree Numbers REST services over HTTP/HTTPS Unknown
Revision Control System C Changeset File Numbers File system 5.3 MB
SCM Anywhere C++, Java, C# Changeset File and Tree Numbers SOAP over HTTP or HTTPS Unknown
Source Code Control System C Changeset File Numbers NFS 1.3 MB
StarTeam C++, C, Java Snapshot File and Tree MD5 hashes custom, TCP/IP Unknown
Subversion C Changeset and Snapshot Tree Numbers custom (svn), custom over ssh, HTTP and SSL (using WebDAV) 41 MB
Surround SCM C++ Changeset File and Tree Numbers TCP/IP Unknown
SVK Perl Changeset Tree Numbers Unknown Unknown
Synergy Java Changeset (text), Snapshot(binary) File Numbers custom, custom over ssh, HTTP Unknown
Team Foundation Server C++ and C# Changeset File and Tree Numbers SOAP over HTTP or HTTPS, Ssh Unknown
Vault C# Changeset File and Tree Numbers HTTP, HTTPS Unknown
Veracity C, JavaScript Changeset Tree Numbers, [28] SHA-1, SHA-2 and Skein hashes. HTTP 52 MB
Vesta C++ Snapshot Tree Unknown NFS 15.8 MB
Visual SourceSafe C Snapshot File Numbers SMB, DCOM Unknown
Visual Studio Team Services C++ and C# Changeset File and Tree Numbers SOAP over HTTP or HTTPS, Ssh Unknown
Software Programming language Storage method Scope of change Revision IDs Network protocols Source code size

3. Features

Table explanation

  • Software: The name of the application that is described.
  • 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 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.
  • 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.
  • 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 systems using different character encodings.
  • Supports large repos: Can the system handle repositories of around a gigabyte or larger effectively?
Software Atomic commits File renames Merge file renames Symbolic links Pre-/post-event hooks Signed revisions Merge tracking End of line conversions Tags International support Unicode filename support Supports large repos
AccuRev SCM Yes Yes Partial[29] Yes Yes Yes Yes Yes N/A Yes Yes[30] Yes[31][32]
GNU Bazaar Yes Yes Yes Yes Yes Yes Yes Yes[33] Yes Yes Yes Unknown
BitKeeper Yes Yes Yes Yes Yes Unknown Yes Yes Yes Unknown Unknown Yes
CA Software Change Manager Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Unknown
ClearCase Partial[34] Yes Yes Yes Yes Yes Yes Yes Yes Yes[35] Unknown Yes
Code Co-op Yes Yes Yes No Partial No No No Yes Unknown Unknown Unknown
Codeville Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown Unknown
CVS No No No No Partial No No Yes Yes Unknown No Yes
CVSNT Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes
darcs Yes Yes Yes No[36] Yes Yes N/A[37] No Yes No Yes[38] Unknown
Dimensions CM Yes Yes Yes No Yes Unknown Yes Yes Yes [39] No [40] Yes Yes
Fossil Yes Yes Yes Yes No Yes Yes Yes[41] Yes Yes Yes Unknown
Git Yes Partial[42] Yes Yes Yes Yes[43] Yes Yes Yes Yes Yes[44] Partial[45]
GNU arch Yes Yes Unknown Yes Yes Yes Unknown Unknown Yes Unknown Unknown Unknown
IC Manage Yes Yes No Yes Yes Yes Yes Yes Yes Yes Unknown Unknown
MKS Integrity Yes Yes Yes No Yes Yes[46] Yes[47] Yes Yes Yes Yes Unknown
Mercurial Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes[48] Partial[49] Yes[50]
Monotone Yes Yes Yes No[51] Yes Yes, mandatory Yes Yes Yes Unknown Yes Unknown
Perforce Helix Core Yes Yes[52] Yes[53] Partial[54] Yes No Yes[55] Yes Yes Yes[56] Yes[57] Yes
Rational Team Concert Yes Yes Yes Yes Yes[58] Yes Yes Yes Yes Yes Yes Unknown
Source Code Control System Yes No N/A N/A No No Yes No No Partial[59] Yes Yes
StarTeam Yes[60] Yes Unknown Yes No No Yes Yes Yes Yes Unknown Yes
Subversion Yes Yes[61] Partial[62] Yes Yes No[63] Yes.[64] Yes Partial[65] Yes Yes Yes
Surround SCM Yes Yes Yes Yes Yes Yes Yes Yes Yes[66] Yes Yes Yes
SVK Yes Yes Yes Yes Yes[67] Yes[68] Yes Yes Yes Yes Unknown Unknown
Synergy Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes[69] Yes
Team Foundation Server Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes
Vault Yes Yes Yes No Yes No No Yes Yes Unknown Unknown Unknown
Veracity Yes Yes Yes Yes Yes No Yes Yes Yes No Yes Yes
Vesta Yes Yes Unknown Unknown Yes No No No Yes No Unknown Yes
Visual SourceSafe No No[70] Unknown No Yes No No Unknown Yes Yes Unknown Unknown
Visual Studio Team Services Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes
Software Atomic commits File renames Merge file renames Symbolic links Pre-/post-event hooks Signed revisions Merge tracking End of line conversions Tags International support Unicode filename support Supports large repos

4. Advanced Features

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
Software Keyword expansion Interactive commits External references Partial checkout/clone Permissions Timestamp preservation Custom automatic merge tool Supported formats Shared build cache of derived objects
AccuRev SCM Yes Unknown Yes Yes execution bit only Yes Yes git (bi-dir)[71] No
GNU Bazaar Yes[72] Yes[73] Yes[74] No execution bit only No[75] Yes[76] bzr, subversion,[77] git,[78] hg,[79] any that has a fastexporter No
BitKeeper POSIX and RCS Yes Yes Yes Yes Yes Yes bitkeeper No
CA Software Change Manager No Yes No Yes execution bit only Yes Yes CA Software Change Manager No
ClearCase Yes[80] No No Yes Yes Yes[81] Yes ClearCase Yes
CVS RCS No Yes Yes[82] Partial[83] Yes No cvs No
CVSNT RCS Yes[84] Yes[85] Yes[86] Yes Yes No cvs Yes[87]
darcs No Yes No No[88] Partial[89] No conflicts only darcs No
Dimensions CM Yes No Yes[90] Yes Yes Yes Yes Migration from ClearCase, Subversion, CVS, PVCS, ChangeMan DS Unknown
Fossil No Yes Yes[91] No execution bit only[92] No No fossil (uses sqlite), any that has a fastexporter[93] No
Git No[94] Yes[95] Yes[96] Yes[97] execution bit only No[98] Yes git, cvs, subversion, hg, any that has a fastexporter No
Mercurial Yes[99] Yes[100] Yes[101] Yes[102] execution bit only through (alpha) extension[103] Yes[104] hg, subversion,[105] git,[106] any other format supported by the Convert extension[107] No
Perforce Helix Core Yes[108] No No Yes Yes Yes[108] Yes[108] Perforce No
Rational Team Concert No Yes Yes Yes Yes Unknown Unknown N/A No
Source Code Control System Yes No N/A Yes execution bit only No No
Surround SCM Yes No No Yes No Yes Yes[109] Surround No
SVK Yes Yes[110] Unknown Yes Unknown Unknown Unknown subversion No
Subversion Yes[111] Partial[112] Yes[113] Yes execution bit only Partial[114] Yes[115] subversion No
Team Foundation Server No Yes Unknown Yes Yes Unknown Yes Unknown Unknown
Veracity No No No No Yes Yes Yes git, cvs, subversion, hg, any that has a fastexporter No
Vesta No No Yes via SDL No Unknown Yes No Vesta Yes
Visual SourceSafe Yes Unknown Unknown Yes Yes Unknown Yes Unknown No
Visual Studio Team Services No Yes Unknown Yes Yes Unknown Yes Unknown Unknown
Software Keyword expansion Interactive commits External references Partial checkout/clone Permissions Timestamp preservation Custom automatic merge tool Supported formats Shared build cache of derived objects

5. Basic Commands

Table explanation

  • 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.
  • 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
Software Repository init clone pull push Local branches checkout update lock add remove move copy merge commit revert generate bundle file rebase
AccuRev SCM mkdepot N/A N/A N/A mkstream mkws update anchor add defunct move cp [then] add / incl -s / ln merge keep / promote purge / revert N/A chstream
GNU Bazaar init / init --no-tree[116] / init-repo / init-repo --no-trees[117] branch / branch --no-tree[118] pull push init / branch checkout / checkout --lightweight[119] update N/A add rm mv N/A merge commit revert send rebase[120]
BitKeeper setup clone pull -R push clone co pull Unknown add rm mv cp pull commit undo makepatch collapse
ClearCase init N/A N/A N/A N/A checkout update lock / unlock mkelem rmname mv N/A merge checkin uncheckout / rmver N/A findmerge
CVS init N/A N/A N/A N/A checkout update Unknown add rm N/A N/A update -j commit remove [then] update N/A N/A
CVSNT init N/A N/A N/A N/A checkout update edit add rm rename N/A update -j commit update -C N/A N/A
darcs init clone pull [121] push N/A[122] clone pull[121] Unknown add remove move N/A pull / push record revert send -o[123] rebase
Fossil new / open clone pull push branch / commit --branch clone/open update N/A add rm/del mv/rename N/A merge commit revert Fossil's repository is single sqlite file itself N/A
Git init / init --bare clone / clone --bare fetch push branch checkout pull N/A add rm mv cp [then] git add[124] merge commit revert bundle rebase
Mercurial init clone pull push bookmark[125] update / up / checkout / co pull -u N/A add remove / rm move / mv copy / cp merge commit / ci revert bundle rebase[126]
Monotone init clone pull push N/A checkout update Unknown add drop rename N/A merge commit revert N/A N/A
Perforce Helix Core p4 client && p4 sync p4 sync p4 sync p4 submit Requires migration to recent streams feature edit sync lock / unlock add delete move copy integrate submit revert Unknown N/A
SVK svk depotmap [or] svnadmin create) mirror pull push copy checkout update Unknown add rm mv cp merge commit revert N/A smerge -I
Subversion svnadmin create svnadmin hotcopy [work-around]: svnadmin load [work-around]: svnadmin dump N/A checkout / co update / up lock add delete / del / remove / rm move / mv / rename / ren copy / cp merge commit / ci revert N/A N/A
Surround SCM mkmainline N/A N/A N/A mkbranch checkout get checkout add rm move N/A merge checkin voidcheckout N/A rebase
Team Foundation Server using Git clone using Git get commit shelfset checkout get lock add delete rename using Git merge commit undo using Git get
Veracity repo init clone pull push branch checkout pull -u lock add rm mv N/A merge commit revert N/A N/A
Vesta vcreate vrepl vrepl vrepl N/A vcheckout vadvance vcheckout [… then] vcheckin[127] vrm mv [then] vcheckin[128] cp [then] vcheckin[129] vdiff vcheckin vcheckin -c 0 vmake [or] vesta vadvance
Visual SourceSafe ? Unknown Unknown Unknown N/A Get Latest Get Latest Check Out Add Files Delete ? Unknown ? Check In Undo Check Out Unknown Unknown
Visual Studio Team Services using Git clone using Git get commit shelfset checkout get lock add delete rename using Git merge commit undo using Git get
Software Repository init clone pull push Local branches checkout update lock add remove move copy merge commit revert generate bundle file rebase

6. Advanced Commands

Table explanation

  • 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.
  • 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
Software Command aliases Lock/unlock Shelve/unshelve Rollback Cherry-picking Bisect Incoming/outgoing Grep Record
AccuRev SCM No enable file locking No revert / purge promote No No No Unknown
GNU Bazaar [in '.bazaar/bazaar.conf' file] No shelve/unshelve uncommit merge (non-tracking) bisect (bisect plugin) missing --theirs-only/missing --mine-only grep (grep plugin) No
BitKeeper Unknown Unknown park/unpark undo Unknown bisect changes -R/-L grep Unknown
CVSNT [in '.cvsrc' file] edit -x/unedit[130] No admin -o[131] yes[132] annotate[133] No no[134] No
Darcs No No revert/unrevert unrecord yes[135] test --bisect pull/push --dry-run No record
Fossil No No stash pop/stash apply[136] merge --rollback merge --cherrypick bisect No search No
Git [in '.gitconfig' file] No stash/stash pop[137] reset HEAD^ cherry-pick bisect cherry grep add -p
Mercurial [in '.hgrc' file] No shelve/unshelve (bundled extension[138]) strip (bundled extension[139]) graft(core[140]) or transplant(bundled extension[141]) bisect incoming/outgoing grep record (bundled extension[142])
Monotone [in monotonerc] No No kill_rev_locally[143] pluck bisect No No Unknown
Perforce Helix Core via broker[144] lock/unlock shelve/unshelve obliterate integ[145] Unknown Unknown grep Unknown
SVK No No No No svk merge No status[146] No No
Subversion No lock/unlock shelve/unshelve[147] No svnmerge cherry-picking Third party tool[148] status -u[149] No No
Surround SCM No checkout shelf rollback duplicatechanges No diff search No
Team Foundation Server Yes lock/unlock shelve/unshelve rollback merge No Unknown Unknown No
Veracity No lock/unlock [150] No No No No incoming/outgoing No No
Visual Studio Team Services Yes lock/unlock shelve/unshelve rollback merge No Unknown Unknown No
Software Command aliases Lock/unlock Shelve/unshelve Rollback Cherry-picking Bisect Incoming/outgoing Grep Record

7. User Interfaces

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: functionality is available through an Integrated Development Environment. Minimum functionality should be to list the revision state of a file and check in/check out files.
Software Web interfaces Stand-alone GUIs Integration and/or Plug-ins for IDEs
AccuRev SCM Yes Windows (incl. Explorer integration), Linux, Unix, OS X, BeOS available IntelliJ IDEA, Eclipse, Visual Studio
GNU Bazaar can use a plain webserver Olive, bzr-gtk (GTK+), Bazaar Explorer (Qt), QBzr (Qt), TortoiseBzr (Windows) Eclipse (BzrEclipse, QBzrEclipse), Visual Studio (bzr-visualstudio), TextMate (TextMateBundle), Komodo IDE, WingIDE
BitKeeper included included (bkd) Unknown
CA Software Change Manager included Eclipse-based GUI Eclipse, MS Visual Studio
ClearCase included, Clearcase Web Interface older: MS Windows native, Motif-based GUI for Unix-like systems, TSO client for z/OS. Emacs, Eclipse ( IBM Proprietary, Eclipse-CCase ), Visual Studio (IBM proprietary), KDevelop (standard?), IntelliJ IDEA (standard in Ultimate Edition)
Code Co-op Not necessary since entire project is replicated locally Windows Unknown
CVS cvsweb, ViewVC, others TortoiseCVS, TkCVS (Tcl/Tk), (Windows Explorer), WinCVS, OS X, GTK, Qt available Eclipse (Team), KDevelop (standard), IntelliJ IDEA (standard in Community and Ultimate Editions), Emacs (standard VC), Komodo IDE, BBEdit, WingIDE
CVSNT cvsweb, ViewVC, others Windows, OS X, OS/400, GTK, Qt available All those that support CVS, plus commercial plugins for SCCI, Bugzilla, Build
darcs darcs.cgi included; darcsweb, Trac under development; TortoiseDarcs (Windows Explorer), OS X (alpha), Eclipse (eclipsedarcs), Emacs (vc-darcs.el)
Dimensions CM Yes Windows (incl. explorer integration) Eclipse, Visual Studio, IntelliJ IDEA, XCode, Powerbuilder
Fossil Embedded webserver included (ui/server mode), ability to run multiple repositories via CGI mode fuel-scm Unknown
Git Gitweb, wit, cgit, GitLab, GitHub, gitorious, Trac, Kallithea, Bitbucket, Stash, Springloops, Bonobo Git Server gitk, git-gui (Tcl/Tk), tig, Gitbox (OS X), TortoiseGit, qgit, gitg (GNOME/GTK), (h)gct (Qt), git-cola (Qt), Git Extensions (Windows), GitEye, SmartGit/Hg, Tower, SourceTree (OS X/Windows), Sprout (OS X), GitX (OS X), GitUp (OS X), GitKraken Aptana 3 Beta (Aptana Studio 3 with Git Integration); Eclipse (JGit/EGit); Helix TeamHub; Netbeans (NbGit); KDevelop; Visual Studio (Git Extensions); Emacs (extension for standard VC); SAP Web IDE; TextMate (Git TextMate Bundle); Vim (VCSCommand plugin and fugitive plugin); IntelliJ IDEA >8.1 (standard in Community and Ultimate Editions); Komodo IDE; Anjuta; XCode, WingIDE; PyCharm
GNU arch ArchZoom ArchWay (GTK2), TlaLog Emacs (standard VC)
IC Manage included Windows, Linux, Unix, OS X Emacs, Cadence Design Framework, Synopsys Custom Designer
MKS Integrity 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[151]
Mercurial included,[152] Bitbucket, Trac, Kallithea Hgk (Tcl/Tk), (h)gct (Qt), TortoiseHg (Windows Explorer, Nautilus), MacHg,

MacMercurial, Murky, SourceTree (Windows/OS X), TortoiseHg, SmartGit/Hg

 IntelliJ IDEA (hg4idea 3rd party plugin), Eclipse (Mercurial Eclipse), NetBeans, Visual Studio 2008, Emacs, Vim (VCSCommand plugin), Komodo IDE, Eric Python IDE, WingIDE
Monotone ViewMTN, TracMonotone, Monotone-Viz (GTK+), Guitone (Qt), Monotone Browser (GTK+, Perl) Unknown
Perforce Helix Core included, P4Web, P4FTP Windows, Linux, Mac OS X Eclipse, Visual Studio, Matlab; Game Engines: Unity, Unreal, Amazon Lumberyard; Graphics: Autodesk Maya, 3ds max, Adobe PS
Rational Team Concert Yes Eclipse-based GUI Eclipse integration; MS Visual Studio integration(Limited)
StarTeam included Windows, Java, Eclipse, Visual Studio, BDS2006 integration, plus Java command-line IntelliJ IDEA (standard in Ultimate Edition), Visual Studio, JBuilder, Eclipse
Subversion Apache 2 module included, WebSVN, ViewSVN, ViewVC, Trac, SharpForge, sventon, Springloops Java, KDESVN, OS X[153] (including Finder integration), Nautilus, Qt, RabbitVCS, RapidSVN, SourceTree (OS X), TortoiseSVN (Windows Explorer) Anjuta, BBEdit, Eclipse (Subclipse, Subversive), Emacs (standard VC), IntelliJ IDEA (standard in Community and Ultimate Editions), KDevelop (standard), Komodo IDE, MonoDevelop (standard), Netbeans, RabbitVCS (for GEdit), TextMate (SVNMate plugin), Visual Studio (AnkhSVN, VisualSVN), WingIDE. See also Comparison of Subversion clients
Surround SCM Yes Windows, OS X, Linux Dreamweaver, Eclipse, IntelliJ IDEA, JDeveloper, KDevelop, NetBeans, Powerbuilder, Visual Studio, WebStorm
Synergy via Telelogic Change interface Windows (incl. explorer integration), Linux, Unix Eclipse (Telelogic proprietary), Visual Studio (Telelogic proprietary), IntelliJ IDEA (Telelogic proprietary)
Team Foundation Server included (Sharepoint Server used for web services) Windows included; OS X, Unix available Visual Studio. Java client for Eclipse IDE and IntelliJ IDEA (standard in Ultimate Edition)
Vault included Windows, Unix-like, OS X Visual Studio 2003 and higher, Eclipse 3.2 and higher
Veracity included Tortoise interface for Windows No
Vesta VestaWeb No No
Visual SourceSafe none included; SSWI, VSS Remoting Windows included; Linux, OS X and Solaris using SourceOffSite; any Java VM using Sourceanywhere for VSS Visual Studio, IntelliJ IDEA (standard in Ultimate Edition)
Visual Studio Team Services Yes Windows included; OS X, Unix available Visual Studio. Java client for Eclipse IDE and IntelliJ IDEA (standard in Ultimate Edition)
Software Web interfaces Stand-alone GUIs Integration and/or plug-ins for IDEs

8. History and Adoption

Table explanation

  • Software: The name of the application that is described.
  • History: briefly describes the software's origins and development.
  • Notable 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.
Software History Notable users
AccuRev SCM 2002 First publicly released in 2002 American Airlines, Ford, Lockheed Martin, Orbitz,[154] Xerox, McAfee,[155] Polycom, SanDisk,[156] Siemens, Sony, Symantec,[157] Thomson Financial, Verizon Wireless[158] and many others
GNU Bazaar 2005 Initial release March 26, 2005. Loosely related to baz. Sponsored by Canonical Ltd.. Ubuntu, Launchpad, KatchTV,[159]
BitKeeper 2000 Initial release May 4, 2000. Influenced by Sun WorkShop TeamWare Linux Kernel (2002–2005) and many companies[160]
CA Software Change Manager 1995 Original company founded in 1977; CA SCM (then called CCC/Harvest) first released in 1995. CA does not disclose customer lists without the companies' permission. CA SCM is used by companies with global development teams including 13 of the Fortune 100.
ClearCase 1990 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. IBM, Alcatel-Lucent, Cisco, Motorola, Siemens, Ericsson, Nokia, Society for Worldwide Interbank Financial Telecommunication and other large organizations worldwide
Code Co-op 1997 The first distributed VCS, demoed in 1997,[161] released soon after.  
CVS 1986 First publicly released July 3, 1986; based on RCS NetBSD, OpenBSD
CVSNT 1998 First publicly released 1998; based on CVS. Started by CVS developers with the goal adding support for a wider range of development methods and processes. Primarily professionals (not hobbyists), e.g.: AnandTech,[162] Wachovia,[163] Wells Fargo,[164] Goldman Sachs [165]
darcs 2003 First announced on April 9, 2003 Mnet, xmonad, Projects Using Darcs
Dimensions CM 1989 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). Lockheed Martin, European Space Agency, Fujitsu Business Communication Systems and many companies worldwide[166]
Fossil 2007 Fossil and SQLite have used Fossil since 21 July 2007. SQLite, Tcl/Tk Project
Git 2005 Started by Linus Torvalds in April 2005, following the BitKeeper controversy.[167] Linux kernel, Android, Bugzilla, DragonFly BSD, GNOME, GNU Emacs, GRUB2, KDE, MySQL, Perl 5,[168] PostgreSQL, X.Org, Cairo, Qt Development Frameworks, Samba, OpenEmbedded, Ruby, Ruby on Rails, Wine, Fluxbox, Openbox, Compiz Fusion, XCB, ELinks, XMMS2, e2fsprogs, GNU Core Utilities, DokuWiki, Drupal, LibreOffice, MediaWiki,[169] Mono, ASP.NET MVC, ADO.NET Entity Framework, NuGet, jQuery and many of its plugins, OpenCV, Wireshark, Django, many companies like Ericsson, Microsoft[170], Huawei, Apple, Amazon, LG
GNU arch 2001 Started by Tom Lord in 2001, it later became part of the GNU project. Lord resigned as maintainer in August 2005. available for GNU Savannah and Gna.org projects
IC Manage 2003 Developed by IC Manage, Inc which was founded in 2003 by Shiv Sikand and Dean Drako. many organizations worldwide[171]
PTC Integrity 2003 Originally developed by MKS Software. Purchased by PTC in May 2011[172] Many global engineering and IT organizations[173]
Mercurial 2005 Started April 6, 2005 by Matt Mackall, following the BitKeeper controversy.[167] First released on April 19, 2005 Python,[174] Mozilla, OpenJDK, NetBeans, Xine, Xen, OpenSolaris, wmii, MoinMoin, Linux-HA, Pidgin, Gajim, Nginx, PyPy, SDL, Facebook[175]
Monotone 2003 First released in April 2003 CTWM, Xaraya, I2P,[176] Botan[177][178]
Perforce Helix Core 1993 Developed by Perforce Software, Inc which was founded in 1995 by Christopher Seiwald. FreeBSD,[179] Scania[180]
Rational Team Concert 2008 Version 1.0 released in June, 2008 IBM
Revision Control System 1985 July 1985 RCS is generally (but not always) superseded by other systems such as CVS, which began as a wrapper on top of RCS.
Source Code Control System 1972 Started by Marc Rochkind in 1972 (binary history files, written in Snobol on IBM-370,[181] SCCSv4 with text history files was published February 18, 1977.[182] The same history file format is still used in SCCS 5.0.[183] as the POSIX source-control tool, SCCS is widely available on UNIX platforms, but not included in many Linux distributions. Sun WorkShop TeamWare uses SCCS files.
StarTeam 1995 Version 1.0 1995;[184] Developed by StarBase software, acquired by Borland(which was acquired by Micro Focus). Borland, BT, Cintas, EDS, Kaiser Permanente, Met Office, Quest Software, Raymond James, Siemens, and many more globally distributed companies[185]
Apache Subversion 2000 Started in 2000 by CVS developers with goal of replacing CVS ASF, clang, gcc, SourceForge, FreeBSD, Google Code, KDE (until 2011), PuTTY, Zope, Xiph, GnuPG, CUPS, Apache OpenOffice, TWiki, WebKit, available on CodePlex, and many organizations worldwide[186]
SVK 2003 Authored by Chia-liang Kao with Audrey Tang. First version was on November 19, 2003. 1.00 on May 9, 2005. 2.0.0 on Dec 28th, 2006. SVK became a product of Best Practical on June 5, 2006. Request Tracker
Synergy 1988 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.  
Team Foundation Server 2006 First publicly released in March, 2006  
Vault 2003 First publicly released in February, 2003 Unknown
Vesta 1991 First publicly released under the LGPL in 2001 DEC Alpha team, Compaq Alpha team, Intel microprocessor development
Visual SourceSafe 1995 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 Unknown
Team Services 2006 Release year 2014  
Software History Notable users

The content is sourced from: https://handwiki.org/wiki/Software:Comparison_of_version_control_software

References

  1. 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.
  2. "CVS team member list", Non-GNU Savannah, The GNU Project, http://savannah.nongnu.org/project/memberlist.php?detailed=1&group=cvs 
  3. CVS Pro, March Hare, http://march-hare.com/cvspro/ 
  4. Computer Associates, http://www.ca.com/ 
  5. "How To Buy". https://www.perforce.com/how-buy. Retrieved 2018-01-18. 
  6. Licesing and pricing, PlasticSCM, http://www.plasticscm.com/buy.aspx 
  7. Various forks of the original Unix sources exist, only one of which is actively maintained
  8. 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.
  9. While some forks of SCCS are free software, others remain closed as parts of commercial Unix distributions.
  10. Apache Software Foundation, http://www.apache.org/ 
  11. SVK allows Subversion to have Distributed branches.
  12. 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.
  13. Rational Synergy, IBM, http://www.ibm.com/software/awdtools/synergy 
  14. Vesta Configuration Management System, Sourceforge, http://sourceforge.net/projects/vesta 
  15. Vesta Configuration Management System, Vesta, http://www.vestasys.org 
  16. Bazaar's critical modules are written in Pyrex. They are automatically translated to pure C; except for the patience sorting module, used in merge resolution, which is written directly in the C language.
  17. A Bazaar bundle is a summary diff, with sufficient extra information to preserve history.
  18. IBM – Rational ClearCase – United States, http://www-03.ibm.com/software/products/en/clearcase 
  19. "Changesets". March Hare Software Ltd.. http://march-hare.com/cvsnt/features/changesets/. Retrieved 8 May 2012. 
  20. Snapshots with binary files. It's discussed to have binary changesets in future (darcs 3)
  21. Fossil Technical Overview, http://fossil-scm.org/index.html/doc/trunk/www/tech_overview.wiki 
  22. Fossil Hash Policy, http://fossil-scm.org/index.html/doc/trunk/www/hashpolicy.wiki 
  23. 4 MB of which are sqlite3.c
  24. Git Server Protocol, http://www.samba.org/~jelmer/dulwich/docs/protocol.html 
  25. https://github.com/git/git
  26. Mercurial revision numbers are local to a repository; they can differ from repository to repository depending on in which order merges are performed.
  27. 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.
  28. Veracity revision numbers are local to a repository; they can differ from repository to repository depending on in which order merges are performed.
  29. Evil twins are common.Evil Twins in SCM, Not Hollywood http://accurev.com/blog/2008/01/24/evil-twins-in-scm-not-hollywood/
  30. "Archived copy". Archived from the original on 2011-11-13. https://web.archive.org/web/20111113040629/http://www.accurev.com/download/docs/5.3.0_books/AccuRev_5_3_0_Install_Release_Notes.pdf. Retrieved 2012-01-12. 
  31. "SCM News – Kronos Turns to AccuRev for Software Configuration Management". AccuRev. 2004-04-26. Archived from the original on 2014-02-02. https://web.archive.org/web/20140202091954/http://www.accurev.com/press-releases/20040426-AccuRev-Kronos.html. Retrieved 2014-01-26. 
  32. "Enhanced Performance and Scalability for Cross-Platform Geographically Distributed Teams". AccuRev. 2008-09-23. Archived from the original on 2014-02-02. https://web.archive.org/web/20140202092247/http://www.accurev.com/press-releases/092308-avid-selects-accurev.html. Retrieved 2014-01-26. 
  33. "EOL conversions are supported since bzr 1.14". Doc.bazaar-vcs.org. http://doc.bazaar-vcs.org/bzr.1.14/en/release-notes/NEWS.html#bzr-1-14. Retrieved 2014-01-26. 
  34. Atomic commit can be enabled for individual checkin's ClearCase 7.1.1 release notes. https://publib.boulder.ibm.com/infocenter/cchelp/v7r1m0/index.jsp?topic=/com.ibm.rational.clearcase.relnotes.doc/topics/c_cc_relnotes_features.htm
  35. Support Policy for National Languages and ClearCase from IBM Support http://www.ibm.com/support/docview.wss?uid=swg21229688
  36. See FAQ http://darcs.net/FAQ#can-darcs-handle-symlinks
  37. darcs' patches each bear a unique identifier, impossible to merge twice the same patch in a repository (without destructively modifying history using "unsafe" commands).
  38. Although it stores (and shows by default) 8-bit filename. See FAQ http://darcs.net/FAQ#can-i-version-control-files-with-characters-in-the-full-unicode-spectrum
  39. Using Item Revision Attributes ("Working with Items" demo, covering user define attributes ). http://help.serena.com/doc_center/demos/CM_Essentials_items_1.html
  40. 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.
  41. Controlled by the 'crnl-glob' setting ([1])
  42. 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.
  43. Since git-1.7.9 (see release notes ). Older versions do not sign commits, only tags (see the -s option in git-tag(1) Manual page) http://git.kernel.org/?p=git/git.git;a=blob_plain;f=Documentation/RelNotes/1.7.9.txt;hb=HEAD
  44. UTF-8 filenames are supported as of version 1.7.10 (MSysGit release notes). https://raw.github.com/msysgit/msysgit/f45b8ee0ef75c03c210a476db9184824ffcb33c1/share/WinGit/ReleaseNotes.rtf
  45. Git has some issues with very large repositories. See Section Better big-file support and Section Designing a faster index format in SoC 2012 Ideas. https://github.com/peff/git/wiki/SoC-2012-Ideas
  46. Integrity enabled change packages provide complete workflow and 21 CFR Part 11 compliant digital signatures against the item controlling the change package.
  47. 2009 SP5 added a feature to merge child development paths.
  48. Mercurial includes internationalization for more than 10 languages as of 2017. https://www.mercurial-scm.org/repo/hg/file/3c3066367d72/i18n
  49. Support depends upon host OS and is well supported under Unix, but not Windows OSs, due to lack of host support. See [2]
  50. With the Largefiles Extension in core since Hg Rev.:2.0 (2011), the remotefilelog extension (2014), the fsmonitor extension in core since Hg Rev.:3.8 (2016) and the experimental sparse extension in core since Hg Rev.:4.3 (2017). https://www.mercurial-scm.org/wiki/LargefilesExtension
  51. It could be done via user level hooks
  52. [3] from the Perforce User's Guide
  53. [4] from the Perforce User's Guide
  54. 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.
  55. "Perforce Public Knowledge Base – Home". Perforce.com. http://www.perforce.com/perforce/technotes/note009.html. Retrieved 2014-01-26. 
  56. "Perforce Knowledge Base: Internationalization and Localization". Kb.perforce.com. 2010-10-21. http://kb.perforce.com/?article=66. Retrieved 2014-01-26. 
  57. "Perforce Knowledge Base: Internationalization and Localization". Kb.perforce.com. 2010-10-21. http://kb.perforce.com/article/66/internationalization-and-localization#i18n. Retrieved 2014-01-26. 
  58. Through the process behaviour components: Operation advisors and Operation participants. http://jazz.net/library/article/292
  59. While the source code of SCCS has been written to support internationalisation, only English message texts exist.
  60. StarTeam supports atomic commits as of version 2006
  61. 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 such as svk.
  62. Since SVN 1.8 subversion supports improved move-tracking on the client side. On the server-side it's not supported yet.
  63. "Changeset Signing". Apache Subversion Mailing Lists. http://svn.haxx.se/dev/archive-2015-06/0052.shtml. Retrieved 2016-08-05. 
  64. provides merge tracking for older versions." id="ref_64">New to SVN 1.5 . A separate tool "svnmerge" provides merge tracking for older versions.
  65. 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.
  66. [5] – Seapine Software Releases Surround SCM 2009
  67. Uses subversion server
  68. Signature – SVK Wiki http://svk.bestpractical.com/view/Signature
  69. in Asian releases (v6.6a to v7.1a) and since version 7.2 in general
  70. Version change history is removed upon rename; old name not referenced.
  71. "GitCentric | AccuRevGit for the Enterprise". Accurev.com. Archived from the original on 2012-10-17. https://web.archive.org/web/20121017043025/http://www.accurev.com/kando. Retrieved 2014-01-26. 
  72. "Bazaar keywords plugin". Wiki.bazaar.canonical.com. 2005-09-05. http://wiki.bazaar.canonical.com/KeywordExpansion. Retrieved 2014-01-26. 
  73. "Bazaar interactive plugin". Launchpad.net. https://launchpad.net/bzr-interactive. Retrieved 2014-01-26. 
  74. "Bazaar Externals plugin". Launchpad.net. http://launchpad.net/bzr-externals. Retrieved 2014-01-26. 
  75. not implemented yet https://bugs.launchpad.net/bzr/+bug/245170
  76. "Ignore merge operation for given extension". https://answers.launchpad.net/bzr/+question/103163. 
  77. "bzr-svn". Launchpad.net. http://launchpad.net/bzr-svn. Retrieved 2014-01-26. 
  78. "bzr-git". Launchpad.net. http://launchpad.net/bzr-git. Retrieved 2014-01-26. 
  79. "bzr-hg". Launchpad.net. http://launchpad.net/bzr-hg. Retrieved 2014-01-26. 
  80. IBM Rational ClearCase: The ten best triggers from IBM DeveloperWorks http://www.ibm.com/developerworks/rational/library/4311.html#N10496
  81. Can not be disabled in dynamic views.
  82. Using alias of the CVSROOT/modules file.
  83. CVS records executable bit when a file is added, but does not allow changing it later on.
  84. This is a GUI feature supported by TortoiseCVS and WinCVS both of which include/use CVSNT.
  85. Same as CVS, plus also the ability to have replicated repositories including 'shadow' repositories.
  86. Use the module/directory name or an alias created using CVSROOT/modules or CVSROOT/modules2 administration file.
  87. CVSNT supports this when the make/build tool used also supports it.
  88. Darcs can do sparse checkouts from explicit checkpoints on darcs-1 repositories, but not from darcs-2 ones
  89. Darcs can automatically detect #! scripts and make them executable on checkout.
  90. Using Sub Project functionality (Documentation Portfolio | User's Guide | Relating a Project or Stream to Other Objects). http://help.serena.com/doc_center/doc_center.html#dcm
  91. Checkouts can be nested with "fossil open --nested"
  92. The manifest, Fossil file formats http://www.fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki#manifest
  93. "Fossil import and export". Fossil-scm.org. 2014-01-22. http://www.fossil-scm.org/index.html/doc/trunk/www/inout.wiki. Retrieved 2014-01-26. 
  94. The Git FAQ states that keyword expansion is not a good thing https://git.wiki.kernel.org/index.php/GitFaq#Does_Git_have_keyword_expansion.3F
  95. add -i and add -p, see git-add(1) Manual Page http://www.kernel.org/pub/software/scm/git/docs/git-add.html
  96. "git-submodule(1) Manual Page". Kernel.org. 2013-02-15. http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html. Retrieved 2014-01-26. 
  97. "git-read-tree(1) Manual Page". kernel.org. 2014-08-24. http://git-scm.com/docs/git-read-tree#_sparse_checkout. Retrieved 2014-10-24. 
  98. The Git FAQ explains why preserving modification time is considered harmful https://git.wiki.kernel.org/index.php/GitFaq#Why_isn.27t_Git_preserving_modification_time_on_files.3F
  99. "Mercurial KeywordExtension page". Mercurial-scm.org. https://www.mercurial-scm.org/wiki/KeywordExtension. Retrieved 2014-01-26. 
  100. "Mercurial RecordExtension page". Mercurial-scm.org. 2013-08-27. https://www.mercurial-scm.org/wiki/RecordExtension. Retrieved 2014-01-26. 
  101. "Subrepository – Mercurial". Mercurial-scm.org. https://www.mercurial-scm.org/wiki/Subrepository?action=show&redirect=Subrepositories. Retrieved 2016-04-22. 
  102. With the sparse extension included in core since Hg Rev.:4.3. https://www.mercurial-scm.org/wiki/Release4.3
  103. "Mercurial Timestamp Extension". Mercurial-scm.org. 2012-04-24. https://www.mercurial-scm.org/wiki/TimestampExtension. Retrieved 2014-01-26. 
  104. "Merge Tool Configuration". Mercurial-scm.org. 2017-03-14. https://www.mercurial-scm.org/wiki/MergeToolConfiguration. Retrieved 2017-09-05. 
  105. "hgsubversion page". Mercurial-scm.org. 2013-08-28. https://www.mercurial-scm.org/wiki/HgSubversion. Retrieved 2014-01-26. 
  106. "Hg-Git Mercurial Plugin". Hg-git.github.com. https://hg-git.github.com/. Retrieved 2014-01-26. 
  107. "Mercurial ConvertExtension page". Mercurial-scm.org. 2013-11-29. https://www.mercurial-scm.org/wiki/ConvertExtension. Retrieved 2014-01-26. 
  108. "P4 User's Guide". Perforce. https://www.perforce.com/perforce/doc.current/manuals/p4guide/. Retrieved 19 January 2018. 
  109. Configurable on server as a Project Option and on the client as a User Option.
  110. commit --interactive, see SVK::Command::Commit http://search.cpan.org/dist/SVK/lib/SVK/Command/Commit.pm
  111. "Keyword Substitution". Svnbook.red-bean.com. http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html. Retrieved 2014-01-26. 
  112. Through third-party tools such as Tortoise SVN.
  113. "Externals Definitions". Svnbook.red-bean.com. http://svnbook.red-bean.com/en/1.0/ch07s03.html. Retrieved 2014-01-26. 
  114. 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.
  115. 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
  116. Standalone Branch, http://wiki.bazaar.canonical.com/StandaloneBranch 
  117. Shared Repository, http://wiki.bazaar.canonical.com/SharedRepository 
  118. Standalone Branch, http://wiki.bazaar.canonical.com/StandaloneBranch 
  119. Heavyweight Checkout and Lightweight Checkout, http://wiki.bazaar.canonical.com/Checkout 
  120. rebase plugin
  121. darcs's default pull command is interactive, allowing the user to choose which patches to apply (merge) in realtime
  122. darcs doesn't have named branches, local or not, branching is handled solely through repository cloning
  123. darcs send prepares a bundle of patches, defaults to sending it by mail but can send it to a file instead
  124. copies are detected after the fact, much like renames
  125. Mercurial Bookmarks are similar to local branches. https://www.mercurial-scm.org/wiki/Bookmarks
  126. "Mercurial Rebase Extension". Mercurial-scm.org. 2012-10-25. https://www.mercurial-scm.org/wiki/RebaseExtension. Retrieved 2014-04-23. 
  127. Through any of various means, place (to-be-immutable) file in an immutable directory prior to vcheckin.
  128. mv(1) or link(2) the immutable file from its origin immutable directory to its destination immutable directory prior to vcheckin.
  129. Through any of various means, copy the immutable file from its origin immutable directory to its destination immutable directory prior to vcheckin.
  130. One can also enable this as a central preference in the repository server control panel or configuration file.
  131. Requires administrator privileges. One can 'roll back' a change using 'cvs update –e –j @commitid –j "@
  132. yes – use TortoiseCVS or WinCVS to commit the change to the destination and select which specific files to keep
  133. bisect is also available for cvs which should work with CVSNT
  134. "bug 6463 – enh: search repository". http://customer.march-hare.com/webtools/bugzilla/ttshow_bug.cgi?id=6463&tt=1. Retrieved 8 May 2012. 
  135. 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
  136. fossil stash supports multiple shelves with comments.
  137. git stash is a multi-level shelve, it's possible to shelve several change groups at the same time
  138. "Mercurial Shelve extension page". Mercurial-scm.org. 2013-11-07. https://www.mercurial-scm.org/wiki/ShelveExtension. Retrieved 2014-01-26. 
  139. "Mercurial Strip extension page". Mercurial-scm.org. https://www.mercurial-scm.org/wiki/StripExtension. Retrieved 11 May 2016. 
  140. "graft -core command (since Hg Rev.2.0)". Selenic.com. http://www.selenic.com/mercurial/hg.1.html#graft. Retrieved 2014-01-26. 
  141. "Mercurial Transplant extension page". Mercurial-scm.org. 2012-05-12. https://www.mercurial-scm.org/wiki/TransplantExtension. Retrieved 2014-01-26. 
  142. "Mercurial Record extension page". Mercurial-scm.org. 2013-08-27. https://www.mercurial-scm.org/wiki/RecordExtension. Retrieved 2014-01-26. 
  143. Only works on a local repository and only on revisions without children. The disapprove command might be an alternative.
  144. "The Perforce Broker". Perforce.com. http://www.perforce.com/perforce/r10.2/manuals/p4sag/11_broker.html. Retrieved 2014-01-26. 
  145. "Perforce Knowledge Base: "Cherry Picking" Integrations". Kb.perforce.com. 1990-01-01. http://kb.perforce.com/article/567/. Retrieved 2014-01-26. 
  146. svk status lists differences between working copy and repository, not differences between two repositories
  147. experimental in SVN 1.10 (release notes) https://subversion.apache.org/docs/release-notes/1.10#shelving
  148. SVN Bisect tool svn-bisect http://search.cpan.org/dist/App-SVN-Bisect/bin/svn-bisect
  149. svn status lists differences between working copy and repository, not differences between two repositories
  150. locks are advisory, and can't be enforced on disconnected instances
  151. "Supported Integrations — PTC Integrity". Mks.com. 2012-09-10. Archived from the original on 2012-07-25. https://web.archive.org/web/20120725110643/http://www.mks.com/customer-service/supported-versions-platforms-integrations/supported-integrations. Retrieved 2014-01-26. 
  152. hgweb for single-repository access and hgwebdir for multiple repository access from a single HTTP address
  153. La Chose : web agency and software maker – agence web et développement de logiciels http://www.lachoseinteractive.net/en/community/subversion/svnx/features/
  154. "When SCM meets Web 2.0 – Cool Widget at Orbitz | Software Configuration Management and Agile Software Development". Accurev.com. Archived from the original on 2014-02-02. https://web.archive.org/web/20140202000408/http://accurev.com/blog/2008/04/17/when-scm-meets-web-20-cool-widget-at-orbitz/. Retrieved 2014-01-26. 
  155. "McAfee Web Services Team Saves $500,000 per Year by Adopting". AccuRev. Archived from the original on 2014-02-02. https://web.archive.org/web/20140202092131/http://www.accurev.com/accurev-mcafee-success-story.html. Retrieved 2014-01-26. 
  156. "SanDisk Gains a Competitive Advantage Using AccuRev SCM Software". AccuRev. Archived from the original on 2014-02-02. https://web.archive.org/web/20140202091934/http://www.accurev.com/accurev_sandisk_scm_solution.htm. Retrieved 2014-01-26. 
  157. "Symantec Achieves Significant Gains by Moving to". AccuRev. Archived from the original on 2014-02-02. https://web.archive.org/web/20140202091758/http://www.accurev.com/accurev-symantec-scm-solution.html. Retrieved 2014-01-26. 
  158. "Webinar – How Verizon Wireless Overcame Obstacles to Deliver Software More Quickly". Accurev.com. 2011-06-01. Archived from the original on 2012-11-20. https://web.archive.org/web/20121120173624/http://www.accurev.com/virtualbooth/20110525-verizon-wireless/Verizon052011swf.html. Retrieved 2014-01-26. 
  159. "WhoUsesBzr - wiki.bazaar.canonical.com". Bazaar-vcs.org. 2005-09-21. http://bazaar-vcs.org/WhoUsesBzr. Retrieved 2014-01-26. 
  160. "The Scalable Distributed Software Configuration Management System". BitKeeper. http://www.bitkeeper.com/Customers.html. Retrieved 2014-01-26. 
  161. "Distributed Source Control System". Portal.acm.org. 1997-05-18. http://portal.acm.org/citation.cfm?id=716428&dl=ACM&coll=portal. Retrieved 2014-01-26. 
  162. "How to Set up a Source Control on Windows without spending a dime.". AnandTech. http://www.anandtech.com/print/1578. Retrieved 8 May 2012. 
  163. "Combining a tag which contains all files with a tag which only contains a subset". http://www.cvsnt.org/pipermail/cvsnt/2007-August/029459.html. Retrieved 8 May 2012. 
  164. "Can no no longer connect to CVSNT from unix clients". http://www.cvsnt.org/pipermail/cvsnt/2007-September/029581.html. 
  165. "gserver client errors". http://www.cvsnt.org/pipermail/cvsnt/2009-June/032250.html. Retrieved 8 May 2012. 
  166. Serena Software Customers. http://www.serena.com/index.php/en/company/customers/
  167. Towards A Better SCM: Revlogs and Mercurial, presented by Matt Mackall to the Ottawa Linux Symposium, July 2006 https://www.mercurial-scm.org/wiki/Presentations?action=AttachFile&do=get&target=ols-mercurial.pdf
  168. "Getting and Working With the Perl Source". dev.perl.org. http://dev.perl.org/perl5/source.html. Retrieved 2014-01-26. 
  169. "Git". MediaWiki. http://www.mediawiki.org/wiki/Git. Retrieved 1 August 2012. 
  170. "The largest Git repo on the planet". May 24, 2017. https://blogs.msdn.microsoft.com/bharry/2017/05/24/the-largest-git-repo-on-the-planet/. 
  171. IC Manage: Industrial Strength Data Management http://icmanage.com/customer.html
  172. "PTC Sets New Standard for Managing Hardware and Software Development Lifecycles with MKS Integrity Acquisition — PTC Integrity". Mks.com. Archived from the original on 2017-08-11. https://web.archive.org/web/20170811000000/http://www.mks.com/about-MKS/press/press-releases/ptc-sets-new-standard-for-managing-hardware-and-software-development-lifecycles-with-mks-integrity-acquisition. Retrieved 2014-01-26. 
  173. "Customers — PTC Integrity". Mks.com. Archived from the original on 2017-08-11. https://web.archive.org/web/20170811000000/http://www.mks.com/customers. Retrieved 2014-01-26. 
  174. "transition ongoing". Python.org. https://www.python.org/dev/peps/pep-0374/#decision. Retrieved 2014-01-26. 
  175. "Facebook for Developers (video of presentation)". Facebook.com. 2015-03-27. https://www.facebook.com/FacebookforDevelopers/videos/10152800517193553/. Retrieved 2017-09-05. 
  176. "Getting the I2P code". https://geti2p.net/en/get-involved/guides/new-developers#getting-the-i2p-code. Retrieved 2014-07-03. 
  177. "Accessing Version Control". 2014-05-26. Archived from the original on 2014-07-14. https://web.archive.org/web/20140714124803/http://botan.randombit.net/vcs.html. Retrieved 2014-07-03. 
  178. "ProjectsUsingMonotone". 2011-02-06. http://wiki.monotone.ca/ProjectsUsingMonotone/. Retrieved 2014-07-03. 
  179. "Interactions Between FreeBSD Subversion and Perforce". https://www.freebsd.org/doc/en_US.ISO8859-1/articles/p4-primer/freebsd-cvs-and-p4.html. Retrieved 2018-01-26. 
  180. "Scania: Adopting DevOps for Auto Production". 2016-06-28. https://devops.com/scania-adopting-devops-auto-production/. Retrieved 2018-01-26. 
  181. Rochkind, Marc J. (December 1975), "The Source Code Control System", IEEE Transactions on Software Engineering SE-1 (4): 364–370, doi:10.1109/tse.1975.6312866, http://basepath.com/aup/talks/SCCS-Slideshow.pdf 
  182. http://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/usr/news/pibs PWB UNIX product announcement
  183. Compare the SCCS 4 file format with the SCCS 5.0 file format (as manpage sccsfile(4) in "Archived copy". Archived from the original on 2014-08-19. https://web.archive.org/web/20140819084236/http://dlc.sun.com/osol/man/downloads/20070320/man-sunosman-20070320.tar.bz2. Retrieved 2014-08-17. 
  184. Starteam® https://web.archive.org/web/19980507011804/http://demo.starbase.com/WebDraw%2BOld%2BWeb%2BSite/StarTeam/StarTeam.htm
  185. Customer Profiles http://www.borland.com/us/customers/profiles/view-by-product.jsp
  186. "Archived copy". Archived from the original on 2006-06-13. https://web.archive.org/web/20060613050431/http://subversion.tigris.org/testimonials.html. Retrieved 2006-05-30. 
More
©Text is available under the terms and conditions of the Creative Commons-Attribution ShareAlike (CC BY-SA) license; additional terms may apply. By using this site, you agree to the Terms and Conditions and Privacy Policy.
This entry is offline, you can click here to edit this entry!
ScholarVision Creations
Feedback