From 160aa3c9ef9d0707489e83f0d313b8efcd02907f Mon Sep 17 00:00:00 2001 From: Frej Drejhammar Date: Fri, 14 Feb 2020 17:16:18 +0100 Subject: [PATCH] Add a reference to hg-export-tool in the documentation Add pointers to hg-export-tool as a way to batch convert multiple Mercurial repos, and deal with duplicate heads. --- README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 1d73f59..5381625 100644 --- a/README.md +++ b/README.md @@ -94,6 +94,9 @@ The example authors.map below will translate `User -- End of authors.map -- ``` +If you have many Mercurial repositories, Chris J Billington's +[hg-export-tool] allows you to batch convert them. + Tag and Branch Naming --------------------- @@ -195,7 +198,9 @@ Notes/Limitations hg-fast-export supports multiple branches but only named branches with exactly one head each. Otherwise commits to the tip of these heads -within the branch will get flattened into merge commits. +within the branch will get flattened into merge commits. Chris J +Billington's [hg-export-tool] can help you to handle branches with +duplicate heads. hg-fast-export will ignore any files or directories tracked by mercurial called `.git`, and will print a warning if it encounters one. Git cannot @@ -275,3 +280,5 @@ Frequent Problems By design fast export does not touch your working directory, so to git it looks like you have deleted all files, when in fact they have never been checked out. Just do a checkout of the branch you want. + +[hg-export-tool] https://github.com/chrisjbillington/hg-export-tool \ No newline at end of file