Migrating from SVN to GIT. It has been done before, …, but has it?

Recent changes in policy re-ignited our quest to migrate away from Subversion to GIT, as GIT is much more powerful for branching and merging e.t.c.

Migrating from Subversion is not very hard; you just start over, right? So you want to lose all the project history? I don’t think so.

The migrated GIT-repository should include all history, all commit messages, all tags, all branches. How do you do that? Continue reading “Migrating from SVN to GIT. It has been done before, …, but has it?”

Using multiple versions of SVN – automatically – transparently

[UPDATE] This post is useless when you upgrade Xcode to version 5.0. If you use version 4 or you’re using a linux environment with svn 1.6 and 1.7 simultaneously; read on :) [/UPDATE]

So you have these projects in your development tree, these are probably managed by the version of Subversion as used on your mac – which with a very high probability would be version 1.6. But now and again, you might find yourself with a Subversion 1.7 project you received from someone else. Your mac will then shout something like this;

Shell outputsvn: The path '.' appears to be part of a Subversion 1.7 or greater
working copy. Please upgrade your Subversion client to use this
working copy.

If – like me – you are NOT prepared to switch to SubVersioN 1.7 entirely, then read on :)

Continue reading “Using multiple versions of SVN – automatically – transparently”

Sending an email upon SVN-commit

When you work with a group of people on the same projects, the larger the group gets, the more difficult the task of keeping everybody informed. So why not do this automatically? Send an e-mail upon an SVN commit. Here’s how I do it. Continue reading “Sending an email upon SVN-commit”

Confidental Infomation
stop spam mail