Autogenerated man pages for v1.2.4-gce5b6

[git.git] / man1 / git-archimport.1

diff --git a/man1/git-archimport.1 b/man1/git-archimport.1
index 3f3a4b6..cfcd6e7 100755 (executable)
--- a/man1/git-archimport.1
+++ b/man1/git-archimport.1
@@ -23,7 +23,7 @@ git-archimport \- Import an Arch repository into git
 .SH "SYNOPSIS"
 
 .nf
-git\-archimport [\-h] [\-v] [\-o] [\-a] [\-f] [\-T] [\-D depth] [\-t tempdir]
+\fIgit\-archimport\fR [\-h] [\-v] [\-o] [\-a] [\-f] [\-T] [\-D depth] [\-t tempdir]
                <archive/branch> [ <archive/branch> ]
 .fi
 
@@ -33,7 +33,7 @@ git\-archimport [\-h] [\-v] [\-o] [\-a] [\-f] [\-T] [\-D depth] [\-t tempdir]
 Imports a project from one or more Arch repositories\&. It will follow branches and repositories within the namespaces defined by the <archive/branch> parameters supplied\&. If it cannot find the remote branch a merge comes from it will just import it as a regular commit\&. If it can find it, it will mark it as a merge whenever possible (see discussion below)\&.
 
 
-The script expects you to provide the key roots where it can start the import from an initial import or tag type of Arch commit\&. It will follow and import new branches within the provided roots\&.
+The script expects you to provide the key roots where it can start the import from an \fIinitial import\fR or \fItag\fR type of Arch commit\&. It will follow and import new branches within the provided roots\&.
 
 
 It expects to be dealing with one project only\&. If it sees branches that have different roots, it will refuse to run\&. In that case, edit your <archive/branch> parameters to define clearly the scope of the import\&.