Last year, me and the other programmer (Superdan) just did it cheesy-style, comment on what you did to the program at the top of the .bsx file, save it based on the date (12-05-03.bsx). All saved in one directory, periodically back it up, fin.
This year though, we have several programmers, and yeah, I see that a problem could arise.
One possible solution I just though of, which is way overkill, and may not work for everyone, is to design a website, that would be run from the localhost (whatever computer you use to program on), and you simply "upload" the new file(s), and a small description of what was changed, who changed it, and if it was loaded into the robot, whatever.
Yes, it's completely overkill, but being snowed in (sort of) makes you think too much
.
I'm sure a similar program could be written in C++/Java, but I don't know either well enough to do something like, whereas PHP/HTML I've done a bit of work in, so maybe I'll try to start some sort of crazy Version Control software.
If anyone sees any huge flaws in my idea, please, point them out, cause it's late, I've been up all day, and I'm starting to suffer from "Cabin Fever". Stupid snow and lack of friends/sledding hills that live within walking distance...