==== SVN Basics ==== Familiar with CVS? Nice! Just write `svn` instead of `cvs` in every command, and it will work as expected on 95% of commands. You can skip rest of this text :-) Never used CVS and any other version control systems? It's really simple! First, you need to make an INITIAL CHECKOUT. svn checkout [repository url] This will create your personal WORKING COPY of code in REPOSITORY. You can use 'co', it's a shorthand 'checkout' Then you modify code in your WC (modify, add/remove files)... It is only changes in your WC. If you want to add / remove / rename files and dirs - just let svn know: svn add newfile.ext svn remove unnededfile.ext svn rename oldfile.txt new_location/new_name.txt When you're done (or, at least, ready to show your code to other developers) you COMMIT your changes. svn ci EDITOR will pop-up, asking you to enter some description for your changes. there also will be a nice list of changed / added / removed files. You can use a short-hand for `commit` - `ci` (like in Check-In) Use `svn up` to catch up with most recent code in repository. So, your day should look like that: In the morning get latest revision from repository: svn up (a lot of work) Commit your changes to repository: svn ci Well, that's it. You can start using SVN! Congratulations! ;-)