Ok, but the thing to note is that svn will keep old versions of a file around so you don't have to keep renaming it. In that way it is simpler to track changes (i.e. if something breaks in a new version of a file, and there is one and only one main file to contend with.
The tricky part is getting started with your local copy. So you have checked in HighVoltageControllerRefactoredISRReorganized.c, lets rename that to plain old HighVoltageController.c, put a tag on it V20090531 ) and everyone who cares can check out that version and we can synch back to that version later.
Then new revisions can get updated since the file exists and your local svn knows about it and can show you what has changed, as opposed to the tons of files with random filenames method
