The Subversion repositories are stored and accessible on https://svn.iac.ethz.ch. You can ask for a user repository which will be only accessible by you. Or you can ask for a project repository which can be accessible by other users too. If your repository should be accessible without authentication (anonymous read access) ask for a public repository. Send a mail to urs.beyerle@env.ethz.ch to ask for a new repository.
For a project and public repository the following information is needed:
It's possible to enable email notification for repositories. If enabled, the users will get an email in case something was changed in the repository (file added, file modified, etc).
https://svn.iac.ethz.ch/repos/users/username
- this is the standard repository for a user
https://svn.iac.ethz.ch/repos/projects/projectname
- each project has its own repository
https://svn.iac.ethz.ch/repos/pub/projectname
- each project has its own repository
You can browse the repositories with a normal web browser. Two different views are available:
With WebDAV you can access the repository like a normal file system. If you remove, add or modify a file, a new revision of your repository is automatically created.
webdavs://iacsvn.ethz.ch/repos/path_to_your_repo
svn co https://svn.iac.ethz.ch/repos/users/beyerleu my_repoNow you have a so called working copy of your personal repository in the folder
my_repo
svn co https://svn.iac.ethz.ch/repos/users/beyerleu/matlab matlab
svn co https://svn.iac.ethz.ch/repos/projects/projectname projectname
svn co --revision 14 https://svn.iac.ethz.ch/repos/projects/projectname projectname-r14
cd my_repo # or cd projectname
svn info
touch testfile svn add testfile
svn status svn st
svn delete testfile
svn cp file copy_of_the_file
svn mv oldfile newfile
svn ci -m "testfile created"If you don't define a comment with the option -m, your default editor will be open to let you write a comment. You can define your default editor by setting the
$EDITOR
environment variable.
svn diff svn diff <file>Comparing current folder content with content of an older revision (-r 100) or from 2010-01-15
svn diff -r 100 svn diff -r {2010-01-15}
svn update svn up
svn st -u
<file>
to version stored in the repo (un-do local edits in your working copy) svn revert <file>
<file>
to an older revision, for example revision 100: svn up -r 100 <file>
svn up -r 80or to the status of a specific date, for example 2010-01-15
svn -r {2010-01-15} up
svn co -r {2009-10-01} https://beyerleu@svn.iac.ethz.ch/repos/users/beyerleu my_repo.2009-10-01
svn propset svn:executable ON <file>
svn logOnly list logs for a specific file
svn log <file>
svn help svn help <subcommands> svn help cp
For more info about common tasks see http://svnbook.red-bean.com/en/1.4/svn.tour.cycle.html
Per default the Linux svn client is caching your password. This can be quite useful, since you don't have to type in your password every time you check out or commit a change. However, the password is stored in cleartext. Per default the folder storing the password ~/.subversion/auth
is only readable by you. You should definitely not change this.
Nevertheless, I would recommend to disable the password caching of the svn command completely by uncomment the following line in your ~/.subversion/config
file.
store-passwords = no
Afterwards, remove all stored svn passwords with
rm ~/.subversion/auth/svn.simple/*