Jump to content

Comparison of version-control software

Edit links
From Wikipedia, the free encyclopedia

This is a dynamic list and may never be able to satisfy particular standards for completeness. You can help by adding missing items with reliable sources.

The following tables describe attributes of notable version control and software configuration management (SCM) 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

[edit]

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, 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.
    • 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 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 changes on both sides, or let the user decide when conflicts arise. Distributed version control systems usually use a merge concurrency model.
Software Maintainer Development status Repository model Concurrency model License Supported platforms Financial cost
AccuRev SCM Micro Focus International Active Client–server Merge or lock Proprietary Most Java Platforms (Unix-like, Windows, macOS) $350 per seat, quoted on an individual basis.
Azure DevOps Microsoft Active Client–server, Distributed Merge or lock Proprietary Windows, cross-platform via Azure DevOps Services Free for up to 5 users in the Azure DevOps Services or for open source projects; else at cost, licensed through MSDN subscription or direct buy.
GNU Bazaar Canonical Ltd. last release from 2016, forked as Breezy Distributed and Client–server Merge GPL-2.0-or-later Unix-like, Windows, macOS Free
BitKeeper BitMover Inc. unmaintained; last updated December 29, 2018 Distributed Merge Apache-2.0 Unix-like, Windows, macOS Free
IBM DevOps Code ClearCase IBM Rational Active Client–server Merge or lock[nb 1] Proprietary Linux, Windows, AIX, Solaris, HP UX, IBM i, OS/390, z/OS, $4600 per floating license (held automatically for 30 minutes minimum per user, can be surrendered manually)
Code Co-op Reliable Software Active Distributed Merge MIT Windows $150 per seat
CVS The CVS Team[1] maintained but new features not added; last release from 2008 Client–server Merge GPL-1.0-or-later Unix-like, Windows, macOS Free
CVSNT March Hare Software[2] and community members Active Client–server Merge or lock GPL or proprietary Unix-like, Windows, macOS, IBM i £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 GPL-2.0-or-later Unix-like, Windows, macOS Free
Dat The Dat team Active Distributed Merge BSD-3-Clause Unix-like, Windows, macOS Free
Dimensions CM Serena Software Active Client–server Merge or lock Proprietary Windows, Linux, Solaris, AIX, HP UX, z/OS Paid
Fossil D. Richard Hipp Active Distributed Merge BSD-2-Clause POSIX, Windows, macOS, Other Free
Git Junio Hamano Active Distributed Merge GPL-2.0-only POSIX, Windows, macOS Free
GNU arch Andy Tai unmaintained Distributed Merge GPL Unix-like, Windows, macOS Free
IC Manage IC Manage Inc. Active Client–server Merge or lock Proprietary Unix-like, Windows, macOS Paid
PTC Integrity PTC Active Client–server Merge or lock Proprietary Unix-like, Windows Paid
Mercurial Mercurial Community Active Distributed Merge GPL-2.0-or-later Unix-like, Windows, macOS Free
Monotone Nathaniel Smith, Graydon Hoare Active Distributed Merge GPL-2.0-or-later Unix-like, Windows, macOS Free
Perforce Helix Core Perforce Software Inc. Active Client–server and Distributed Merge or lock Proprietary Unix-like, Windows, macOS Available as perpetual license and subscriptions; prices vary based on configurations and options[3]
Plastic SCM Codice Software Active Client–server and Distributed Merge or lock Proprietary Linux, Windows, macOS 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.[4]
PVCS Serena Software Active Client–server Lock Proprietary Windows, Unix-like Paid
Rational Team Concert IBM Rational Active Client–server[nb 2][5][6] Merge or lock Proprietary Linux, Windows, AIX, Solaris, HP UX, IBM i, OS/390, z/OS, macOS Free for up to 10 users, else paid
Revision Control System Thien-Thi Nguyen Active local Merge or lock GPL-3.0-or-later Unix-like Free
Source Code Control System (SCCS) Jörg Schilling[nb 3] Active local lock[nb 4] CDDL – proprietary[nb 5] Unix-like, macOS Free CDDL-licensed versions or paid in some UNIX distributions.
StarTeam Borland (Micro Focus) Active Client–server Merge or lock Proprietary Windows and Cross-platform via Java based client Paid
Subversion (SVN) Apache Software Foundation[7] Active Client–server Merge or lock[nb 6] Apache-2.0 Unix-like, Windows, macOS Free
Surround SCM Perforce Software Inc. Active Client–server Merge or lock Proprietary Linux, Windows, macOS $595 per user; $29/month subscription
Synergy IBM Rational Active Client–server and Distributed Merge or lock Proprietary Linux, Windows, Unix-like Paid[8]
Vault SourceGear LLC Active Client–server Merge or lock Proprietary Unix-like, Linux, Windows $300 per user
Vesta Kenneth Schalk; Tim Mann,[9][10] 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 $500 per license approximately, or single license included with each MSDN subscription.
Software Maintainer Development status Repository model Concurrency model License Supported platforms Financial cost

Technical information

[edit]

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.
  • 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 Un­known
Azure DevOps C++ and C# Changeset File and Tree Numbers SOAP over HTTP or HTTPS, Ssh Un­known
GNU Bazaar Python 2, Pyrex (optional), C[nb 7] Snapshot Tree Pseudorandom custom, custom over ssh, custom over HTTP, HTTP, SFTP, FTP, email bundles,[nb 8] 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 File and Tree[citation needed] Numbers HTTP, TCP/IP Un­known
IBM DevOps Code ClearCase C, Java, Perl Changeset File and Tree [11] Numbers custom (CCFS), custom (MVFS filesystem driver), HTTP Un­known
Code Co-op C++ Changeset Un­known User ID-Ordinal e-mail (MAPI, SMTP/POP3, Gmail), LAN Un­known
CVS C Changeset File Numbers pserver, ssh 10.3 MB
CVSNT C++ Changeset File and Tree[12] Numbers custom over ssh, sspi, sserver, gserver, pserver 55 MB
darcs Haskell Changeset (Patch)[nb 9] 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 Un­known
Fossil C Snapshot or changeset [13] Tree SHA-1 or SHA-3 hashes [14] HTTP/HTTPS, custom over ssh 7.2 MB[nb 10]
Git C, shell scripts, Perl Snapshot Tree SHA-1 hashes custom (git), custom over ssh,[15] HTTP/HTTPS, rsync, email, bundles 23 MB [16]
GNU arch C, shell scripts Changeset Tree Numbers HTTP, WebDAV Un­known
IC Manage C++, C Changeset Un­known Numbers custom Un­known
Mercurial Python, C Changeset Tree Numbers,[nb 11] SHA-1 hashes custom over ssh, HTTP, email bundles (with standard plugin) 20 MB
MKS Integrity C, Java Changeset File Numbers custom, HTTP Un­known
Monotone C++ Hybrid[nb 12] Tree SHA-1 hashes custom (netsync), custom over ssh, file system 4.4 MB
Perforce Helix Core C++, C Changeset Tree Numbers custom Un­known
PVCS C++, C Changeset File Numbers Un­known Un­known
Rational Team Concert Java Changeset Tree Numbers REST services over HTTP/HTTPS Un­known
Revision Control System C Changeset File Numbers File system 5.3 MB
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 Un­known
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 Un­known
Synergy Java Changeset (text), Snapshot(binary) File Numbers custom, custom over ssh, HTTP Un­known
Vault C# Changeset File and Tree Numbers HTTP, HTTPS Un­known
Vesta C++ Snapshot Tree Un­known NFS 15.8 MB
Visual SourceSafe C Snapshot File Numbers SMB, DCOM Un­known
Software Programming language Storage method Scope of change Revision IDs Network protocols Source code size

Features

[edit]

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.
  • 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[nb 13] Yes Yes Yes Yes Yes — Yes Yes[17] Yes[18][19]
Azure DevOps Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes
GNU Bazaar Yes Yes Yes Yes Yes Yes Yes Yes[20] Yes Yes Yes Un­known
BitKeeper Yes Yes Yes Yes Yes Un­known Yes Yes Yes Un­known Un­known Yes
CA Software Change Manager Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Un­known
IBM DevOps Code ClearCase Partial[nb 14] Yes Yes Yes Yes Yes Yes Yes Yes Yes[21] Un­known Yes
Code Co-op Yes Yes Yes No Partial No No No Yes Un­known Un­known Un­known
CVS No No No No Partial No No Yes Yes Un­known No Yes
CVSNT Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes
darcs Yes Yes Yes No[nb 15] Yes Yes —[nb 16] No Yes No Yes[nb 17] Un­known
Dimensions CM Yes Yes Yes No Yes Un­known Yes Yes Yes [nb 18] No [nb 19] Yes Yes
Fossil Yes Yes Yes Yes Yes[22] Yes Yes Yes[nb 20] Yes Yes Yes Yes[23]
Git Yes Partial[nb 21] Yes Yes Yes Yes[nb 22] Yes Yes Yes Yes Yes[nb 23] Partial[nb 24]
GNU arch Yes Yes Un­known Yes Yes Yes Un­known Un­known Yes Un­known Un­known Un­known
IC Manage Yes Yes No Yes Yes Yes Yes Yes Yes Yes Un­known Un­known
MKS Integrity Yes Yes Yes No Yes Yes[nb 25] Yes[nb 26] Yes Yes Yes Yes Un­known
Mercurial Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes[nb 27] Partial[nb 28] Yes[24]
Monotone Yes Yes Yes No[nb 29] Yes Yes, mandatory Yes Yes Yes Un­known Yes Un­known
Perforce Helix Core Yes Yes[25] Yes[26] Partial[nb 30] Yes No Yes[27] Yes Yes Yes[28] Yes[29] Yes
Rational Team Concert Yes Yes Yes Yes Yes[nb 31] Yes Yes Yes Yes Yes Yes Un­known
Source Code Control System Yes No — — No No Yes No No Partial[nb 32] Yes Yes
StarTeam Yes[nb 33] Yes Un­known Yes No No Yes Yes Yes Yes Un­known Yes
Subversion Yes Yes[nb 34] Partial[nb 35] Yes Yes No[nb 36] Yes.[nb 37] Yes Partial[nb 38] Yes Yes Yes
Surround SCM Yes Yes Yes Yes Yes Yes Yes Yes Yes[30] Yes Yes Yes
Synergy Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes[nb 39] Yes
Vault Yes Yes Yes No Yes No No Yes Yes Un­known Un­known Un­known
Vesta Yes Yes Un­known Un­known Yes No No No Yes No Un­known Yes
Visual SourceSafe No No[nb 40] Un­known No Yes No No Un­known Yes Yes Un­known Un­known
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

Advanced features

[edit]

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
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 Un­known Yes Yes execution bit only Yes Yes git (bi-dir)[31] No
Azure DevOps No Yes Un­known Yes Yes Un­known Yes Un­known Un­known
GNU Bazaar Yes[32] Yes[33] Yes[34] No execution bit only No[nb 41] Yes[35] bzr, subversion,[36] git,[37] hg,[38] 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
IBM DevOps Code ClearCase Yes[39] No No Yes Yes Yes[nb 42] Yes ClearCase Yes
CVS RCS No Yes Yes[nb 43] Partial[nb 44] Yes No cvs No
CVSNT RCS Yes[nb 45] Yes[nb 46] Yes[nb 47] Yes Yes No cvs Yes[nb 48]
darcs No Yes No No[nb 49] Partial[nb 50] No conflicts only darcs No
Dimensions CM Yes No Yes[nb 51] Yes Yes Yes Yes Migration from ClearCase, Subversion, CVS, PVCS, ChangeMan DS Un­known
Fossil No Yes Yes[nb 52] No execution bit only[40] No No fossil (uses sqlite), any that has a fastexporter;[41] migration from git and svn[42] No
Git No[nb 53] Yes[nb 54] Yes[43] Yes[44] execution bit only No[nb 55] Yes git, cvs, subversion, hg, any that has a fastexporter No
Mercurial Yes[45] Yes[46] Yes[47] Yes[48] execution bit only through (alpha) extension[49] Yes[50] hg, subversion,[51] lossless two-way push to and pull from git,[52] migration from any other format supported by the Convert extension:[53] CVS, Darcs, Bazaar, Monotone, GNU Arch, and Perforce[54] No
Perforce Helix Core Yes[55] No No Yes Yes Yes[55] Yes[55] Perforce No
Rational Team Concert No Yes Yes Yes Yes Un­known Yes N/A No
Source Code Control System Yes No — Yes execution bit only some variants[citation needed] No sccs No
Surround SCM Yes No No Yes No Yes Yes[nb 56] Surround No
Subversion Yes[56] Partial[nb 57] Yes[57] Yes execution bit only Partial[nb 58] Yes[nb 59] subversion No
Vesta No No Yes via SDL No Un­known Yes No Vesta Yes
Visual SourceSafe Yes Un­known Un­known Yes Yes Un­known Yes Un­known No
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

Basic commands

[edit]

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.
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
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 init – init –no-tree[nb 60] – init-repo – init-repo –no-trees[nb 61] branch – branch –no-tree[nb 62] pull push init – branch checkout – checkout –lightweight[nb 63] update N/A add rm mv N/A merge commit revert send rebase[nb 64]
BitKeeper setup clone pull -R push clone co pull Un­known add rm mv cp pull commit undo makepatch collapse
IBM DevOps Code 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 Un­known 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 [58] push N/A[nb 65] clone pull[58] Un­known add remove move N/A pull – push record revert send -o[nb 66] 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[nb 67] merge commit reset –hard bundle rebase
Mercurial init clone pull push bookmark[nb 68] update – up – checkout – co pull -u N/A add remove – rm move – mv copy – cp merge commit – ci revert bundle rebase[59]
Monotone init clone pull push N/A checkout update Un­known 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 Un­known N/A
Source Code Control System create N/A N/A N/A admin -fb get (readonly) – edit get (readonly) – edit N/A[nb 69] create N/A N/A N/A edit -i delta get -r N/A edit -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
Vesta vcreate vrepl vrepl vrepl N/A vcheckout vadvance vcheckout [… then] vcheckin[nb 70] vrm mv [then] vcheckin[nb 71] cp [then] vcheckin[nb 72] vdiff vcheckin vcheckin -c 0 vmake [or] vesta vadvance
Visual SourceSafe ? Un­known Un­known Un­known N/A Get Latest Get Latest Check Out Add Files Delete ? Un­known ? Check In Undo Check Out Un­known Un­known
Software Repository init clone pull push Local branches checkout update lock add remove move copy merge commit revert generate bundle file rebase

Advanced commands

[edit]

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.
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 Un­known
Azure DevOps Yes lock/unlock shelve/unshelve rollback merge No Un­known Un­known No
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 Un­known Un­known park/unpark undo Un­known bisect changes -R/-L grep Un­known
CVSNT [in '.cvsrc' file] edit -x/unedit[nb 73] No admin -o[nb 74] yes[nb 75] annotate[nb 76] No no[60] No
Darcs No No revert/unrevert unrecord yes[nb 77] test –bisect pull/push –dry-run No record
Fossil No No stash pop/stash apply[nb 78] merge –rollback merge –cherrypick bisect No search No
Git [in '.gitconfig' file] No stash/stash pop[nb 79] reset HEAD^ cherry-pick bisect cherry grep add -p
Mercurial [in '.hgrc' file] No shelve/unshelve (bundled extension[61]) strip (bundled extension[62]) graft(core[63]) or transplant(bundled extension[64]) bisect incoming/outgoing grep commit –interactive
Monotone [in monotonerc] No No kill_rev_locally[nb 80] pluck bisect No No Un­known
Perforce Helix Core via broker[65] lock/unlock shelve/unshelve obliterate integ[66] Un­known interchanges grep Un­known
Subversion No lock/unlock shelve/unshelve[nb 81] No svnmerge cherry-picking Third party tool[nb 82] status -u[nb 83] No No
Surround SCM No checkout shelf rollback duplicatechanges No diff search No
Software Command aliases Lock/unlock Shelve/unshelve Rollback Cherry-picking Bisect Incoming/outgoing Grep Record

User interfaces

[edit]

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.
Software Web interfaces Stand-alone GUIs Integration and/or Plug-ins for IDEs
AccuRev SCM Yes Windows (incl. Explorer integration), Linux, Unix, macOS, BeOS available IntelliJ IDEA, Eclipse, Visual Studio
Azure DevOps 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)
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, Wing IDE
BitKeeper included included (bkd) Un­known
CA Software Change Manager included Eclipse-based GUI Eclipse, MS Visual Studio
IBM DevOps Code 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 Un­known
CVS cvsweb, ViewVC, others TortoiseCVS (Windows Explorer), TkCVS (Tcl/Tk), WinCVS, macOS, GTK, Qt available Eclipse (Team), KDevelop (standard), IntelliJ IDEA (standard in Community and Ultimate Editions), Emacs (standard VC), Komodo IDE, BBEdit, Wing IDE
CVSNT cvsweb, ViewVC, others Windows, macOS, 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), macOS (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 Un­known
Git Gitweb, wit, cgit, GitLab, GitHub, gitorious, Trac, Kallithea, Bitbucket, Stash, Springloops, Bonobo Git Server, Gitea, Gogs gitk, git-gui (Tcl/Tk), tig, Gitbox (macOS), TortoiseGit, qgit, gitg (GNOME/GTK), (h)gct (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; 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, Wing IDE; PyCharm
GNU arch ArchZoom ArchWay (GTK2), TlaLog Emacs (standard VC)
IC Manage included Windows, Linux, Unix, macOS 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[67]
Mercurial included,[nb 84] Trac, Kallithea Hgk (Tcl/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), Komodo IDE, Eric Python IDE, Wing IDE
Monotone ViewMTN, TracMonotone, Monotone-Viz (GTK+), Guitone (Qt), Monotone Browser (GTK+, Perl) Un­known
Perforce Helix Core included, P4Web, P4FTP Windows, Linux, Mac macOS 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, macOS[68] (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), Komodo IDE, MonoDevelop (standard), Netbeans, RabbitVCS (for GEdit), TextMate (SVNMate plugin), Visual Studio (AnkhSVN, VisualSVN), Wing IDE. See also Comparison of Subversion clients
Surround SCM Yes Windows, macOS, Linux Eclipse, IntelliJ IDEA, JDeveloper, NetBeans, 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)
Vault included Windows, Unix-like, macOS Visual Studio 2003 and higher, Eclipse 3.2 and higher
Vesta VestaWeb No No
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)
Software Web interfaces Stand-alone GUIs Integration and/or plug-ins for IDEs

History and adoption

[edit]

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.
Software History Notable current users
AccuRev SCM First publicly released in 2002
Azure DevOps Server First publicly released in March, 2006 as Visual Studio Team System, renamed to Team Foundation Server in 2010 and Azure DevOps Server in 2019. Microsoft
Azure DevOps Services 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. Microsoft
GNU Bazaar Initial release March 26, 2005. Loosely related to baz. Sponsored by Canonical Ltd.
BitKeeper Initial release May 4, 2000. Influenced by Sun WorkShop TeamWare
CA Software Change Manager Original company founded in 1977; CA SCM (then called CCC/Harvest) first released in 1995.
IBM DevOps Code ClearCase 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.
Code Co-op The first distributed VCS, demoed in 1997,[69] released soon after.
CVS First publicly released July 3, 1986; based on RCS NetBSD, OpenBSD
CVSNT 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.
darcs First announced on April 9, 2003
Dimensions CM 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).
Fossil Fossil and SQLite have used Fossil since 21 July 2007.
Git Started by Linus Torvalds in April 2005, following the BitKeeper controversy.[70] Linux kernel, Android, OpenJDK, Bugzilla, DragonFly BSD, FreeBSD, gcc,[71] GNOME, GNU Emacs, GnuPG,[72] GRUB2, KDE, MySQL, Perl 5,[73] PostgreSQL, Python,[74] X.Org, Cairo, Qt Development Frameworks, Samba, OpenEmbedded, Ruby, Ruby on Rails, Wine, Fluxbox, Openbox, Compiz Fusion, XCB, Xen, ELinks, XMMS2, e2fsprogs, GNU Core Utilities, DokuWiki, Drupal, LibreOffice, MediaWiki,[75] Mono, ASP.NET MVC, ADO.NET Entity Framework, NuGet, jQuery and many of its plugins, OpenCV, Twitter, Netflix, LinkedIn, Wireshark, Django, many companies like Eclipse Foundation, Ericsson, Microsoft,[76] Huawei, Apple, Amazon, LG
GNU arch Started by Tom Lord in 2001, it later became part of the GNU project. Lord resigned as maintainer in August 2005.
IC Manage Developed by IC Manage, Inc which was founded in 2003 by Shiv Sikand and Dean Drako.
PTC Integrity Originally developed by MKS Software. Purchased by PTC in May 2011[77]
Mercurial Started April 6, 2005 by Matt Mackall, following the BitKeeper controversy.[70] First released on April 19, 2005
Monotone First released in April 2003
Perforce Helix Core Developed by Perforce Software, Inc which was founded in 1995 by Christopher Seiwald.
Rational Team Concert Version 1.0 released in June, 2008
Revision Control System July 1985
Source Code Control System Started by Marc Rochkind in 1972 (binary history files, written in Snobol on IBM-370,[78] SCCSv4 with text history files was published February 18, 1977.[79] The same history file format is still used in SCCS 5.0.[80]
StarTeam Version 1.0 1995;[81] Developed by StarBase software, acquired by Borland(which was acquired by Micro Focus).
Apache Subversion Started in 2000 by CVS developers with goal of replacing CVS
Synergy 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.
Vault First publicly released in February, 2003 Un­known
Vesta First publicly released under the LGPL in 2001
Visual SourceSafe 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
Software History Notable current users

See also

[edit]

Notes

[edit]
  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. ^ RTC is not a distributed revision control system; but has some distributed feature that can be configured
  3. ^ Various forks of the original Unix sources exist, only one of which is actively maintained
  4. ^ 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.
  5. ^ While some forks of SCCS are free software, others remain closed as parts of commercial Unix distributions.
  6. ^ 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.
  7. ^ 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.
  8. ^ A Bazaar bundle is a summary diff, with sufficient extra information to preserve history.
  9. ^ Snapshots with binary files. It's discussed to have binary changesets in future (darcs 3)
  10. ^ 4 MB of which are sqlite3.c
  11. ^ Mercurial revision numbers are local to a repository; they can differ from repository to repository depending on in which order merges are performed.
  12. ^ 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.
  13. ^ Evil twins are common.Evil Twins in SCM, Not Hollywood Archived 2013-10-16 at the Wayback Machine
  14. ^ Atomic commit can be enabled for individual checkin's ClearCase 7.1.1 release notes.
  15. ^ See FAQ
  16. ^ darcs' patches each bear a unique identifier, impossible to merge twice the same patch in a repository (without destructively modifying history using "unsafe" commands).
  17. ^ Although it stores (and shows by default) 8-bit filename. See FAQ
  18. ^ Using Item Revision Attributes ("Working with Items" demo, covering user define attributes Archived 2016-03-04 at the Wayback Machine).
  19. ^ 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.
  20. ^ Controlled by the 'crnl-glob' setting ([1])
  21. ^ 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.
  22. ^ Since git-1.7.9 (see release notes Archived 2013-04-15 at archive.today). Older versions do not sign commits, only tags (see the -s option in git-tag(1) Manual page)
  23. ^ UTF-8 filenames are supported as of version 1.7.10 (MSysGit release notes).
  24. ^ 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.
  25. ^ Integrity enabled change packages provide complete workflow and 21 CFR Part 11 compliant digital signatures against the item controlling the change package.
  26. ^ 2009 SP5 added a feature to merge child development paths.
  27. ^ Mercurial includes internationalization for more than 10 languages as of 2017.
  28. ^ Support depends upon host OS and is well supported under Unix, but not Windows OSs, due to lack of host support. See [2]
  29. ^ It could be done via user level hooks
  30. ^ 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.
  31. ^ Through the process behaviour components: Operation advisors and Operation participants. http://jazz.net/library/article/292
  32. ^ While the source code of SCCS has been written to support internationalisation, only English message texts exist.
  33. ^ StarTeam supports atomic commits as of version 2006
  34. ^ 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.
  35. ^ Since SVN 1.8 subversion supports improved move-tracking on the client side. On the server-side it's not supported yet.
  36. ^ "Changeset Signing". Apache Subversion Mailing Lists. Retrieved 2016-08-05.
  37. ^ New to SVN 1.5 <http://subversion.apache.org/docs/release-notes/1.5.html#merge-tracking>. A separate tool "svnmerge" <[3]> provides merge tracking for older versions.
  38. ^ 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.
  39. ^ in Asian releases (v6.6a to v7.1a) and since version 7.2 in general
  40. ^ Version change history is removed upon rename; old name not referenced.
  41. ^ not implemented yet
  42. ^ Can not be disabled in dynamic views.
  43. ^ Using alias of the CVSROOT/modules file.
  44. ^ CVS records executable bit when a file is added, but does not allow changing it later on.
  45. ^ This is a GUI feature supported by TortoiseCVS and WinCVS both of which include/use CVSNT.
  46. ^ Same as CVS, plus also the ability to have replicated repositories including 'shadow' repositories.
  47. ^ Use the module/directory name or an alias created using CVSROOT/modules or CVSROOT/modules2 administration file.
  48. ^ CVSNT supports this when the make/build tool used also supports it.
  49. ^ Darcs can do sparse checkouts from explicit checkpoints on darcs-1 repositories, but not from darcs-2 ones[citation needed]
  50. ^ Darcs can automatically detect #! scripts and make them executable on checkout.
  51. ^ Using Sub Project functionality (Documentation Portfolio | User's Guide | Relating a Project or Stream to Other Objects).
  52. ^ Checkouts can be nested with "fossil open –nested"
  53. ^ The Git FAQ states that keyword expansion is not a good thing
  54. ^ add -i and add -p, see git-add(1) Manual Page
  55. ^ The Git FAQ explains why preserving modification time is considered harmful
  56. ^ Configurable on server as a Project Option and on the client as a User Option.
  57. ^ Through third-party tools such as Tortoise SVN.
  58. ^ 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.
  59. ^ 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
  60. ^ Standalone Branch, archived from the original on 2016-03-04, retrieved 2014-11-06
  61. ^ Shared Repository, archived from the original on 2016-03-04, retrieved 2014-11-06
  62. ^ Standalone Branch, archived from the original on 2016-03-04, retrieved 2014-11-06
  63. ^ Heavyweight Checkout and Lightweight Checkout, archived from the original on 2016-06-30, retrieved 2014-11-06
  64. ^ rebase plugin
  65. ^ darcs doesn't have named branches, local or not, branching is handled solely through repository cloning
  66. ^ darcs send prepares a bundle of patches, defaults to sending it by mail but can send it to a file instead
  67. ^ copies are detected after the fact, much like renames
  68. ^ Mercurial Bookmarks are similar to local branches.
  69. ^ SCCS has implicit locks, applied when checking out via edit, removed when creating a delta.
  70. ^ Through any of various means, place (to-be-immutable) file in an immutable directory prior to vcheckin.
  71. ^ mv(1) or link(2) the immutable file from its origin immutable directory to its destination immutable directory prior to vcheckin.
  72. ^ Through any of various means, copy the immutable file from its origin immutable directory to its destination immutable directory prior to vcheckin.
  73. ^ One can also enable this as a central preference in the repository server control panel or configuration file.
  74. ^ Requires administrator privileges. One can 'roll back' a change using 'cvs update –e –j @commitid –j "@<commitid"' but the change and rollback evidence remain in the history.
  75. ^ yes – use TortoiseCVS or WinCVS to commit the change to the destination and select which specific files to keep
  76. ^ bisect is also available for cvs which should work with CVSNT
  77. ^ 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
  78. ^ fossil stash supports multiple shelves with comments.
  79. ^ git stash is a multi-level shelve, it's possible to shelve several change groups at the same time
  80. ^ Only works on a local repository and only on revisions without children. The disapprove command might be an alternative.
  81. ^ experimental in SVN 1.10 (release notes)
  82. ^ SVN Bisect tool svn-bisect
  83. ^ svn status lists differences between working copy and repository, not differences between two repositories
  84. ^ hgweb for single-repository access and hgwebdir for multiple repository access from a single HTTP address

References

[edit]
  1. ^ "CVS team member list", Non-GNU Savannah, The GNU Project
  2. ^ CVS Pro, March Hare
  3. ^ "How To Buy". perforce.com. Retrieved 2018-01-18.
  4. ^ Licesing and pricing, PlasticSCM
  5. ^ "What is a distributed version control system". GitLab.
  6. ^ Jean-Michel Lemieux, Countdown to the next Rational Team Concert: Part II – Source control enhancements, Jazz Community, archived from the original on 2015-09-10, retrieved 2010-12-28
  7. ^ Apache Software Foundation
  8. ^ Rational Synergy, IBM, 9 November 2020
  9. ^ Vesta Configuration Management System, Sourceforge, 5 June 2013
  10. ^ Vesta Configuration Management System, Vesta
  11. ^ IBM – Rational ClearCase – United States, 9 November 2020, archived from the original on November 11, 2013
  12. ^ "Changesets". March Hare Software Ltd. Retrieved 8 May 2012.
  13. ^ Fossil Technical Overview
  14. ^ Fossil Hash Policy
  15. ^ Git Server Protocol
  16. ^ "Git - fast, scalable, distributed revision control system". GitHub. 2 November 2021.
  17. ^ "Archived copy" (PDF). Archived from the original (PDF) on 2011-11-13. Retrieved 2012-01-12.{{cite web}}: CS1 maint: archived copy as title (link)
  18. ^ "SCM News – Kronos Turns to AccuRev for Software Configuration Management". AccuRev. 2004-04-26. Archived from the original on 2014-02-02. Retrieved 2014-01-26.
  19. ^ "Enhanced Performance and Scalability for Cross-Platform Geographically Distributed Teams". AccuRev. 2008-09-23. Archived from the original on 2014-02-02. Retrieved 2014-01-26.
  20. ^ "EOL conversions are supported since bzr 1.14". Doc.bazaar-vcs.org. Archived from the original on 2009-04-13. Retrieved 2014-01-26.
  21. ^ Support Policy for National Languages and ClearCase from IBM Support
  22. ^ https://fossil-scm.org/home/doc/tip/www/hooks.md
  23. ^ https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki#scale
  24. ^ 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).
  25. ^ [4] Archived 2014-02-10 at the Wayback Machine from the Perforce User's Guide
  26. ^ [5] Archived 2014-02-09 at the Wayback Machine from the Perforce User's Guide
  27. ^ "Perforce Public Knowledge Base – Home". Perforce.com. Archived from the original on 2007-08-14. Retrieved 2014-01-26.
  28. ^ "Perforce Knowledge Base: Internationalization and Localization". Kb.perforce.com. 2010-10-21. Archived from the original on 2012-02-08. Retrieved 2014-01-26.
  29. ^ "Perforce Knowledge Base: Internationalization and Localization". Kb.perforce.com. 2010-10-21. Archived from the original on 2013-01-30. Retrieved 2014-01-26.
  30. ^ [6] – Seapine Software Releases Surround SCM 2009
  31. ^ "GitCentric | AccuRevGit for the Enterprise". Accurev.com. Archived from the original on 2012-10-17. Retrieved 2014-01-26.
  32. ^ "Bazaar keywords plugin". Wiki.bazaar.canonical.com. 2005-09-05. Archived from the original on 2014-02-01. Retrieved 2014-01-26.
  33. ^ "Bazaar interactive plugin". Launchpad.net. 7 March 2008. Retrieved 2014-01-26.
  34. ^ "Bazaar Externals plugin". Launchpad.net. 9 November 2009. Retrieved 2014-01-26.
  35. ^ "Ignore merge operation for given extension". 4 March 2010.
  36. ^ "bzr-svn". Launchpad.net. 8 May 2006. Retrieved 2014-01-26.
  37. ^ "bzr-git". Launchpad.net. 15 July 2006. Retrieved 2014-01-26.
  38. ^ "bzr-hg". Launchpad.net. 13 June 2006. Retrieved 2014-01-26.
  39. ^ IBM Rational ClearCase: The ten best triggers from IBM DeveloperWorks
  40. ^ The manifest, Fossil file formats
  41. ^ "Fossil import and export". Fossil-scm.org. 2014-01-22. Archived from the original on 2014-02-02. Retrieved 2014-01-26.
  42. ^ "FossilHelp: import"
  43. ^ "git-submodule(1) Manual Page". Kernel.org. 2013-02-15. Retrieved 2014-01-26.
  44. ^ "git-read-tree(1) Manual Page". kernel.org. 2014-08-24. Retrieved 2014-10-24.
  45. ^ "Mercurial KeywordExtension page". Mercurial-scm.org. Retrieved 2014-01-26.
  46. ^ "Mercurial RecordExtension page". Mercurial-scm.org. 2013-08-27. Retrieved 2014-01-26.
  47. ^ "Subrepository – Mercurial". Mercurial-scm.org. Retrieved 2016-04-22.
  48. ^ With the sparse extension included in core since Hg Rev.:4.3.
  49. ^ "Mercurial Timestamp Extension". Mercurial-scm.org. 2012-04-24. Retrieved 2014-01-26.
  50. ^ "Merge Tool Configuration". Mercurial-scm.org. 2017-03-14. Retrieved 2017-09-05.
  51. ^ "hgsubversion page". Mercurial-scm.org. 2013-08-28. Retrieved 2014-01-26.
  52. ^ "Hg-Git Mercurial Plugin". Hg-git.github.com. Retrieved 2014-01-26.
  53. ^ "Mercurial ConvertExtension page". Mercurial-scm.org. 2013-11-29. Retrieved 2014-01-26.
  54. ^ "Mercurial: the definitive guide: Appendix: Migrating to Mercurial"
  55. ^ a b c "P4 User's Guide". Perforce. Retrieved 19 January 2018.
  56. ^ "Keyword Substitution". Svnbook.red-bean.com. Retrieved 2014-01-26.
  57. ^ "Externals Definitions". Svnbook.red-bean.com. Retrieved 2014-01-26.
  58. ^ a b darcs's default pull command is interactive, allowing the user to choose which patches to apply (merge) in realtime
  59. ^ "Mercurial Rebase Extension". Mercurial-scm.org. 2012-10-25. Retrieved 2014-04-23.
  60. ^ "bug 6463 – enh: search repository". Retrieved 8 May 2012.
  61. ^ "Mercurial Shelve extension page". Mercurial-scm.org. 2013-11-07. Retrieved 2014-01-26.
  62. ^ "Mercurial Strip extension page". Mercurial-scm.org. Retrieved 11 May 2016.
  63. ^ "graft -core command (since Hg Rev.2.0)". Selenic.com. Retrieved 2014-01-26.
  64. ^ "Mercurial Transplant extension page". Mercurial-scm.org. 2012-05-12. Retrieved 2014-01-26.
  65. ^ "The Perforce Broker". Perforce.com. Archived from the original on 2013-11-16. Retrieved 2014-01-26.
  66. ^ "Perforce Knowledge Base: "Cherry Picking" Integrations". Kb.perforce.com. 1990-01-01. Archived from the original on 2012-03-09. Retrieved 2014-01-26.
  67. ^ "Supported Integrations – PTC Integrity". Mks.com. 2012-09-10. Archived from the original on 2012-07-25. Retrieved 2014-01-26.
  68. ^ "La Chose : web agency and software maker – agence web et développement de logiciels". Archived from the original on 2016-06-18. Retrieved 2006-09-20.
  69. ^ Distributed Source Control System. Portal.acm.org. 1997-05-18. pp. 98–107. ISBN 9783540630142. Retrieved 2014-01-26.
  70. ^ a b Towards A Better SCM: Revlogs and Mercurial, presented by Matt Mackall to the Ottawa Linux Symposium, July 2006
  71. ^ "GCC: Anonymous read-only Git access". Retrieved 24 October 2023.
  72. ^ "A Hacker's Guide to GnuPG". 11 March 2021. Retrieved 24 October 2023.
  73. ^ "Getting and Working With the Perl Source". dev.perl.org. Retrieved 2014-01-26.
  74. ^ "Setup and building". Python.org. Retrieved 2023-10-24.
  75. ^ "Git". MediaWiki. Retrieved 1 August 2012.
  76. ^ "The largest Git repo on the planet". May 24, 2017.
  77. ^ "PTC Sets New Standard for Managing Hardware and Software Development Lifecycles with MKS Integrity Acquisition – PTC Integrity". Mks.com. Archived from the original on 2014-07-22. Retrieved 2014-01-26.
  78. ^ Rochkind, Marc J. (December 1975), "The Source Code Control System" (PDF), IEEE Transactions on Software Engineering, vol. SE-1, no. 4, pp. 364–370, doi:10.1109/tse.1975.6312866, S2CID 10006076, archived from the original (PDF) on 2011-05-25, retrieved 2014-07-31
  79. ^ http://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/usr/news/pibs PWB UNIX product announcement
  80. ^ Compare the SCCS 4 file format with the SCCS 5.0 Archived 2014-08-19 at the Wayback Machine file format (as manpage sccsfile(4) in "Archived copy". Archived from the original on 2014-08-19. Retrieved 2014-08-17.{{cite web}}: CS1 maint: archived copy as title (link)
  81. ^ Starteam®


Retrieved from "https://en.wikipedia.org/w/index.php?title=Comparison_of_version-control_software&oldid=1262617905"