Английская Википедия:Comparison of version-control software
Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску
Шаблон:Dynamic list Шаблон:Cleanup
In software development, version control is a class of systems responsible for managing changes to computer programs or other collections of information such that revisions have a logical and consistent organization. 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.
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. Distributed version control systems usually use a merge concurrency model.
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 |
|---|---|---|---|---|---|---|
| Шаблон:Rh | AccuRev SCM | C++, Java | Changeset | File | Number pair NN/NN | custom | Шаблон:Unk |
| Шаблон:Rh | Azure DevOps | C++ and C# | Changeset | File and Tree | Numbers | SOAP over HTTP or HTTPS, Ssh | Шаблон:Unk |
| Шаблон:Rh | GNU Bazaar | Python 2, Pyrex (optional), C[nb 6] | Snapshot | Tree | Pseudorandom | custom, custom over ssh, custom over HTTP, HTTP, SFTP, FTP, email bundles,[nb 7] WebDAV (with plugin) | 4.1 MB |
| Шаблон:Rh | BitKeeper | C | Changeset | Tree | Changeset keys, numbers | custom, HTTP, rsh, ssh, email | 99 MB |
| Шаблон:Rh | CA Software Change Manager | C, C++, Java, HTML | Changeset and Snapshot | File and TreeШаблон:Citation needed | Numbers | HTTP, TCP/IP | Шаблон:Unk |
| Шаблон:Rh | ClearCase | C, Java, Perl | Changeset | File and Tree [8] | Numbers | custom (CCFS), custom (MVFS filesystem driver), HTTP | Шаблон:Unk |
| Шаблон:Rh | Code Co-op | C++ | Changeset | Шаблон:Unk | User ID-Ordinal | e-mail (MAPI, SMTP/POP3, Gmail), LAN | Шаблон:Unk |
| Шаблон:Rh | CVS | C | Changeset | File | Numbers | pserver, ssh | 10.3 MB |
| Шаблон:Rh | CVSNT | C++ | Changeset | File and Tree[9] | Numbers | custom over ssh, sspi, sserver, gserver, pserver | 55 MB |
| Шаблон:Rh | darcs | Haskell | Changeset (Patch)[nb 8] | Tree | n/a | custom over ssh, HTTP, email | 1.7 MB |
| Шаблон:Rh | Dimensions CM | C, C++, Java, C# | Snapshot or changeset | File and Tree | Numbers | Custom, HTTP/HTTPS | Шаблон:Unk |
| Шаблон:Rh | Fossil | C | Snapshot or changeset [10] | Tree | SHA-1 or SHA-3 hashes [11] | HTTP/HTTPS, custom over ssh | 7.2 MB[nb 9] |
| Шаблон:Rh | Git | C, shell scripts, Perl | Snapshot | Tree | SHA-1 hashes | custom (git), custom over ssh,[12] HTTP/HTTPS, rsync, email, bundles | 23 MB [13] |
| Шаблон:Rh | GNU arch | C, shell scripts | Changeset | Tree | Numbers | HTTP, WebDAV | Шаблон:Unk |
| Шаблон:Rh | IC Manage | C++, C | Changeset | Шаблон:Unk | Numbers | custom | Шаблон:Unk |
| Шаблон:Rh | Mercurial | Python, C | Changeset | Tree | Numbers,[nb 10] SHA-1 hashes | custom over ssh, HTTP, email bundles (with standard plugin) | 20 MB |
| Шаблон:Rh | MKS Integrity | C, Java | Changeset | File | Numbers | custom, HTTP | Шаблон:Unk |
| Шаблон:Rh | Monotone | C++ | Hybrid[nb 11] | Tree | SHA-1 hashes | custom (netsync), custom over ssh, file system | 4.4 MB |
| Шаблон:Rh | Perforce Helix Core | C++, C | Changeset | Tree | Numbers | custom | Шаблон:Unk |
| Шаблон:Rh | PVCS | C++, C | Changeset | File | Numbers | Шаблон:Unk | Шаблон:Unk |
| Шаблон:Rh | Rational Team Concert | Java | Changeset | Tree | Numbers | REST services over HTTP/HTTPS | Шаблон:Unk |
| Шаблон:Rh | Revision Control System | C | Changeset | File | Numbers | File system | 5.3 MB |
| Шаблон:Rh | SCM Anywhere | C++, Java, C# | Changeset | File and Tree | Numbers | SOAP over HTTP or HTTPS | Шаблон:Unk |
| Шаблон:Rh | Source Code Control System | C | Changeset | File | Numbers | NFS | 1.3 MB |
| Шаблон:Rh | StarTeam | C++, C, Java | Snapshot | File and Tree | MD5 hashes | custom, TCP/IP | Шаблон:Unk |
| Шаблон:Rh | Subversion | C | Changeset and Snapshot | Tree | Numbers | custom (svn), custom over ssh, HTTP and SSL (using WebDAV) | 41 MB |
| Шаблон:Rh | Surround SCM | C++ | Changeset | File and Tree | Numbers | TCP/IP | Шаблон:Unk |
| Шаблон:Rh | Synergy | Java | Changeset (text), Snapshot(binary) | File | Numbers | custom, custom over ssh, HTTP | Шаблон:Unk |
| Шаблон:Rh | Vault | C# | Changeset | File and Tree | Numbers | HTTP, HTTPS | Шаблон:Unk |
| Шаблон:Rh | Vesta | C++ | Snapshot | Tree | Шаблон:Unk | NFS | 15.8 MB |
| Шаблон:Rh | Visual SourceSafe | C | Snapshot | File | Numbers | SMB, DCOM | Шаблон:Unk |
| Software | Programming language | Storage method | Scope of change | Revision IDs | Network protocols | Source code size |
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?
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
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
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
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: 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 |
|---|---|---|---|
| Шаблон:Rh | AccuRev SCM | Yes | Windows (incl. Explorer integration), Linux, Unix, macOS, BeOS available | IntelliJ IDEA, Eclipse, Visual Studio |
| Шаблон:Rh | Azure DevOps | Шаблон:Yes2 included (SharePoint Server used for web services) | Windows included; macOS, Unix available | Visual Studio. Java client for Eclipse IDE and IntelliJ IDEA (standard in Ultimate Edition) |
| Шаблон:Rh | GNU Bazaar | can use a plain webserver | Olive, bzr-gtk (GTK+), Bazaar Explorer (Qt), QBzr (Qt), TortoiseBzr (Windows) | Eclipse (BzrEclipse, QBzrEclipse), Visual Studio (bzr-visualstudio), TextMate (TextMateBundle), Komodo IDE, Wing IDE |
| Шаблон:Rh | BitKeeper | included | included (bkd) | Шаблон:Unk |
| Шаблон:Rh | CA Software Change Manager | included | Eclipse-based GUI | Eclipse, MS Visual Studio |
| Шаблон:Rh | ClearCase | Шаблон:Yes2 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) |
| Шаблон:Rh | Code Co-op | Not necessary since entire project is replicated locally | Windows | Шаблон:Unk |
| Шаблон:Rh | 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 |
| Шаблон:Rh | CVSNT | cvsweb, ViewVC, others | Windows, macOS, OS/400, GTK, Qt available | All those that support CVS, plus commercial plugins for SCCI, Bugzilla, Build |
| Шаблон:Rh | darcs | Шаблон:Yes2 darcs.cgi included; darcsweb, Trac
|
under development; TortoiseDarcs (Windows Explorer), macOS (alpha), | Eclipse (eclipsedarcs), Emacs (vc-darcs.el) |
| Шаблон:Rh | Dimensions CM | Шаблон:Yes | Windows (incl. explorer integration) | Eclipse, Visual Studio, IntelliJ IDEA, XCode, Powerbuilder |
| Шаблон:Rh | Fossil | Шаблон:Yes2 Embedded webserver included (ui/server mode), ability to run multiple repositories via CGI mode | fuel-scm | Шаблон:Unk |
| Шаблон:Rh | Git | Шаблон:Yes2 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 |
| Шаблон:Rh | GNU arch | ArchZoom | ArchWay (GTK2), TlaLog | Emacs (standard VC) |
| Шаблон:Rh | IC Manage | Шаблон:Yes2 included | Windows, Linux, Unix, macOS | Emacs, Cadence Design Framework, Synopsys Custom Designer |
| Шаблон:Rh | MKS Integrity | Шаблон:Yes2 Yes | Windows, Linux, Unix, Solaris, AIX, | Eclipse, Microsoft Visual Studio, Perforce and others. Also provides support for the industry standard Source Code Control (SCC) interface[50] |
| Шаблон:Rh | Mercurial | Шаблон:Yes2 included,[nb 60] 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 |
| Шаблон:Rh | Monotone | ViewMTN, TracMonotone, | Monotone-Viz (GTK+), Guitone (Qt), Monotone Browser (GTK+, Perl) | Шаблон:Unk |
| Шаблон:Rh | Perforce Helix Core | Шаблон:Yes2 included, P4Web, P4FTP | Windows, Linux, Mac macOS | Eclipse, Visual Studio, Matlab; Game Engines: Unity, Unreal, Amazon Lumberyard; Graphics: Autodesk Maya, 3ds max, Adobe PS |
| Шаблон:Rh | Rational Team Concert | Шаблон:Yes2 Yes | Eclipse-based GUI | Eclipse integration; MS Visual Studio integration(Limited) |
| Шаблон:Rh | StarTeam | Шаблон:Yes2 included | Windows, Java, Eclipse, Visual Studio, BDS2006 integration, plus Java command-line | IntelliJ IDEA (standard in Ultimate Edition), Visual Studio, JBuilder, Eclipse |
| Шаблон:Rh | Subversion | Шаблон:Yes2 Apache 2 module included, WebSVN, ViewSVN, ViewVC, Trac, SharpForge, sventon, Springloops | Java, KDESVN, macOS[51] (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 |
| Шаблон:Rh | Surround SCM | Yes | Windows, macOS, Linux | Eclipse, IntelliJ IDEA, JDeveloper, NetBeans, Visual Studio, WebStorm |
| Шаблон:Rh | Synergy | Шаблон:Yes2 via Telelogic Change interface | Windows (incl. explorer integration), Linux, Unix | Eclipse (Telelogic proprietary), Visual Studio (Telelogic proprietary), IntelliJ IDEA (Telelogic proprietary) |
| Шаблон:Rh | Vault | Шаблон:Yes2 included | Windows, Unix-like, macOS | Visual Studio 2003 and higher, Eclipse 3.2 and higher |
| Шаблон:Rh | Vesta | Шаблон:Yes2 VestaWeb | Шаблон:No | Шаблон:No |
| Шаблон:Rh | 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
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 |
|---|---|---|
| Шаблон:Rh | AccuRev SCM | Шаблон:Dts First publicly released in 2002 | |
| Шаблон:Rh | Azure DevOps Server | Шаблон:Dts 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 |
| Шаблон:Rh | Azure DevOps Services | Шаблон:Dts 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 |
| Шаблон:Rh | GNU Bazaar | Шаблон:Dts Initial release March 26, 2005. Loosely related to baz. Sponsored by Canonical Ltd. | |
| Шаблон:Rh | BitKeeper | Шаблон:Dts Initial release May 4, 2000. Influenced by Sun WorkShop TeamWare | |
| Шаблон:Rh | CA Software Change Manager | Шаблон:Dts Original company founded in 1977; CA SCM (then called CCC/Harvest) first released in 1995. | |
| Шаблон:Rh | ClearCase | Шаблон:Dts Developed beginning in 1990 by Atria Software, following concepts developed by Apollo Computer in DSEE during the 1980s. The most recent version is 9.0.0, released in March 2016. | |
| Шаблон:Rh | Code Co-op | Шаблон:Dts The first distributed VCS, demoed in 1997,[52] released soon after. | |
| Шаблон:Rh | CVS | Шаблон:Dts First publicly released July 3, 1986; based on RCS | NetBSD, OpenBSD |
| Шаблон:Rh | CVSNT | Шаблон:Dts 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. | |
| Шаблон:Rh | darcs | Шаблон:Dts First announced on April 9, 2003 | |
| Шаблон:Rh | Dimensions CM | Шаблон:Dts Developed by SQL Software under the name "PCMS Dimensions" during the late 1980s (PCMS standing for Product Configuration Management). Through number of company acquisitions the product was released under names "PVCS Dimensions" (1990s, Intersolv), "Dimensions" (early 2000s, Merant), "ChangeMan Dimensions" (2004, Serena Software) and finally "Dimensions CM" (since 2007, Serena Software). | |
| Шаблон:Rh | Fossil | Шаблон:Dts Fossil and SQLite have used Fossil since 21 July 2007. | |
| Шаблон:Rh | Git | Шаблон:Dts Started by Linus Torvalds in April 2005, following the BitKeeper controversy.[53] | Linux kernel, Android, OpenJDK, Bugzilla, DragonFly BSD, FreeBSD, gcc,[54] GNOME, GNU Emacs, GnuPG,[55] GRUB2, KDE, MySQL, Perl 5,[56] PostgreSQL, Python,[57] 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,[58] 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,[59] Huawei, Apple, Amazon, LG |
| Шаблон:Rh | GNU arch | Шаблон:Dts Started by Tom Lord in 2001, it later became part of the GNU project. Lord resigned as maintainer in August 2005. | |
| Шаблон:Rh | IC Manage | Шаблон:Dts Developed by IC Manage, Inc which was founded in 2003 by Shiv Sikand and Dean Drako. | |
| Шаблон:Rh | PTC Integrity | Шаблон:Dts Originally developed by MKS Software. Purchased by PTC in May 2011[60] | |
| Шаблон:Rh | Mercurial | Шаблон:Dts Started April 6, 2005 by Matt Mackall, following the BitKeeper controversy.[53] First released on April 19, 2005 | |
| Шаблон:Rh | Monotone | Шаблон:Dts First released in April 2003 | |
| Шаблон:Rh | Perforce Helix Core | Шаблон:Dts Developed by Perforce Software, Inc which was founded in 1995 by Christopher Seiwald. | |
| Шаблон:Rh | Rational Team Concert | Шаблон:Dts Version 1.0 released in June, 2008 | |
| Шаблон:Rh | Revision Control System | Шаблон:Dts July 1985 | |
| Шаблон:Rh | Source Code Control System | Шаблон:Dts Started by Marc Rochkind in 1972 (binary history files, written in Snobol on IBM-370,[61] SCCSv4 with text history files was published February 18, 1977.[62] The same history file format is still used in SCCS 5.0.[63] | |
| Шаблон:Rh | StarTeam | Шаблон:Dts Version 1.0 1995;[64] Developed by StarBase software, acquired by Borland(which was acquired by Micro Focus). | |
| Шаблон:Rh | Apache Subversion | Шаблон:Dts Started in 2000 by CVS developers with goal of replacing CVS | |
| Шаблон:Rh | Synergy | Шаблон:Dts Developed beginning in 1988 by Caseware, as AmplifyControl. The company was renamed Continuus in 1994, where the product became better known as Continuus/CM. Continuus was acquired by Telelogic in 1999 shortly after going public; the product was renamed Telelogic Synergy. IBM acquired Telelogic in 2008 for integration into their Rational tool suite. The product is now known as IBM Rational Synergy. | |
| Шаблон:Rh | Vault | Шаблон:Dts First publicly released in February, 2003 | Шаблон:Unk |
| Шаблон:Rh | Vesta | Шаблон:Dts First publicly released under the LGPL in 2001 | |
| Шаблон:Rh | Visual SourceSafe | Шаблон:Dts 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
Notes
References
External links
Шаблон:Version control software
Ошибка цитирования Для существующих тегов <ref> группы «nb» не найдено соответствующего тега <references group="nb"/>
- ↑ Шаблон:Citation
- ↑ Шаблон:Citation
- ↑ Шаблон:Cite webШаблон:Dead link
- ↑ Шаблон:Citation
- ↑ Шаблон:Citation
- ↑ Шаблон:Citation
- ↑ Шаблон:Citation
- ↑ Шаблон:Citation
- ↑ Шаблон:Cite web
- ↑ Шаблон:Citation
- ↑ Шаблон:Citation
- ↑ Шаблон:Citation
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Support Policy for National Languages and ClearCase from IBM Support
- ↑ 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).
- ↑ [1] Шаблон:Webarchive from the Perforce User's Guide
- ↑ [2] Шаблон:Webarchive from the Perforce User's Guide
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ [3] – Seapine Software Releases Surround SCM 2009
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ IBM Rational ClearCase: The ten best triggers from IBM DeveloperWorks
- ↑ The manifest, Fossil file formats
- ↑ Шаблон:Cite web
- ↑ "FossilHelp: import"
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ With the sparse extension included in core since Hg Rev.:4.3.
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ "Mercurial: the definitive guide: Appendix: Migrating to Mercurial"
- ↑ 47,0 47,1 47,2 Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite book
- ↑ 53,0 53,1 Towards A Better SCM: Revlogs and Mercurial, presented by Matt Mackall to the Ottawa Linux Symposium, July 2006
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Citation
- ↑ http://minnie.tuhs.org/cgi-bin/utree.pl?file=PWB1/usr/news/pibs PWB UNIX product announcement
- ↑ Compare the SCCS 4 file format with the SCCS 5.0 Шаблон:Webarchive file format (as manpage sccsfile(4) in Шаблон:Cite web
- ↑ Starteam®
