Cleaning up VDrift source tree

[joevenzon]

Was it usual for VDrift to use subversions locking in the past? Were your experiences positive?

I've used it at work for other projects where it was vital, but to be honest, I don't think anyone's really used it for VDrift. There are a small number of people working on anything at a given moment, so not many collisions. I think the forum has been used sometimes to communicate before beginning work on something that someone else checked in (although this has failed in the past as well). 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 would be happy to help testing this. I will deploy something later today or tomorrow.

Some tests:
* making a series of small changes to a .png image file, checking repository size change
* adding and then deleting the equivalent of a track's set of files, checking repository size change
* on a large repository like the entire vdrift data repo, make a single change to a .png file somewhere deep and check the time taken to make a git commit -a or svn ci
* on a large repo, test git workflow for branching, changing a .png file, and merging back in. test time and repository size change

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?