Abstract

Distributed version controls models relax the dependency upon a central repository as the keeper of the one true project.

• Every developer has a snapshot of an entire development history.

  • In essence, you check out the entire past history of a project.
  • And every checked out copy becomes an independent branch.

• Developers may decide for themselves which of these branches should merge

  • Merging and conflict resolution, which are treated as exceptional operations in centralized systems, are regarded as the norm in this model.

We will look at git, a popular distributed version control system.

Read or review this CS252 lecture, including the sections marked “optional”.