To use SVN at the command line, you can check out an existing folder (project) into your account. For instance to check out the folders starting at "fred" svn co https://svn.eg.bucknell.edu/cs208/f11/fred A fred directory should now appear. You should all have a directory with your username available in SVN under the directory for the current semester (s09,f09,s10,f10,...). You can create files and edit them in your account inside this directory. Let's say we add foo.txt to the fred directory. We need to tell SVN about foo.txt. SVN knows all things inside fred belong to the fred SVN project but it ignores them until you formally tell it to track them. cd fred svn add foo.txt You can add whole directories (and thus recursively add their contents) at one time by adding the directory name. Let's say we create a lab1 directory full of files inside the fred project. cd fred svn add lab1 This tells SVN about the files, it does NOT commit them. To actually commit files, you can commit them individually or commit the whole fred project. This next example commits just foo.txt. The -m adds a comment. If you leave it out, SVN will open emacs and force you to type one anyway. cd fred svn commit foo.txt -m "a comment must go here" Alternatively, we can commit what ever files we need as a group. cd fred svn commit -m "a comment must go here" For any team work, the instructor needs to create a team directory for you. From there, the team can checkout the project and begin working. SVN commands ------------ svn update gets latest updates from repository svn add filename tells svn to start tracking a new file (not a commit) svn commit -m "comment" tells svn to commit your latest changes svn log shows all commit logs with users, times, dates svn log filename/dirname shows all commit logs for that file/dir svn status shows the status of ALL files To see all conflicted files: svn status | grep C A conflicted one has a C to the left svn resolved filename marks the local file as better than the repo file it can then be committed