darcs to mercurial migration

Hello, I'm switching from darcs to mercurial with some of my projects. I'd like to retain as much of the history as possible, what tools are there available for this? Günther

Günther Schmidt wrote:
Hello,
I'm switching from darcs to mercurial with some of my projects.
I'd like to retain as much of the history as possible, what tools are there available for this?
The cannonical revision control conversion tool is called tailor: http://progetti.arstecnica.it/tailor/ I haven't used it myself but have heard that it has some problems. Obviously you shouldn't delete your old tree until you are 100% satisfied that the new one is intact. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

On Thu, 06 May 2010 01:08:08 +0200, Günther Schmidt
Hello,
I'm switching from darcs to mercurial with some of my projects.
I'd like to retain as much of the history as possible, what tools are there available for this?
I recommend you darcs-fast-export and then use the/a mercurial fast-import. http://vmiklos.hu/project/darcs-fast-export/ Regards, -- Nicolas Pouillard http://nicolaspouillard.fr

On Fri, May 7, 2010 at 2:29 AM, Nicolas Pouillard < nicolas.pouillard@gmail.com> wrote:
On Thu, 06 May 2010 01:08:08 +0200, Günther Schmidt
wrote: Hello,
I'm switching from darcs to mercurial with some of my projects.
I'd like to retain as much of the history as possible, what tools are there available for this?
I recommend you darcs-fast-export and then use the/a mercurial fast-import.
Does this tool use libdarcs to read the darcs repository data and metadata? I see the claim that it is correct on the page you linked to:
Correct
darcs-fast-export produces correct results in any extreme cases. It has been tested with a collection of large darcs repos (called big-zoohttp://code.haskell.org/darcs/big-zoo/). And several testcases under the t/ directory.
The correctness argument is solely based on testing of the conversion on repositories? If so, how can it remain correct when darcs changes the format or semantics of its data? Tailor on the other hand, invokes the various vcs directly and transfers the diffs between the repositories. This seems inherently safer to me. Jason

On Fri, 7 May 2010 08:42:31 -0700, Jason Dagit
On Fri, May 7, 2010 at 2:29 AM, Nicolas Pouillard < nicolas.pouillard@gmail.com> wrote:
On Thu, 06 May 2010 01:08:08 +0200, Günther Schmidt
wrote: Hello,
I'm switching from darcs to mercurial with some of my projects.
I'd like to retain as much of the history as possible, what tools are there available for this?
I recommend you darcs-fast-export and then use the/a mercurial fast-import.
Does this tool use libdarcs to read the darcs repository data and metadata?
No I don't think so.
I see the claim that it is correct on the page you linked to:
Correct
darcs-fast-export produces correct results in any extreme cases. It has been tested with a collection of large darcs repos (called big-zoohttp://code.haskell.org/darcs/big-zoo/). And several testcases under the t/ directory.
The correctness argument is solely based on testing of the conversion on repositories? If so, how can it remain correct when darcs changes the format or semantics of its data?
Tailor on the other hand, invokes the various vcs directly and transfers the diffs between the repositories. This seems inherently safer to me.
Sure if tailor fits your needs, then perfect. But I find it slow and buggy, in particular be sure of checking that you have the same result in the end. Often it is not the case... -- Nicolas Pouillard http://nicolaspouillard.fr

Hi Günther, tehre is a fast darcs to git tool. Maybe you can convert to mercurial easily then. Ping me on irc (MarcWeber) or write back if you're interested. I'll digg the link up then. Marc Weber
participants (6)
-
Erik de Castro Lopo
-
Günther Schmidt
-
Ivan Miljenovic
-
Jason Dagit
-
Marc Weber
-
Nicolas Pouillard