Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
gitcvs-migration(7) Manual Page
gitcvs-migration - Git for CVS users
'git cvsimport' *
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.
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.
|================================ 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|