I use the subversion repository to save code for the future. In my repository, I have the following folder structure:
\ |- Project1\ |- - Trunk\ |- - Branches\ |- - Tags\ |- Project2\ ....
This works for me, and I have big and small projects that I coded from high school in this repository. If, for example, I want to transfer the project that I encoded in Linux to Windows, I create a branch, which I, for example, call the Win32 port. And when I have version 1.0 of the project, I create a tag named 1.0.
Using this method, you can also set up backup scripts and save the backup in another place. (I use the cron job and some python scripts for this, but it all depends on which system the server uses.)
A book on subversion is available here freely: Link
ETroll
source share