What I can tell you is that I do not know for sure how to do it :) On Sat, May 6, 2017 at 2:29 PM, Peter Uhnak <i.uhnak@gmail.com> wrote:
Hi,
the code generated from the migration tool can be used by both Iceberg and GitFileTree (because they both use FileTree format to store the code).
So you can just migrate your code, install Iceberg and you're good to go. I can write a blog post about this I guess...
(maybe I could add the migration to icerberg, but I need to check if libgit2 can do the importing part)
Peter
On Sat, May 06, 2017 at 08:56:51AM +0200, Stephane Ducasse wrote:
Peter
what is the path to migrate MCZ project from SmalltalkHub to github and that we can use them with Iceberg.
Stef
On Sat, May 6, 2017 at 8:44 AM, Stephane Ducasse < stepharo.self@gmail.com> wrote:
this is super cool!!!! Tx a lot peter for that.
On Thu, May 4, 2017 at 2:32 PM, Peter Uhnák <i.uhnak@gmail.com> wrote:
With Iceberg knocking on the door, migration from SmalltalkHub to Git(Hub/Lab/...) has become relevant once more.
And that's why I wrote git-migration tool https://github.com/peteru hnak/git-migration to help you move on to greener pastures.
Among other things described in the too-long-didn't read README:
the tool will generate git-fast-import (a special format for fast git imports) file that can be easily and quickly applied on your git repository. All commits are preserved in their proper order, and merges (commits with multiple parents) are also converted to git merges.
So far I've tested it on my custom intentionally broken repository, and PolyMath.
PolyMath has 784 commits in 74 packages; it took Pharo about 3 minutes to process all SmalltalkHub commits and generate 87MB file; git then imported the file in less than a second.
(Git history of PolyMath in GitKraken)
the tool also provides you with a bunch of visualizations that can help you analyze your SmalltakHub history and investigate problems.
(trees of all packages in the PolyMath repository)
More things could be desired (e.g. even better performance), so feel free to open issues, ideally with pull requests. ;)
Peter