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
12

DESCRIPTION

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

MERGES

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

OPTIONS

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

AUTHOR

104       Written by Martin Langhoff <martin@laptop.org[1]>.
105

DOCUMENTATION

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

GIT

111       Part of the git(1) suite
112

NOTES

114        1. martin@laptop.org
115           mailto:martin@laptop.org
116
117        2. git@vger.kernel.org
118           mailto:git@vger.kernel.org
119
120
121
122Git 1.7.4.4                       04/11/2011                 GIT-ARCHIMPORT(1)