Switch to git as the NetarchiveSuite SCM

We currently use Subversion (svn) as Source Control Management (SCM) system in the NetarchiveSuite project. This has a number of shortcomings, the most significant being:

• Weak support for versioning of folders. The most pronounced symptom of this is that folder renaming or moving can be difficult when the changes need to be merged back. The infamous Tree conflicts often occur here.
• Weak support for branching. The problem is again that refactorings are difficult and can lead to insolvable tree conflicts.

We should therefore consider moving to git as the NetarchiveSuite SCM.

We migrated the Bitrepository to git a month ago and this hasn't caused any significant problems.

For a more detailed list of pro/cons see:

• http://thinkvitamin.com/code/why-you-should-switch-from-subversion-to-git/
• http://whygitisbetterthanx.com/

Major changes/problems

• As git use sha-1 hash's as revision numbers, we lose svns human readable, sequential revision numbers. See what is the git equivalent for revision number? for discussion of this issue.
• Our current usage of svn properties in the file headers, as the pre-commit hooks we use in svn isn't supported. In git this information needs to be accessed directly in git.