1GIT-ARCHIMPORT(1)                 Git Manual                 GIT-ARCHIMPORT(1)
2
3
4

NAME

6       git-archimport - Import an Arch repository into git
7

SYNOPSIS

9           git-archimport [-h] [-v] [-o] [-a] [-f] [-T] [-D depth] [-t tempdir]
10                          <archive/branch>[:<git-branch>] ...
11

DESCRIPTION

13       Imports a project from one or more Arch repositories. It will follow
14       branches and repositories within the namespaces defined by the
15       <archive/branch> parameters supplied. If it cannot find the remote
16       branch a merge comes from it will just import it as a regular commit.
17       If it can find it, it will mark it as a merge whenever possible (see
18       discussion below).
19
20       The script expects you to provide the key roots where it can start the
21       import from an initial import or tag type of Arch commit. It will
22       follow and import new branches within the provided roots.
23
24       It expects to be dealing with one project only. If it sees branches
25       that have different roots, it will refuse to run. In that case, edit
26       your <archive/branch> parameters to define clearly the scope of the
27       import.
28
29       git-archimport uses tla extensively in the background to access the
30       Arch repository. Make sure you have a recent version of tla available
31       in the path. tla must know about the repositories you pass to
32       git-archimport.
33
34       For the initial import git-archimport expects to find itself in an
35       empty directory. To follow the development of a project that uses Arch,
36       rerun git-archimport with the same parameters as the initial import to
37       perform incremental imports.
38
39       While git-archimport will try to create sensible branch names for the
40       archives that it imports, it is also possible to specify git branch
41       names manually. To do so, write a git branch name after each
42       <archive/branch> parameter, separated by a colon. This way, you can
43       shorten the Arch branch names and convert Arch jargon to git jargon,
44       for example mapping a "PROJECT--devo--VERSION" branch to "master".
45
46       Associating multiple Arch branches to one git branch is possible; the
47       result will make the most sense only if no commits are made to the
48       first branch, after the second branch is created. Still, this is useful
49       to convert Arch repositories that had been rotated periodically.
50

MERGES

52       Patch merge data from Arch is used to mark merges in git as well. git
53       does not care much about tracking patches, and only considers a merge
54       when a branch incorporates all the commits since the point they forked.
55       The end result is that git will have a good idea of how far branches
56       have diverged. So the import process does lose some patch-trading
57       metadata.
58
59       Fortunately, when you try and merge branches imported from Arch, git
60       will find a good merge base, and it has a good chance of identifying
61       patches that have been traded out-of-sequence between the branches.
62

OPTIONS

64       -h
65           Display usage.
66
67       -v
68           Verbose output.
69
70       -T
71           Many tags. Will create a tag for every commit, reflecting the
72           commit name in the Arch repository.
73
74       -f
75           Use the fast patchset import strategy. This can be significantly
76           faster for large trees, but cannot handle directory renames or
77           permissions changes. The default strategy is slow and safe.
78
79       -o
80           Use this for compatibility with old-style branch names used by
81           earlier versions of git-archimport. Old-style branch names were
82           category--branch, whereas new-style branch names are
83           archive,category--branch--version. In both cases, names given on
84           the command-line will override the automatically-generated ones.
85
86       -D <depth>
87           Follow merge ancestry and attempt to import trees that have been
88           merged from. Specify a depth greater than 1 if patch logs have been
89           pruned.
90
91       -a
92           Attempt to auto-register archives at
93           http://mirrors.sourcecontrol.net This is particularly useful with
94           the -D option.
95
96       -t <tmpdir>
97           Override the default tempdir.
98
99       <archive/branch>
100           Archive/branch identifier in a format that tla log understands.
101

AUTHOR

103       Written by Martin Langhoff <martin@catalyst.net.nz>.
104

DOCUMENTATION

106       Documentation by Junio C Hamano, Martin Langhoff and the git-list
107       <git@vger.kernel.org>.
108

GIT

110       Part of the git(7) suite
111
112
113
114
115Git 1.5.3.3                       10/09/2007                 GIT-ARCHIMPORT(1)