Comment Re:Different strokes for different folks (Score 1) 378
... As long as you can get them to commit the changes, you're ensured that those changes are now on a server/machine that is getting backed up and taken care of.
I solved this problem at my last job by setting up a testing environment that pulled changes from the repository. It helped that the system being worked on was large and complex enough that it would be a pain in the ass to try to set up a local copy on your own machine for testing, so everyone would just use the test server, which, in order to use, required a commit to the development repository so the test server could pull the commit and put it into testing (in fact, this was accomplished in the post-commit script). The SVN server would receive commits from every developer continually through the day, and even the tiny change always had at least one "backup" somewhere.
The only downside to this is commit log pollution, but it wasn't really a problem -- these tiny commits would just have an empty log comment that could be easily ignored, and when things were finally working well, the changes would then be merged into the main branch with a properly documented commit.