[Accidentally sent privately by accident, meant to send to list.]
---------- Forwarded message ----------
From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Sun, May 15, 2011 at 1:02 PM
Subject: Re: Howto: Mercurial to Subversion migration
To: Yuri Z <vega113_at_gmail.com>
On Sun, May 15, 2011 at 11:45 AM, Yuri Z <vega113_at_gmail.com> wrote:
> Hello
> I am commiter in the Apache Wave project which was accepted into the Apache
> incubator. We already migrated our issues from the googlecode to the Jira
> and the next step is migration of the source code into the Apache SVN from
> Mercurial. I tried to google for information on mercurial to svn migration
> but couldn't find any simple (or even any working) solution. It would be a
> great help to our migration effort if someone from the Subversion team can
> advice on the best way to handle this.
> Thanks
> Yuri Zelikov
I'm not a member of the "team", just an experienced user. I was faced
with a similar project, recently, with git, and said "don't make me
hurt you".
The only way I know of is to do an export of your current codebase,
and import it into SVN. The same is true for git. tools to convert svn
to other, more distributed systems are common place. There are
compelling reasons that repository conversion is awkward, much like
converting bread back into wheat.
You might be able to do something useful with "hgsvn", linking a
working mercurial copy writing scripts to step through the mercurial
updates and committing them to a Subversion trunk. Complete
integration of all available mercurial or git properties to
Subversion, including unweaving interwoven and multiply sourced
component histories, though? It's like turning a sweater back into a
sheep's fleece, it's messy, and the sheep will be unhappy.
Received on 2011-05-15 22:30:15 CEST