Using the SVN Repository
Sharing code across multiple computers (and among multiple contributors) can be a pain in the butt, unless you use a code repository, like SVN or Git. We'll be using SVN.
Our repository will be kept on marshall, my own research machine which you now have an account on (same username and password as in the Linux labs).
To get the repository on a new machine, you'll use svn co <URL> If you're on marshall, the URL can be file:///home/taylor/MLGroup/ If you're on a different machine, it should be svn+ssh://<username>@marshall.cs.usna.edu/home/taylor/MLGroup/ Using svn+ssh, it will ask you your password multiple times.
Now, you can go into that directory in your local filesystem, and make all the changes you like. When you commit those changes back to the repository, those changes will be reflected in EVERYBODY's filesystems the next time they update. So, the workflow for a session looks like this:
- Get any changes in the repository by running svn update.
- Make your changes. Deleting a file? Instead of just rm, use svn rm. Copying a file? Instead of just cp, use svn cp. Create a new file? Add it with svn add newfilename. Check to see what you've changed with svn status.
- Commit the changes, by running svn commit -m 'some short message to appear in the log file to tell us what you changed.'
Did something weird happen? Google it! The internet overfloweth with useful information about SVN.