I manage(d) another try :

hg --> git

This is currently in process. After 20h a little bit more than 180000 rev are exported to git.
Will wait some hours more to see what append, but so far so good.

git --> svn

This is the second step of my idea, in order to see if it's more faster with this conversion.
But have to wait the hg --> git finishing.

hg --> svn

Do another try with only the 30 last revisions with the same script (start revision configurable)

This work pretty well (just a little special case with [email protected] file).
And
$ diff -r svn-repos/ hg-repos/ > diff-result
$ cat diff-result | grep -v ".svn"

relevant results only show 2 empty folders in svn repos that are not still present in hg one :
offapi/drafts/
smoketestoo_native/com/

=========

So, without a really good surprise from the git --> svn conversion, it's clearly appear that it will not be manageable to import all history in svn [1].

So 2 options :

1) Import all the code without history. Have to check history into hg or git (have to wait if conversion goes well to the end)

2) Define a "good" starting revision, were good means :
* enough history in svn for pretty well being
* time reasonable computation (over-the-thumb-maths says [ :) ] approximately 250 commits/hour)


What do you think ?
++


[1] at least with my material, may a really BIG machine can lower time, but I doubt it will achieve it in reasonable time.


On 07/26/2011 03:53 PM, Michael Stahl wrote:
On 26.07.2011 13:51, florent andré wrote:
Hi there,

I actually run a script [1] on my local laptop and online svn serveur
that import the OOO340 hg to an svn trunk folder.

For now, it's work pretty well - get all history from OO340 - with good
commit log e.g. :
-------
Added:
ooo/trunk/trunk/xmloff/source/text/XMLTextColumnsContext.cxx
Modified:
ooo/trunk/trunk/xmloff/source/text/XMLTextPropertySetContext.cxx
ooo/trunk/trunk/xmloff/source/text/makefile.mk
Log:
changeset: 41:196d10f76091
user: mib
date: Thu Sep 21 09:48:30 2000 +0000
text column import
--------

But, as it simulate all svn commit, it's a little bit long...
Actually on 45/276930 revision.

well, the first 263206 revisions are the easy ones, because they're
linear :)

btw, what script are you using?

what will it do with merge revisions?

If the process goes well to the end, what could be the next step ?
Restart this script on the apache svn or extract some kind of svn dump
from my svn-serveur and import it ?

presumably it ought to be possible and easiest to import an SVN dump,
but i'm no SVN expert...

regards,
michael

Reply via email to