Differences

This shows you the differences between two versions of the page.

--- svn [2010/05/06 10:40] – damir
+++ svn [2010/05/06 10:52] – damir
@@ Line 1: / Line 1: @@
 ====== Subversion ======
-Subversion is an open-source control version system that is a compelling replacement for CVS. At least the client version is installed by default on all our Linux machines, and can be easily installed on Macs via [[http://fink.sf.org|fink]] or [[http://www.macports.org|macports]].
+Subversion is an open-source control version system that is a compelling replacement for CVS. At least the client version is installed by default on all our Linux machines, and can be easily installed on Macs via [[http://fink.sf.org|fink]] or [[http://www.macports.org|macports]].\\
-The basic idea is to keep a master copy of your source files in a //repository// where the subversion also keeps track of all the (committed) modifications to the files.
+The basic idea is to keep a master copy of your source files in a //repository// where the subversion also keeps track of all the (committed) modifications to the files. For editing a file, one have to check it out (e.g. get a local copy) from the repository.\\
-For editing a file, one have to check it out (e.g. get a local copy) from the repository. Once the editing is done, the modifications are committed back to the server. This allows more than one person (or the same person on many computers) to work on the same set of files because they are actually working on their local copy of the files.
+Once the editing is done, the modifications are committed back to the server. This allows more than one person (or the same person on many computers) to work on the same set of files because they are actually working on their local copy of the files.\\
-When a user commits his changes, the files he has been editing might have been changed (and committed) by another user in the mean while. In this case, subversion merges the changes automatically unless it detects a conflict (e.g. two user having changed the same line of code).
+When a user commits his changes, the files he/her has been editing might have been changed (and committed) by another user in the mean while. In this case, subversion merges the changes automatically unless it detects a conflict (e.g. two user having changed the same line of code).
 Everyone can create his own subversion repository in his homedirectory with the following command:
 <code>
@@ Line 141: / Line 141: @@
 </code>
-===== New Repository =====
+===== Personal Repositories =====
 you can always create a personal repository in your homedir by doing:
   - ssh into server: <code>ssh lth.epfl.ch</code>
-  - Create empty repository: <code>svnadmin create <name_of_repository></code>
+  - create an empty repository: <code>svnadmin create <name_of_repository></code>
+  - use the standard svn subcommands to checkout, list or commit to the repository
-general repositories, that needs to be available (under lth.epfl.ch/svn<LABNAME>/) can be created only by the sysadministrators.
+===== General Repositories =====
+General repositories, that needs to be available under <code>ssh+svn://lth.epfl.ch/svn<LABNAME>/<REPOSITORY></code> can be created only by the System Administrators.\\
+To create a general repository you need to send an email with these informations:
+  - name of the repository
+  - list of users that need access to it
+  - visibility:
+    - Private: The repository can be private (the only way to access it is through the svn commands)
+    - Public: The repository can be accessed through the web interface
 ===== Few general recommendations =====