1GIT-CVSIMPORT(1) Git Manual GIT-CVSIMPORT(1)
2
6 git-cvsimport - Salvage your data out of another SCM people love to
7 hate
8
10 git-cvsimport [-o <branch-for-HEAD>] [-h] [-v] [-d <CVSROOT>]
11 [-A <author-conv-file>] [-p <options-for-cvsps>] [-P <file>]
12 [-C <git_repository>] [-z <fuzz>] [-i] [-k] [-u] [-s <subst>]
13 [-a] [-m] [-M <regex>] [-S <regex>] [-L <commitlimit>]
14 [-r <remote>] [<CVS_module>]
15
17 Imports a CVS repository into git. It will either create a new
18 repository, or incrementally import into an existing one.
19 Splitting the CVS log into patch sets is done by cvsps. At least
21 version 2.1 is required.
22 You should never do any work of your own on the branches that are
24 created by git-cvsimport. By default initial import will create and
25 populate a "master" branch from the CVS repository´s main branch which
26 you´re free to work with; after that, you need to git merge incremental
27 imports, or any CVS branches, yourself. It is advisable to specify a
28 named remote via -r to separate and protect the incoming branches.
29
31 -v
32 Verbosity: let cvsimport report what it is doing.
33 -d <CVSROOT>
35 The root of the CVS archive. May be local (a simple path) or
36 remote; currently, only the :local:, :ext: and :pserver: access
37 methods are supported. If not given, git-cvsimport will try to read
38 it from CVS/Root. If no such file exists, it checks for the CVSROOT
39 environment variable.
40 <CVS_module>
42 The CVS module you want to import. Relative to <CVSROOT>. If not
43 given, git-cvsimport tries to read it from CVS/Repository.
44 -C <target-dir>
46 The git repository to import to. If the directory doesn´t exist, it
47 will be created. Default is the current directory.
48 -r <remote>
50 The git remote to import this CVS repository into. Moves all CVS
51 branches into remotes/<remote>/<branch> akin to the git-clone
52 --use-separate-remote option.
53 -o <branch-for-HEAD>
55 When no remote is specified (via -r) the HEAD branch from CVS is
56 imported to the origin branch within the git repository, as HEAD
57 already has a special meaning for git. When a remote is specified
58 the HEAD branch is named remotes/<remote>/master mirroring
59 git-clone behaviour. Use this option if you want to import into a
60 different branch.
61 Use -o master for continuing an import that was initially done by
63 the old cvs2git tool.
64 -i
66 Import-only: don´t perform a checkout after importing. This option
67 ensures the working directory and index remain untouched and will
68 not create them if they do not exist.
69 -k
71 Kill keywords: will extract files with -kk from the CVS archive to
72 avoid noisy changesets. Highly recommended, but off by default to
73 preserve compatibility with early imported trees.
74 -u
76 Convert underscores in tag and branch names to dots.
77 -s <subst>
79 Substitute the character "/" in branch names with <subst>
80 -p <options-for-cvsps>
82 Additional options for cvsps. The options -u and -A are implicit
83 and should not be used here.
84 If you need to pass multiple options, separate them with a comma.
86 -z <fuzz>
88 Pass the timestamp fuzz factor to cvsps, in seconds. If unset,
89 cvsps defaults to 300s.
90 -P <cvsps-output-file>
92 Instead of calling cvsps, read the provided cvsps output file.
93 Useful for debugging or when cvsps is being handled outside
94 cvsimport.
95 -m
97 Attempt to detect merges based on the commit message. This option
98 will enable default regexes that try to capture the name source
99 branch name from the commit message.
100 -M <regex>
102 Attempt to detect merges based on the commit message with a custom
103 regex. It can be used with -m to also see the default regexes. You
104 must escape forward slashes.
105 -S <regex>
107 Skip paths matching the regex.
108 -a
110 Import all commits, including recent ones. cvsimport by default
111 skips commits that have a timestamp less than 10 minutes ago.
112 -L <limit>
114 Limit the number of commits imported. Workaround for cases where
115 cvsimport leaks memory.
116 -A <author-conv-file>
118 CVS by default uses the Unix username when writing its commit logs.
119 Using this option and an author-conv-file in this format
120 exon=Andreas Ericsson <ae@op5.se>
124 spawn=Simon Pawn <spawn@frog-pond.org>
125 git-cvsimport will make it appear as those authors had their
128 GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL set properly all along.
129 For convenience, this data is saved to $GIT_DIR/cvs-authors each
131 time the -A option is provided and read from that same file each
132 time git-cvsimport is run.
133 It is not recommended to use this feature if you intend to export
135 changes back to CVS again later with git-cvsexportcommit(1).
136 -h
138 Print a short usage message and exit.
139
141 If -v is specified, the script reports what it is doing.
142 Otherwise, success is indicated the Unix way, i.e. by simply exiting
144 with a zero exit status.
145
147 Written by Matthias Urlichs <smurf@smurf.noris.de>, with help from
148 various participants of the git-list <git@vger.kernel.org>.
149
151 Documentation by Matthias Urlichs <smurf@smurf.noris.de>.
152
154 Part of the git(7) suite
155Git 1.5.3.3 10/09/2007 GIT-CVSIMPORT(1)