From b2f6d28722b04c51d21a26f3aebec8c3e5aae72e Mon Sep 17 00:00:00 2001 From: Frej Drejhammar Date: Fri, 27 Jan 2012 20:06:07 +0100 Subject: [PATCH] Update documentation: The tool is no longer called hg-fast-import --- hg-fast-export.txt | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/hg-fast-export.txt b/hg-fast-export.txt index 0568597..9ab5bf4 100644 --- a/hg-fast-export.txt +++ b/hg-fast-export.txt @@ -18,7 +18,7 @@ Using hg-fast-export is quite simple for a mercurial repository : mkdir repo-git # or whatever cd repo-git git init - hg-fast-import.sh -r + hg-fast-export.sh -r Incremental imports to track hg repos is supported, too. @@ -44,13 +44,14 @@ User =User Notes/Limitations ================= -hg-fast-import supports multiple branches but only named branches with exaclty -one head each. Otherwise commits to the tip of these heads within branch -will get flattened into merge commits. +hg-fast-export supports multiple branches but only named branches with +exaclty one head each. Otherwise commits to the tip of these heads +within branch will get flattened into merge commits. -As each git-fast-import run creates a new pack file, it may be required -to repack the repository quite often for incremental imports (especially -when importing a small number of changesets per incremental import). +As each git-fast-import run creates a new pack file, it may be +required to repack the repository quite often for incremental imports +(especially when importing a small number of changesets per +incremental import). The way the hg API and remote access protocol is designed it is not possible to use hg-fast-export on remote repositories @@ -59,11 +60,12 @@ possible to use hg-fast-export on remote repositories Design ====== -hg-fast-import.py was designed in a way that doesn't require a 2-pass mechanism -or any prior repository analysis: if just feeds what it finds into -git-fast-import. This also implies that it heavily relies on strictly -linear ordering of changesets from hg, i.e. its append-only storage -model so that changesets hg-fast-import already saw never get modified. +hg-fast-export.py was designed in a way that doesn't require a 2-pass +mechanism or any prior repository analysis: if just feeds what it +finds into git-fast-import. This also implies that it heavily relies +on strictly linear ordering of changesets from hg, i.e. its +append-only storage model so that changesets hg-fast-export already +saw never get modified. Footnotes ========= -- 2.11.4.GIT