<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sect2 SYSTEM "../../../dtd/dblite.dtd">

<sect2 lang="en" id="gitcvs-migration(7)">
    <title>gitcvs-migration(7)</title>
    <date>2024-07-02</date>
<revhistory><revision><date>2024-07-02</date></revision></revhistory>
<indexterm>
<primary>gitcvs-migration(7)</primary>
</indexterm>
<simplesect id="gitcvs-migration(7)__name">
<title>NAME</title>
<simpara>gitcvs-migration - Git for CVS users</simpara>
</simplesect>
<simplesect id="gitcvs-migration(7)__synopsis">
<title>SYNOPSIS</title>
<blockquote>
<literallayout><emphasis>git cvsimport</emphasis> *</literallayout>
</blockquote>
</simplesect>
<simplesect id="gitcvs-migration(7)__description">
<title>DESCRIPTION</title>
<simpara>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.</simpara>
<simpara>Some basic familiarity with Git is required. Having gone through
<xref linkend="gittutorial(7)" /> and
<xref linkend="gitglossary(7)" /> should be sufficient.</simpara>
</simplesect>
<simplesect id="gitcvs-migration(7)__developing_against_a_shared_repository">
<title>Developing against a shared repository</title>
<simpara>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:</simpara>
<screen>$ git clone foo.com:/pub/repo.git/ my-project
$ cd my-project</screen>
<simpara>and hack away.  The equivalent of <emphasis>cvs update</emphasis> is</simpara>
<screen>$ git pull origin</screen>
<simpara>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.</simpara>
<note>
<simpara>The <emphasis>pull</emphasis> command knows where to get updates from because of certain
configuration variables that were set by the first <emphasis>git clone</emphasis>
command; see <emphasis>git config -l</emphasis> and the <xref linkend="git-config(1)" /> man
page for details.</simpara>
</note>
<simpara>You can update the shared repository with your changes by first committing
your changes, and then using the <emphasis>git push</emphasis> command:</simpara>
<screen>$ git push origin master</screen>
<simpara>to "push" those commits to the shared repository.  If someone else has
updated the repository more recently, <emphasis>git push</emphasis>, like <emphasis>cvs commit</emphasis>, will
complain, in which case you must pull any changes before attempting the
push again.</simpara>
<simpara>In the <emphasis>git push</emphasis> command above we specify the name of the remote branch
to update (<emphasis>master</emphasis>).  If we leave that out, <emphasis>git push</emphasis> tries to update
any branches in the remote repository that have the same name as a branch
in the local repository.  So the last <emphasis>push</emphasis> can be done with either of:</simpara>
<screen>$ git push origin
$ git push foo.com:/pub/project.git/</screen>
<simpara>as long as the shared repository does not have any branches
other than <emphasis>master</emphasis>.</simpara>
</simplesect>
<simplesect id="gitcvs-migration(7)__setting_up_a_shared_repository">
<title>Setting Up a Shared Repository</title>
<simpara>We assume you have already created a Git repository for your project,
possibly created from scratch or from a tarball (see
<xref linkend="gittutorial(7)" />), or imported from an already existing CVS
repository (see the next section).</simpara>
<simpara>Assume your existing repo is at /home/alice/myproject.  Create a new "bare"
repository (a repository without a working tree) and fetch your project into
it:</simpara>
<screen>$ mkdir /pub/my-repo.git
$ cd /pub/my-repo.git
$ git --bare init --shared
$ git --bare fetch /home/alice/myproject master:master</screen>
<simpara>Next, give every team member read/write access to this repository.  One
easy way to do this is to give all the team members ssh access to the
machine where the repository is hosted.  If you don't want to give them a
full shell on the machine, there is a restricted shell which only allows
users to do Git pushes and pulls; see <xref linkend="git-shell(1)" />.</simpara>
<simpara>Put all the committers in the same group, and make the repository
writable by that group:</simpara>
<screen>$ chgrp -R $group /pub/my-repo.git</screen>
<simpara>Make sure committers have a umask of at most 027, so that the directories
they create are writable and searchable by other group members.</simpara>
</simplesect>
<simplesect id="gitcvs-migration(7)__importing_a_cvs_archive">
<title>Importing a CVS archive</title>
<note><simpara>These instructions use the <emphasis>git-cvsimport</emphasis> script which ships with
git, but other importers may provide better results. See the note in
<xref linkend="git-cvsimport(1)" /> for other options.</simpara></note>
<simpara>First, install version 2.1 or higher of cvsps from
<ulink url="https://github.com/andreyvit/cvsps">https://github.com/andreyvit/cvsps</ulink> and make
sure it is in your path.  Then cd to a checked out CVS working directory
of the project you are interested in and run <xref linkend="git-cvsimport(1)" />:</simpara>
<screen>$ git cvsimport -C &lt;destination&gt; &lt;module&gt;</screen>
<simpara>This puts a Git archive of the named CVS module in the directory
&lt;destination&gt;, which will be created if necessary.</simpara>
<simpara>The import checks out from CVS every revision of every file.  Reportedly
cvsimport can average some twenty revisions per second, so for a
medium-sized project this should not take more than a couple of minutes.
Larger projects or remote repositories may take longer.</simpara>
<simpara>The main trunk is stored in the Git branch named <emphasis>origin</emphasis>, and additional
CVS branches are stored in Git branches with the same names.  The most
recent version of the main trunk is also left checked out on the <emphasis>master</emphasis>
branch, so you can start adding your own changes right away.</simpara>
<simpara>The import is incremental, so if you call it again next month it will
fetch any CVS updates that have been made in the meantime.  For this to
work, you must not modify the imported branches; instead, create new
branches for your own changes, and merge in the imported branches as
necessary.</simpara>
<simpara>If you want a shared repository, you will need to make a bare clone
of the imported directory, as described above. Then treat the imported
directory as another development clone for purposes of merging
incremental imports.</simpara>
</simplesect>
<simplesect id="gitcvs-migration(7)__advanced_shared_repository_management">
<title>Advanced Shared Repository Management</title>
<simpara>Git allows you to specify scripts called "hooks" to be run at certain
points.  You can use these, for example, to send all commits to the shared
repository to a mailing list.  See <xref linkend="githooks(5)" />.</simpara>
<simpara>You can enforce finer grained permissions using update hooks.  See
<ulink url="https://www.kernel.org/pub/software/scm/git/docs/howto/update-hook-example.html"><citetitle>Controlling access to branches using
update hooks</citetitle></ulink>.</simpara>
</simplesect>
<simplesect id="gitcvs-migration(7)__providing_cvs_access_to_a_git_repository">
<title>Providing CVS Access to a Git Repository</title>
<simpara>It is also possible to provide true CVS access to a Git repository, so
that developers can still use CVS; see <xref linkend="git-cvsserver(1)" /> for
details.</simpara>
</simplesect>
<simplesect id="gitcvs-migration(7)__alternative_development_models">
<title>Alternative Development Models</title>
<simpara>CVS users are accustomed to giving a group of developers commit access to
a common repository.  As we've seen, this is also possible with Git.
However, the distributed nature of Git allows other development models,
and you may want to first consider whether one of them might be a better
fit for your project.</simpara>
<simpara>For example, you can choose a single person to maintain the project's
primary public repository.  Other developers then clone this repository
and each work in their own clone.  When they have a series of changes that
they're happy with, they ask the maintainer to pull from the branch
containing the changes.  The maintainer reviews their changes and pulls
them into the primary repository, which other developers pull from as
necessary to stay coordinated.  The Linux kernel and other projects use
variants of this model.</simpara>
<simpara>With a small group, developers may just pull changes from each other's
repositories without the need for a central maintainer.</simpara>
</simplesect>
<simplesect id="gitcvs-migration(7)__see_also">
<title>SEE ALSO</title>
<simpara><xref linkend="gittutorial(7)" />,
<xref linkend="gittutorial-2(7)" />,
<xref linkend="gitcore-tutorial(7)" />,
<xref linkend="gitglossary(7)" />,
<xref linkend="giteveryday(7)" />,
<ulink url="https://www.kernel.org/pub/software/scm/git/docs/user-manual.html"><citetitle>The Git User's Manual</citetitle></ulink></simpara>
</simplesect>
<simplesect id="gitcvs-migration(7)__git">
<title>GIT</title>
<simpara>Part of the <xref linkend="git(1)" /> suite</simpara>
</simplesect>
</sect2>
