8e170cdc1f95f21b184e014ed928b6db46a2e9c2
1 git-cvsimport-script(1)
2 =======================
3 v0.1, July 2005
5 NAME
6 ----
7 git-cvsimport-script - Import a CVS repository into git
10 SYNOPSIS
11 --------
12 'git-cvsimport-script' [ -o <branch-for-HEAD> ] [ -h ] [ -v ]
13 [ -d <CVSROOT> ] [ -p <options-for-cvsps> ]
14 <CVS_module> [ <GIT_repository> ]
17 DESCRIPTION
18 -----------
19 Imports a CVS repository into git. It will either create a new
20 repository, or incrementally import into an existing one.
22 Splitting the CVS log into patch sets is done by 'cvsps'.
23 At least version 2.1 is required.
25 OPTIONS
26 -------
27 -d <CVSROOT>::
28 The root of the CVS archive. May be local (a simple path) or remote;
29 currently, only the :pserver: access method is supported.
31 -o <branch-for-HEAD>::
32 The 'HEAD' branch from CVS is imported to the 'origin' branch within
33 the git repository, as 'HEAD' already has a special meaning for git.
34 Use this option if you want to import into a different branch.
36 Use '-o master' for continuing an import that was initially done by
37 the old cvs2git tool.
39 -p <options-for-cvsps>::
40 Additional options for cvsps.
41 The options '-x' and '-A' are implicit and should not be used here.
43 If you need to pass multiple options, separate them with a comma.
45 -v::
46 Verbosity: let 'cvsimport' report what it is doing.
48 <CVS_module>::
49 The CVS module you want to import. Relative to <CVSROOT>.
51 <type>::
52 Typically this matches the real type of <object> but asking
53 for a type that can trivially dereferenced from the given
54 <object> is also permitted. An example is to ask for a
55 "tree" with <object> being a commit object that contains it,
56 or to ask for a "blob" with <object> being a tag object that
57 points at it.
59 -h::
60 Print a short usage message and exit.
62 OUTPUT
63 ------
64 If '-v' is specified, the script reports what it is doing.
66 Otherwise, success is indicated the Unix way, i.e. by simply exiting with
67 a zero exit status.
70 Author
71 ------
72 Written by Matthias Urlichs <smurf@smurf.noris.de>, with help from
73 various participants of the git-list <git@vger.kernel.org>.
75 Documentation
76 --------------
77 Documentation by Matthias Urlichs <smurf@smurf.noris.de>.
79 GIT
80 ---
81 Part of the link:git.html[git] suite