GIT-CVSIMPORT(1) | Git Manual | GIT-CVSIMPORT(1) |
NAME¶
git-cvsimport - Salvage your data out of another SCM people love to hate
SYNOPSIS¶
git cvsimport [-o <branch-for-HEAD>] [-h] [-v] [-d <CVSROOT>]
[-A <author-conv-file>] [-p <options-for-cvsps>] [-P <file>]
[-C <git-repository>] [-z <fuzz>] [-i] [-k] [-u] [-s <subst>]
[-a] [-m] [-M <regex>] [-S <regex>] [-L <commit-limit>]
[-r <remote>] [-R] [<CVS-module>]
DESCRIPTION¶
WARNING: git cvsimport uses cvsps version 2, which is considered deprecated; it does not work with cvsps version 3 and later. If you are performing a one-shot import of a CVS repository consider using cvs2git[1] or cvs-fast-export[2].
Imports a CVS repository into Git. It will either create a new repository, or incrementally import into an existing one.
Splitting the CVS log into patch sets is done by cvsps. At least version 2.1 is required.
WARNING: for certain situations the import leads to incorrect results. Please see the section ISSUES for further reference.
You should never do any work of your own on the branches that are created by git cvsimport. By default initial import will create and populate a "master" branch from the CVS repository’s main branch which you’re free to work with; after that, you need to git merge incremental imports, or any CVS branches, yourself. It is advisable to specify a named remote via -r to separate and protect the incoming branches.
If you intend to set up a shared public repository that all developers can read/write, or if you want to use git-cvsserver(1), then you probably want to make a bare clone of the imported repository, and use the clone as the shared repository. See gitcvs-migration(7).
OPTIONS¶
-v
-d <CVSROOT>
<CVS-module>
-C <target-dir>
-r <remote>
-o <branch-for-HEAD>
Use -o master for continuing an import that was initially done by the old cvs2git tool.
-i
-k
-u
-s <subst>
-p <options-for-cvsps>
If you need to pass multiple options, separate them with a comma.
-z <fuzz>
-P <cvsps-output-file>
-m
-M <regex>
The regex must capture the source branch name in $1.
This option can be used several times to provide several detection regexes.
-S <regex>
-a
-L <limit>
-A <author-conv-file>
exon=Andreas Ericsson <ae@op5.se>
spawn=Simon Pawn <spawn@frog-pond.org> America/Chicago
git cvsimport will make it appear as those authors had their GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL set properly all along. If a time zone is specified, GIT_AUTHOR_DATE will have the corresponding offset applied.
For convenience, this data is saved to $GIT_DIR/cvs-authors each time the -A option is provided and read from that same file each time git cvsimport is run.
It is not recommended to use this feature if you intend to export changes back to CVS again later with git cvsexportcommit.
-R
src/widget.c 1.1 1d862f173cdc7325b6fa6d2ae1cfd61fd1b512b7
The revision data is appended to the file if it already exists, for use when doing incremental imports.
This option may be useful if you have CVS revision numbers stored in commit messages, bug-tracking systems, email archives, and the like.
-h
OUTPUT¶
If -v is specified, the script reports what it is doing.
Otherwise, success is indicated the Unix way, i.e. by simply exiting with a zero exit status.
ISSUES¶
Problems related to timestamps:
Problems related to branches:
Problems related to tags:
If you suspect that any of these issues may apply to the repository you want to import, consider using cvs2git:
GIT¶
Part of the git(1) suite
NOTES¶
- 1.
- cvs2git
- 2.
- cvs-fast-export
09/20/2024 | Git 2.46.1 |