Here are three basic tasks one may use SubGit for. Follow links below to get detailed documentation. In case something is not clear or you experience a difficulty, do not hesitate to contact us at email@example.com email address.
1. Quick How-To
Follow quick how-to set up Git/SVN mirror. These instructions would be sufficient to set up a Git mirror for most of the standard SVN projects.
Create a Git repository that will mirror remote Subversion repository accessible over network. Translation from Git to Subversion is initiated on push operation and translation from Subversion to Git is performed asynchronously in background.
Install SubGit into Subversion repository on the server side. Both Subversion and Git repositories reside on the same server. Translation in both directions is initiated instantly and introduces minimal overhead.
Perform one-time import of an existing Subversion project into Git. No synchronization is required.
In order to set up SubGit to work seamlessly with Gerrit, you’d need to install SubGit plugin for Gerrit and follow standard instructions to configure Git/SVN mirror or import your SVN project into Gerrit managed Git repository.
For Atlassian Bitbucket Server Git repositories management tool (formerly known as Atlassian Stash) we offer SubGit wrapped as an add-on. Visit SVN Mirror Add-On for Bitbucket Server page for more details. Follow instructions on creating bi-directional mirror of your existing Subversion project and importing your Subversion project into Bitbucket Server.
From the very beginning, SubGit was developed as an alternative to Git-Svn, so quite naturally SubGit does resolve many of the Git-Svn limitations.
Brief information on SubGit versions history and new features available in each version since version 1.0.
Without a registration you may use SubGit for evaluation period of 30 days. Would you like to extend this evaluation period, feel free to contact us at firstname.lastname@example.org.