Git --fast-version-control
Topics ▾ Version 1.6.2.5 ▾ gitcvs-migration last updated in 2.0.0

SYNOPSIS

git cvsimport *

DESCRIPTION

Git differs from CVS in that every working tree contains a repository with a full copy of the project history, and no repository is inherently more important than any other. However, you can emulate the CVS model by designating a single shared repository which people can synchronize with; this document explains how to do that.

Some basic familiarity with git is required. Having gone through gittutorial(7) and gitglossary(7) should be sufficient.

Developing against a shared repository

Suppose a shared repository is set up in /pub/repo.git on the host foo.com. Then as an individual committer you can clone the shared repository over ssh with:

$ git clone foo.com:/pub/repo.git/ my-project
$ cd my-project

and hack away. The equivalent of cvs update is

$ git pull origin

which merges in any work that others might have done since the clone operation. If there are uncommitted changes in your working tree, commit them first before running git pull.

Note
================================ The pull command knows where to get updates from because of certain configuration variables that were set by the first git-clone command; see git config -l and the git-config(1) man