Cleaning up VDrift source tree

[BiGBeN87]

I just finished cloning the svn and uploading it to github:

https://github.com/bigben87/VDrift-Data

So fork me on GitHub and do your tests! I will go to sleep now, but I have an early measurement already:
1.6 GiB of binary data with 900 revisions weigh in at 1,.7 GiB .git directory. So size considerations seem for no reason.

The problem we run into on VDrift most often is just someone changing a file that someone else had previously changed, and then that person being like "wtf, why did you change that?", but they weren't working on it simultaneously, so that's a different problem with some different solution.

I have witnessed this behavior in some other projects to. I always felt that a forum is the wrong place to talk about code, however. GitHub's pull-request implementation encourages discussion on specific changes throughout the whole development process. Maybe that already gives enough structure on the right place to prevent wtf-commits in the future.

Some tests:
* making a series of small changes to a .png image file, checking repository size change

PNGs are usually compressed. Therefore Git will add almost the full file size.

Considerations:
* for the size and time tests, how does running git gc affect the results? would this need to be a regular manual maintenance for a github hosted repo?

Git automatically invoked gc after cloning the svn: https://gist.github.com/1261544 Therefore I can not test it now.