From: Jan T. <jt...@gm...> - 2015-04-03 16:33:16
|
Guys, I've finished "testing" push of the git repo to github and I'd like to hear your comments opinions on whether the migration process could/shoul be improved -- I guess lots of you have more extensive experience with git than I have. The Kaldi organization is here: https://github.com/kaldi-asr/ and the testing repository is https://github.com/kaldi-asr/test-migration-2.git So far, I pushed only the trunk and stable branch -- I'm not sure if import of all sandboxes makes sense. For conversion, I used the svn2git: svn2git -v https://svn.code.sf.net/p/kaldi/code/ --trunk /trunk --branches /sandbox --notags --authors ../kaldi-devs-map-tmp.txt -m after this finished, I added line "fetch = stable:refs/remotes/svn/stable" into the .git/config file so it looks like this: [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [svn-remote "svn"] url = https://svn.code.sf.net/p/kaldi/code fetch = trunk:refs/remotes/svn/trunk fetch = stable:refs/remotes/svn/stable branches = sandbox/*:refs/remotes/svn/* [svn] authorsfile = ../kaldi-devs-map-tmp.txt then I did git svn fetch # to get the stable branch fetched git checkout -b "stable" "remotes/svn/stable" #to convert the remote to local git remote add origin https://github.com/kaldi-asr/test-migration-2.git #add target of push git push -u origin master #to push the master to github git push -u origin stable #to push the "stable" branch to github y. |