Commit (version control)

This article is about the verb in revision control. For the noun, see changeset. For other uses, see Commit.

In version control systems, a commit adds the latest changes to [part of] the source code to the repository, making these changes part of the head revision of the repository. Unlike commits in data management, commits in version control systems are kept in the repository indefinitely. Thus, when other users do an update or a checkout from the repository, they will receive the latest committed version, unless they specify they wish to retrieve a previous version of the source code in the repository. Version control systems allow rolling back to previous versions easily. In this context, a commit within a version control system is protected as it is easily rolled back, even after the commit has been done.

Free/open-source	CVS (1986, 1990 in C) CVSNT (1998) QVCS Enterprise (1998) Subversion (2000)

Proprietary	Software Change Manager (1970s) Panvalet (1970s) Endevor (1980s) Dimensions CM (1980s) DSEE (1984) Synergy (1990) ClearCase (1992) CMVC (1994) Visual SourceSafe (1994) Perforce (1995) StarTeam (1995) Integrity (2001) Surround SCM (2002) AccuRev SCM (2002) SourceAnywhere (2003) Vault (2003) Team Foundation Server (2005) Team Concert (2008)

Distributed

Free/open-source	GNU arch (2001) Darcs (2002) DCVS (2002) ArX (2003) Monotone (2003) SVK (2003) Codeville (2005) Bazaar (2005) Git (2005) Mercurial (2005) Fossil (2007) Veracity (2010)

Proprietary	TeamWare (1990s?) Code Co-op (1997) BitKeeper (1998) Plastic SCM (2006)

Concepts

Category
Comparison
List

This article is issued from Wikipedia - version of the Wednesday, September 09, 2015. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.

Commit (version control)

See also