1git-archimport(1) 2================= 3 4NAME 5---- 6git-archimport - Import an arch repository into git 7 8 9SYNOPSIS 10-------- 11`git-archimport` [ -h ] [ -v ] [ -T ] [ -t tempdir ] 12 <archive/branch> [ <archive/branch> ] 13 14DESCRIPTION 15----------- 16Imports a project from one or more Arch repositories. It will follow branches 17and repositories within the namespaces defined by the <archive/branch> 18parameters suppplied. If it cannot find the remote branch a merge comes from 19it will just import it as a regular merge. If it can find it, it will perform 20a merge whenever possible. 21 22The script expects you to provide the key roots where it can start the import 23from an 'initial import' or 'tag' type of Arch commit. It will follow and import 24new branches within the provided roots. 25 26It expects to be dealing with one project only. If it sees 27branches that have different roots, it will refuse to run. In that case, edit your 28<archive/branch> parameters to define clearly the scope of the import. 29 30`git-archimport` uses `tla` extensively in the background to access the Arch repository. 31Make sure you have a recent version of `tla` available in the path. `tla` must 32know about the repositories you pass to `git-archimport`. 33 34For the initial import `git-archimport` expects to find itself in an empty 35directory. To follow the development of a project that uses Arch, rerun 36`git-archimport` with the same parameters as the initial import to perform incremental imports. 37of a project using Arch. 38 39Patch merge data from Arch is used to mark merges in GIT as well. GIT 40does not care much about tracking patches, and only considers a merge when a 41branch incorporates all the commits since the point they forked. The end result 42is that GIT will have a good idea of how far branches have diverged. So the 43import process does lose some patch-trading metadata. 44 45Fortunately, when you try and merge branches imported from Arch, 46GIT will find a good merge base, and it has a good chance of identifying 47patches that have been traded out-of-sequence between the branches. 48 49OPTIONS 50------- 51 52-h:: 53 Display usage. 54 55-v:: 56 Verbose output. 57 58-T:: 59 Many tags. Will create a tag for every commit, reflecting the commit 60 name in the Arch repository. 61 62-t <tmpdir>:: 63 Override the default tempdir. 64 65 66<archive/branch>:: 67 Archive/branch identifier in a format that `tla log` understands. 68 69 70Author 71------ 72Written by Martin Langhoff <martin@catalyst.net.nz>. 73 74Documentation 75-------------- 76Documentation by Junio C Hamano, Martin Langhoff and the git-list <git@vger.kernel.org>. 77 78GIT 79--- 80Part of the link:git.html[git] suite 81