version_control:introduction_to_version_control_systems
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| version_control:introduction_to_version_control_systems [2019/02/21 18:48] – [Examples] mithat | version_control:introduction_to_version_control_systems [2019/02/21 18:50] – [Backing up is not a core function!] mithat | ||
|---|---|---|---|
| Line 23: | Line 23: | ||
| * Permit moving back and forth through different **revisions** (i.e., the history) of the project. | * Permit moving back and forth through different **revisions** (i.e., the history) of the project. | ||
| * Allow **branching** and **merging** of revisions. | * Allow **branching** and **merging** of revisions. | ||
| - | * Let multiple users (a team) share and integrate code. | + | * Let multiple users (a team) **share and integrate** code. |
| ===== Backing up is not a core function! ===== | ===== Backing up is not a core function! ===== | ||
| Line 29: | Line 29: | ||
| * The VCS you use may suck as a backup system. | * The VCS you use may suck as a backup system. | ||
| * Backing up is something you may or may not get "for free." | * Backing up is something you may or may not get "for free." | ||
| - | * Depending on the VCS you use, if you lose the repository, you may lose all the history---or the entire project. | + | * With some VCS, if you lose the repository, you lose all the history or even the entire project. |
| ===== Centralized versus distributed ===== | ===== Centralized versus distributed ===== | ||
version_control/introduction_to_version_control_systems.txt · Last modified: 2019/02/21 18:52 by mithat