I've got an SVN repository of a PHP site and the last programmer didn't use source control properly. As a result, only code since I started working here is in the Repo. I have a bunch of old copies of the full code base saved in files as backups but they're not in source control. I don't know why most of the copies were saved nor do I have any reasonable way to tag them to a version number. I do have the dates the backups were made, all backups have proper file system timestamps.Due to upgrades to the frameworks and database drivers involved, the old code is quite defunct; it no longer works on the current server configuration. However, the previous programmers had some unique logic, so I hate to be completely without old copies to refer to what on earth they were doing.Should I keep this stuff in version control? How? Wall off the old code in separate Tags/branches?
Should I add old code into my repository?
version control;svn
If you have reasonable timestamps on each of these working versions then perhaps you can check them in one at a time until you get to the most recent version of the codebase, your latest changes.The problem with the Tag approach like everybody else suggests is that you will lose changeset history on each file and this will make comparisons between older versions of the code more difficult.