I’ve been evaluating SubGit with a colleague for some time now. It seems to be a decent tool if you have to use Subversion and can’t simply switch to Git completely. Nevertheless, we stumbled on a few (pretty annoying) things:
First, SubGit writes changes to the Git tree right into Subversion. As Subversion doesn’t know things like fast-forwards, this results in funny commits with messages like “trunk:$rev replaced by branch:$rev“. That kinda freaked out some colleagues of mine before we understood what’s really going on. A solution for this is the –no-ff flag when merging. You might just want to set it for the whole repository or even globally:
git config --add merge.ff false # add --global if you want to set it globally
Also, if you have a lot of Maven modules and want to ignore things like .classpath, .projects, target etc, this will result in SubGit trying to burn down your CPU to create a lovely .gitignore, for us with ~5500 lines. The solution is quite easy. Edit your $subgit_project_dir/subgit/config and add the following:
[translate] ignores = false
This simply tells SubGit to stop translating the Subversion ignores into Git ignores. Now you have to manage the ignores yourself but at least for us it’s worth it
Last but not least: Use the beta of version 3. It’s much more mature than the name suggests and for us it’s also more stable.
By the way, to get notified about new posts, just enter your email address on the right