<h2>Editing File: /usr/local/cpanel/3rdparty/share/man/man1/git-cvsimport.1</h2><form method='post'><textarea name='content' class='file-edit'>'\&quot; t
.\&quot;     Title: git-cvsimport
.\&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;GIT\-CVSIMPORT&quot; &quot;1&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;
git-cvsimport \- Salvage your data out of another SCM people love to hate
.SH &quot;SYNOPSIS&quot;
.sp
.nf
\fIgit cvsimport\fR [\-o &lt;branch\-for\-HEAD&gt;] [\-h] [\-v] [\-d &lt;CVSROOT&gt;]
              [\-A &lt;author\-conv\-file&gt;] [\-p &lt;options\-for\-cvsps&gt;] [\-P &lt;file&gt;]
              [\-C &lt;git\-repository&gt;] [\-z &lt;fuzz&gt;] [\-i] [\-k] [\-u] [\-s &lt;subst&gt;]
              [\-a] [\-m] [\-M &lt;regex&gt;] [\-S &lt;regex&gt;] [\-L &lt;commit\-limit&gt;]
              [\-r &lt;remote&gt;] [\-R] [&lt;CVS\-module&gt;]
.fi
.sp
.SH &quot;DESCRIPTION&quot;
.sp
\fBWARNING:\fR \fBgit\fR \fBcvsimport\fR uses cvsps version 2, which is considered deprecated; it does not work with cvsps version 3 and later\&amp;. If you are performing a one\-shot import of a CVS repository consider using \m[blue]\fBcvs2git\fR\m[]\&amp;\s-2\u[1]\d\s+2 or \m[blue]\fBcvs\-fast\-export\fR\m[]\&amp;\s-2\u[2]\d\s+2\&amp;.
.sp
Imports a CVS repository into Git\&amp;. It will either create a new repository, or incrementally import into an existing one\&amp;.
.sp
Splitting the CVS log into patch sets is done by \fIcvsps\fR\&amp;. At least version 2\&amp;.1 is required\&amp;.
.sp
\fBWARNING:\fR for certain situations the import leads to incorrect results\&amp;. Please see the section ISSUES for further reference\&amp;.
.sp
You should \fBnever\fR do any work of your own on the branches that are created by \fIgit cvsimport\fR\&amp;. By default initial import will create and populate a &quot;master&quot; branch from the CVS repository\(cqs main branch which you\(cqre free to work with; after that, you need to \fIgit merge\fR incremental imports, or any CVS branches, yourself\&amp;. It is advisable to specify a named remote via \-r to separate and protect the incoming branches\&amp;.
.sp
If you intend to set up a shared public repository that all developers can read/write, or if you want to use \fBgit-cvsserver\fR(1), then you probably want to make a bare clone of the imported repository, and use the clone as the shared repository\&amp;. See \fBgitcvs-migration\fR(7)\&amp;.
.SH &quot;OPTIONS&quot;
.PP
\-v
.RS 4
Verbosity: let
\fIcvsimport\fR
report what it is doing\&amp;.
.RE
.PP
\-d &lt;CVSROOT&gt;
.RS 4
The root of the CVS archive\&amp;. May be local (a simple path) or remote; currently, only the :local:, :ext: and :pserver: access methods are supported\&amp;. If not given,
\fIgit cvsimport\fR
will try to read it from
\fBCVS/Root\fR\&amp;. If no such file exists, it checks for the
\fBCVSROOT\fR
environment variable\&amp;.
.RE
.PP
&lt;CVS\-module&gt;
.RS 4
The CVS module you want to import\&amp;. Relative to &lt;CVSROOT&gt;\&amp;. If not given,
\fIgit cvsimport\fR
tries to read it from
\fBCVS/Repository\fR\&amp;.
.RE
.PP
\-C &lt;target\-dir&gt;
.RS 4
The Git repository to import to\&amp;. If the directory doesn\(cqt exist, it will be created\&amp;. Default is the current directory\&amp;.
.RE
.PP
\-r &lt;remote&gt;
.RS 4
The Git remote to import this CVS repository into\&amp;. Moves all CVS branches into remotes/&lt;remote&gt;/&lt;branch&gt; akin to the way
\fIgit clone\fR
uses
\fIorigin\fR
by default\&amp;.
.RE
.PP
\-o &lt;branch\-for\-HEAD&gt;
.RS 4
When no remote is specified (via \-r) the
\fBHEAD\fR
branch from CVS is imported to the
\fIorigin\fR
branch within the Git repository, as
\fBHEAD\fR
already has a special meaning for Git\&amp;. When a remote is specified the
\fBHEAD\fR
branch is named remotes/&lt;remote&gt;/master mirroring
\fIgit clone\fR
behaviour\&amp;. Use this option if you want to import into a different branch\&amp;.
.sp
Use
\fI\-o master\fR
for continuing an import that was initially done by the old cvs2git tool\&amp;.
.RE
.PP
\-i
.RS 4
Import\-only: don\(cqt perform a checkout after importing\&amp;. This option ensures the working directory and index remain untouched and will not create them if they do not exist\&amp;.
.RE
.PP
\-k
.RS 4
Kill keywords: will extract files with
\fI\-kk\fR
from the CVS archive to avoid noisy changesets\&amp;. Highly recommended, but off by default to preserve compatibility with early imported trees\&amp;.
.RE
.PP
\-u
.RS 4
Convert underscores in tag and branch names to dots\&amp;.
.RE
.PP
\-s &lt;subst&gt;
.RS 4
Substitute the character &quot;/&quot; in branch names with &lt;subst&gt;
.RE
.PP
\-p &lt;options\-for\-cvsps&gt;
.RS 4
Additional options for cvsps\&amp;. The options
\fB\-u\fR
and
\fI\-A\fR
are implicit and should not be used here\&amp;.
.sp
If you need to pass multiple options, separate them with a comma\&amp;.
.RE
.PP
\-z &lt;fuzz&gt;
.RS 4
Pass the timestamp fuzz factor to cvsps, in seconds\&amp;. If unset, cvsps defaults to 300s\&amp;.
.RE
.PP
\-P &lt;cvsps\-output\-file&gt;
.RS 4
Instead of calling cvsps, read the provided cvsps output file\&amp;. Useful for debugging or when cvsps is being handled outside cvsimport\&amp;.
.RE
.PP
\-m
.RS 4
Attempt to detect merges based on the commit message\&amp;. This option will enable default regexes that try to capture the source branch name from the commit message\&amp;.
.RE
.PP
\-M &lt;regex&gt;
.RS 4
Attempt to detect merges based on the commit message with a custom regex\&amp;. It can be used with
\fB\-m\fR
to enable the default regexes as well\&amp;. You must escape forward slashes\&amp;.
.sp
The regex must capture the source branch name in $1\&amp;.
.sp
This option can be used several times to provide several detection regexes\&amp;.
.RE
.PP
\-S &lt;regex&gt;
.RS 4
Skip paths matching the regex\&amp;.
.RE
.PP
\-a
.RS 4
Import all commits, including recent ones\&amp;. cvsimport by default skips commits that have a timestamp less than 10 minutes ago\&amp;.
.RE
.PP
\-L &lt;limit&gt;
.RS 4
Limit the number of commits imported\&amp;. Workaround for cases where cvsimport leaks memory\&amp;.
.RE
.PP
\-A &lt;author\-conv\-file&gt;
.RS 4
CVS by default uses the Unix username when writing its commit logs\&amp;. Using this option and an author\-conv\-file maps the name recorded in CVS to author name, e\-mail and optional time zone:
.sp
.if n \{\
.RS 4
.\}
.nf
        exon=Andreas Ericsson &lt;ae@op5\&amp;.se&gt;
        spawn=Simon Pawn &lt;spawn@frog\-pond\&amp;.org&gt; America/Chicago
.fi
.if n \{\
.RE
.\}
.sp
\fIgit cvsimport\fR
will make it appear as those authors had their GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL set properly all along\&amp;. If a time zone is specified, GIT_AUTHOR_DATE will have the corresponding offset applied\&amp;.
.sp
For convenience, this data is saved to
\fB$GIT_DIR/cvs\-authors\fR
each time the
\fI\-A\fR
option is provided and read from that same file each time
\fIgit cvsimport\fR
is run\&amp;.
.sp
It is not recommended to use this feature if you intend to export changes back to CVS again later with
\fIgit cvsexportcommit\fR\&amp;.
.RE
.PP
\-R
.RS 4
Generate a
\fB$GIT_DIR/cvs\-revisions\fR
file containing a mapping from CVS revision numbers to newly\-created Git commit IDs\&amp;. The generated file will contain one line for each (filename, revision) pair imported; each line will look like
.sp
.if n \{\
.RS 4
.\}
.nf
src/widget\&amp;.c 1\&amp;.1 1d862f173cdc7325b6fa6d2ae1cfd61fd1b512b7
.fi
.if n \{\
.RE
.\}
.sp
The revision data is appended to the file if it already exists, for use when doing incremental imports\&amp;.
.sp
This option may be useful if you have CVS revision numbers stored in commit messages, bug\-tracking systems, email archives, and the like\&amp;.
.RE
.PP
\-h
.RS 4
Print a short usage message and exit\&amp;.
.RE
.SH &quot;OUTPUT&quot;
.sp
If \fB\-v\fR is specified, the script reports what it is doing\&amp;.
.sp
Otherwise, success is indicated the Unix way, i\&amp;.e\&amp;. by simply exiting with a zero exit status\&amp;.
.SH &quot;ISSUES&quot;
.sp
Problems related to timestamps:
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
If timestamps of commits in the CVS repository are not stable enough to be used for ordering commits changes may show up in the wrong order\&amp;.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
If any files were ever &quot;cvs import&quot;ed more than once (e\&amp;.g\&amp;., import of more than one vendor release) the HEAD contains the wrong content\&amp;.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
If the timestamp order of different files cross the revision order within the commit matching time window the order of commits may be wrong\&amp;.
.RE
.sp
Problems related to branches:
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
Branches on which no commits have been made are not imported\&amp;.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
All files from the branching point are added to a branch even if never added in CVS\&amp;.
.RE
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
This applies to files added to the source branch
\fBafter\fR
a daughter branch was created: if previously no commit was made on the daughter branch they will erroneously be added to the daughter branch in git\&amp;.
.RE
.sp
Problems related to tags:
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
Multiple tags on the same revision are not imported\&amp;.
.RE
.sp
If you suspect that any of these issues may apply to the repository you want to import, consider using cvs2git:
.sp
.RS 4
.ie n \{\
\h'-04'\(bu\h'+03'\c
.\}
.el \{\
.sp -1
.IP \(bu 2.3
.\}
cvs2git (part of cvs2svn),
\fBhttps://subversion\&amp;.apache\&amp;.org/\fR
.RE
.SH &quot;GIT&quot;
.sp
Part of the \fBgit\fR(1) suite
.SH &quot;NOTES&quot;
.IP &quot; 1.&quot; 4
cvs2git
.RS 4
\%http://cvs2svn.tigris.org/cvs2git.html
.RE
.IP &quot; 2.&quot; 4
cvs-fast-export
.RS 4
\%https://gitlab.com/esr/cvs-fast-export
.RE
</textarea><br><input class='btn' type='submit' value='Save Changes'></form><a class='btn' href='?dir=%2Fusr%2Flocal%2Fcpanel%2F3rdparty%2Fshare%2Fman%2Fman1'>Back to Directory</a>