Difference between revisions of "Revision control"
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) (→See also) |
||
| Line 22: | Line 22: | ||
* [[Git (software)]] | * [[Git (software)]] | ||
| + | * [[GitHub]] | ||
| + | * [[Source code]] | ||
* [[Source code repository]] | * [[Source code repository]] | ||
| + | * [[SourceForge]] | ||
== External links == | == External links == | ||
Revision as of 16:24, 24 August 2015
Revision control, also known as version control and source control (and an aspect of software configuration management), is the management of changes to:
- Documents
- Source code
- Other collections of information
Changes are usually identified by a number or letter code, termed the "revision number", "revision level", or simply "revision". For example, an initial set of files is "revision 1". When the first change is made, the resulting set is "revision 2", and so on. Each revision is associated with a timestamp and the person making the change.
Revisions can be compared, restored, and with some types of files, merged.
The need for a logical way to organize and control revisions has existed for almost as long as writing has existed, but revision control became much more important, and complicated, when the era of computing began.
The numbering of book editions and of specification revisions are examples that date back to the print-only era.
Today, the most capable (as well as complex) revision control systems are those used in software development, where a team of people may change the same files.
Version control systems (VCS) most commonly run as stand-alone applications, but revision control is also embedded in various types of software such as word processors and spreadsheets, e.g., Google Docs and Sheets, and in various content management systems.
See also
External links
- Revision control @ Wikipedia
- How to write a proper commit message by Laurence Gellert
