Average Rating: 3.5/5.0Number of Ratings: 4Number of Reviews: 2
My Review of hgsvn |
||
You have not rated or reviewed this project.Click below to rate/review. | My Rating: | |
New Review |
This project is put into maintanance mode. No new features will be added and only really critical bugs will be fixed for now. If you're looking for a tool to work with Mercurial on top of Subversion please refer to hgsubversion, a hg extension that provides a more sophisticated approach.
When I took the challenge of working with Mercurial at Subversion repositories earlier this year, I looked at several candidates.
While hgsvn in general was in a working state, it was practically unusable for me. cloning the whole SVN repo from Trac-Hacks.org project (~8500 commits at that time) process time per commit seemed to increase between linear and exponential with every commit added to the local clone.
What seemed to become a true hybrid repo took twice the space of the svn-only or hg-only repo too.
And finally I had to restart the cloning every ~500 commits manually, after purging traces of latest failed transactions on both, the SVN and HG part.
All this was truly cumbersome and after ~20 hours and 2 retries starting from zero distributed over three or four successive days I finally gave up - almost finished.
hgsubversion did the whole cloning in less than 4 hours and only required 3 restarts. The rest is a different story.
When I took the challenge of working with Mercurial at Subversion repositories earlier this year, I looked at several candidates.
While hgsvn in general was in a working state, it was practically unusable for me. cloning the whole SVN repo from Trac-Hacks.org project (~8500 commits at that time) process time per commit seemed to increase between linear and exponential with every commit added to the local clone.
What seemed to become a true hybrid repo took twice the space of the svn-only or hg-only repo too.
And finally I had to restart the cloning every ~500 commits manually, after purging traces of latest failed transactions on both, the SVN and HG part.
All this was truly cumbersome and after ~20 hours and 2 retries starting from zero distributed over three or four successive days I finally gave up - almost finished.
hgsubversion did the whole cloning in less than 4 hours and only required 3 restarts. The rest is a different story.
This project is put into maintanance mode. No new features will be added and only really critical bugs will be fixed for now. If you're looking for a tool to work with Mercurial on top of Subversion please refer to hgsubversion, a hg extension that provides a more sophisticated approach.