@@ -9,14 +9,14 @@ git-archimport - Import a GNU Arch repository into Git
9
9
SYNOPSIS
10
10
--------
11
11
[verse]
12
- 'git archimport' [-h] [-v] [-o] [-a] [-f] [-T] [-D depth] [-t tempdir]
13
- <archive/ branch>[:<git-branch>] ...
12
+ 'git archimport' [-h] [-v] [-o] [-a] [-f] [-T] [-D < depth> ] [-t < tempdir> ]
13
+ <archive>/< branch>[:<git-branch>]...
14
14
15
15
DESCRIPTION
16
16
-----------
17
17
Imports a project from one or more GNU Arch repositories.
18
18
It will follow branches
19
- and repositories within the namespaces defined by the <archive/ branch>
19
+ and repositories within the namespaces defined by the <archive>/< branch>
20
20
parameters supplied. If it cannot find the remote branch a merge comes from
21
21
it will just import it as a regular commit. If it can find it, it will mark it
22
22
as a merge whenever possible (see discussion below).
@@ -27,7 +27,7 @@ import new branches within the provided roots.
27
27
28
28
It expects to be dealing with one project only. If it sees
29
29
branches that have different roots, it will refuse to run. In that case,
30
- edit your <archive/ branch> parameters to define clearly the scope of the
30
+ edit your <archive>/< branch> parameters to define clearly the scope of the
31
31
import.
32
32
33
33
'git archimport' uses `tla` extensively in the background to access the
@@ -42,7 +42,7 @@ incremental imports.
42
42
43
43
While 'git archimport' will try to create sensible branch names for the
44
44
archives that it imports, it is also possible to specify Git branch names
45
- manually. To do so, write a Git branch name after each <archive/ branch>
45
+ manually. To do so, write a Git branch name after each <archive>/< branch>
46
46
parameter, separated by a colon. This way, you can shorten the Arch
47
47
branch names and convert Arch jargon to Git jargon, for example mapping a
48
48
"PROJECT{litdd}devo{litdd}VERSION" branch to "master".
@@ -104,8 +104,8 @@ OPTIONS
104
104
Override the default tempdir.
105
105
106
106
107
- <archive/ branch>::
108
- Archive/ branch identifier in a format that `tla log` understands.
107
+ <archive>/< branch>::
108
+ <archive>/< branch> identifier in a format that `tla log` understands.
109
109
110
110
111
111
GIT
0 commit comments