Subversion in the Lab

Team: Guide to using Subversion in the lab is here (protected). Let me know how to make it more effective.


Alec Sent in this:

Under ‘basic procedure’ –

It’s a 4-step deal. Before you re-checkin your code, you should run
‘svn update’ to make sure that you know in what context your checkin
will be made, and more importantly to make sure that your code will
check in cleanly. If you don’t subversion will yell at you to do

If two people modify the same lines, svn will yell at the last
person to commit. If you make changes, think they work, and then
check in without testing the newer code, things could break.

Guide is updated accordingly.

Leave a Reply