as a merge whenever possible (see discussion below).
The script expects you to provide the key roots where it can start the import
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.
+from an 'initial import' or 'tag' type of Arch commit. It will follow and
+import new branches within the provided roots.
-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.
+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.
Make sure you have a recent version of `tla` available in the path. `tla` must
know about the repositories you pass to `git-archimport`.
For the initial import `git-archimport` expects to find itself in an empty
directory. To follow the development of a project that uses Arch, rerun
Make sure you have a recent version of `tla` available in the path. `tla` must
know about the repositories you pass to `git-archimport`.
For the initial import `git-archimport` expects to find itself in an empty
directory. To follow the development of a project that uses Arch, rerun
does not care much about tracking patches, and only considers a merge when a
branch incorporates all the commits since the point they forked. The end result
does not care much about tracking patches, and only considers a merge when a
branch incorporates all the commits since the point they forked. The end result
import process does lose some patch-trading metadata.
Fortunately, when you try and merge branches imported from Arch,
import process does lose some patch-trading metadata.
Fortunately, when you try and merge branches imported from Arch,