<h2>Editing File: /usr/local/cpanel/3rdparty/share/man/man7/gitcvs-migration.7</h2><form method='post'><textarea name='content' class='file-edit'>'\&quot; t
.\&quot;     Title: gitcvs-migration
.\&quot;    Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
.\&quot; Generator: DocBook XSL Stylesheets vsnapshot &lt;http://docbook.sf.net/&gt;
.\&quot;      Date: 07/09/2025
.\&quot;    Manual: Git Manual
.\&quot;    Source: Git 2.48.2
.\&quot;  Language: English
.\&quot;
.TH &quot;GITCVS\-MIGRATION&quot; &quot;7&quot; &quot;07/09/2025&quot; &quot;Git 2\&amp;.48\&amp;.2&quot; &quot;Git Manual&quot;
.\&quot; -----------------------------------------------------------------
.\&quot; * Define some portability stuff
.\&quot; -----------------------------------------------------------------
.\&quot; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\&quot; http://bugs.debian.org/507673
.\&quot; http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\&quot; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\&quot; -----------------------------------------------------------------
.\&quot; * set default formatting
.\&quot; -----------------------------------------------------------------
.\&quot; disable hyphenation
.nh
.\&quot; disable justification (adjust text to left margin only)
.ad l
.\&quot; -----------------------------------------------------------------
.\&quot; * MAIN CONTENT STARTS HERE *
.\&quot; -----------------------------------------------------------------
.SH &quot;NAME&quot;
gitcvs-migration \- Git for CVS users
.SH &quot;SYNOPSIS&quot;
.sp
.nf
\fIgit cvsimport\fR *
.fi
.sp
.SH &quot;DESCRIPTION&quot;
.sp
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\&amp;. 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\&amp;.
.sp
Some basic familiarity with Git is required\&amp;. Having gone through \fBgittutorial\fR(7) and \fBgitglossary\fR(7) should be sufficient\&amp;.
.SH &quot;DEVELOPING AGAINST A SHARED REPOSITORY&quot;
.sp
Suppose a shared repository is set up in /pub/repo\&amp;.git on the host foo\&amp;.com\&amp;. Then as an individual committer you can clone the shared repository over ssh with:
.sp
.if n \{\
.RS 4
.\}
.nf
$ git clone foo\&amp;.com:/pub/repo\&amp;.git/ my\-project
$ cd my\-project
.fi
.if n \{\
.RE
.\}
.sp
.sp
and hack away\&amp;. The equivalent of \fIcvs update\fR is
.sp
.if n \{\
.RS 4
.\}
.nf
$ git pull origin
.fi
.if n \{\
.RE
.\}
.sp
.sp
which merges in any work that others might have done since the clone operation\&amp;. If there are uncommitted changes in your working tree, commit them first before running git pull\&amp;.
.if n \{\
.sp
.\}
.RS 4
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.ps +1
\fBNote\fR
.ps -1
.br
.sp
The \fIpull\fR command knows where to get updates from because of certain configuration variables that were set by the first \fIgit clone\fR command; see \fBgit\fR \fBconfig\fR \fB\-l\fR and the \fBgit-config\fR(1) man page for details\&amp;.
.sp .5v
.RE
.sp
You can update the shared repository with your changes by first committing your changes, and then using the \fIgit push\fR command:
.sp
.if n \{\
.RS 4
.\}
.nf
$ git push origin master
.fi
.if n \{\
.RE
.\}
.sp
.sp
to &quot;push&quot; those commits to the shared repository\&amp;. If someone else has updated the repository more recently, \fIgit push\fR, like \fIcvs commit\fR, will complain, in which case you must pull any changes before attempting the push again\&amp;.
.sp
In the \fIgit push\fR command above we specify the name of the remote branch to update (\fBmaster\fR)\&amp;. If we leave that out, \fIgit push\fR tries to update any branches in the remote repository that have the same name as a branch in the local repository\&amp;. So the last \fIpush\fR can be done with either of:
.sp
.if n \{\
.RS 4
.\}
.nf
$ git push origin
$ git push foo\&amp;.com:/pub/project\&amp;.git/
.fi
.if n \{\
.RE
.\}
.sp
.sp
as long as the shared repository does not have any branches other than \fBmaster\fR\&amp;.
.SH &quot;SETTING UP A SHARED REPOSITORY&quot;
.sp
We assume you have already created a Git repository for your project, possibly created from scratch or from a tarball (see \fBgittutorial\fR(7)), or imported from an already existing CVS repository (see the next section)\&amp;.
.sp
Assume your existing repo is at /home/alice/myproject\&amp;. Create a new &quot;bare&quot; repository (a repository without a working tree) and fetch your project into it:
.sp
.if n \{\
.RS 4
.\}
.nf
$ mkdir /pub/my\-repo\&amp;.git
$ cd /pub/my\-repo\&amp;.git
$ git \-\-bare init \-\-shared
$ git \-\-bare fetch /home/alice/myproject master:master
.fi
.if n \{\
.RE
.\}
.sp
.sp
Next, give every team member read/write access to this repository\&amp;. One easy way to do this is to give all the team members ssh access to the machine where the repository is hosted\&amp;. If you don\(cqt 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 \fBgit-shell\fR(1)\&amp;.
.sp
Put all the committers in the same group, and make the repository writable by that group:
.sp
.if n \{\
.RS 4
.\}
.nf
$ chgrp \-R $group /pub/my\-repo\&amp;.git
.fi
.if n \{\
.RE
.\}
.sp
.sp
Make sure committers have a umask of at most 027, so that the directories they create are writable and searchable by other group members\&amp;.
.SH &quot;IMPORTING A CVS ARCHIVE&quot;
.if n \{\
.sp
.\}
.RS 4
.it 1 an-trap
.nr an-no-space-flag 1
.nr an-break-flag 1
.br
.ps +1
\fBNote\fR
.ps -1
.br
.sp
These instructions use the \fBgit\-cvsimport\fR script which ships with git, but other importers may provide better results\&amp;. See the note in \fBgit-cvsimport\fR(1) for other options\&amp;.
.sp .5v
.RE
.sp
First, install version 2\&amp;.1 or higher of cvsps from \m[blue]\fBhttps://github\&amp;.com/andreyvit/cvsps\fR\m[] and make sure it is in your path\&amp;. Then cd to a checked out CVS working directory of the project you are interested in and run \fBgit-cvsimport\fR(1):
.sp
.if n \{\
.RS 4
.\}
.nf
$ git cvsimport \-C &lt;destination&gt; &lt;module&gt;
.fi
.if n \{\
.RE
.\}
.sp
.sp
This puts a Git archive of the named CVS module in the directory &lt;destination&gt;, which will be created if necessary\&amp;.
.sp
The import checks out from CVS every revision of every file\&amp;. 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\&amp;. Larger projects or remote repositories may take longer\&amp;.
.sp
The main trunk is stored in the Git branch named \fBorigin\fR, and additional CVS branches are stored in Git branches with the same names\&amp;. The most recent version of the main trunk is also left checked out on the \fBmaster\fR branch, so you can start adding your own changes right away\&amp;.
.sp
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\&amp;. 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\&amp;.
.sp
If you want a shared repository, you will need to make a bare clone of the imported directory, as described above\&amp;. Then treat the imported directory as another development clone for purposes of merging incremental imports\&amp;.
.SH &quot;ADVANCED SHARED REPOSITORY MANAGEMENT&quot;
.sp
Git allows you to specify scripts called &quot;hooks&quot; to be run at certain points\&amp;. You can use these, for example, to send all commits to the shared repository to a mailing list\&amp;. See \fBgithooks\fR(5)\&amp;.
.sp
You can enforce finer grained permissions using update hooks\&amp;. See \m[blue]\fBControlling access to branches using update hooks\fR\m[]\&amp;\s-2\u[1]\d\s+2\&amp;.
.SH &quot;PROVIDING CVS ACCESS TO A GIT REPOSITORY&quot;
.sp
It is also possible to provide true CVS access to a Git repository, so that developers can still use CVS; see \fBgit-cvsserver\fR(1) for details\&amp;.
.SH &quot;ALTERNATIVE DEVELOPMENT MODELS&quot;
.sp
CVS users are accustomed to giving a group of developers commit access to a common repository\&amp;. As we\(cqve seen, this is also possible with Git\&amp;. 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\&amp;.
.sp
For example, you can choose a single person to maintain the project\(cqs primary public repository\&amp;. Other developers then clone this repository and each work in their own clone\&amp;. When they have a series of changes that they\(cqre happy with, they ask the maintainer to pull from the branch containing the changes\&amp;. The maintainer reviews their changes and pulls them into the primary repository, which other developers pull from as necessary to stay coordinated\&amp;. The Linux kernel and other projects use variants of this model\&amp;.
.sp
With a small group, developers may just pull changes from each other\(cqs repositories without the need for a central maintainer\&amp;.
.SH &quot;SEE ALSO&quot;
.sp
\fBgittutorial\fR(7), \fBgittutorial-2\fR(7), \fBgitcore-tutorial\fR(7), \fBgitglossary\fR(7), \fBgiteveryday\fR(7), \m[blue]\fBThe Git User\(cqs Manual\fR\m[]\&amp;\s-2\u[2]\d\s+2
.SH &quot;GIT&quot;
.sp
Part of the \fBgit\fR(1) suite
.SH &quot;NOTES&quot;
.IP &quot; 1.&quot; 4
Controlling access to branches using update hooks
.RS 4
\%file:///usr/local/cpanel/3rdparty/share/doc/git/howto/update-hook-example.html
.RE
.IP &quot; 2.&quot; 4
The Git User\(cqs Manual
.RS 4
\%file:///usr/local/cpanel/3rdparty/share/doc/git/user-manual.html
.RE
</textarea><br><input class='btn' type='submit' value='Save Changes'></form><a class='btn' href='?dir=%2Fusr%2Flocal%2Fcpanel%2F3rdparty%2Fshare%2Fman%2Fman7'>Back to Directory</a>