Differences

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

--- svn [2008/02/12 14:49] – Added Tips & Tricks Section kleiner
+++ svn [2010/05/06 10:50] – damir
@@ Line 16: / Line 16: @@
 For group projects, it is better to use the common repository which is
   * for algo: <nowiki>svn+ssh://USERNAME@clusteralgo.epfl.ch/SVN/trunk</nowiki>
-  * for licos: <nowiki>svn+ssh://USERNAME@licos.epfl.ch/SVN/trunk</nowiki>
+  * for licos: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/svnlicos/</nowiki>
   * for lth: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/svnlth/</nowiki>
   * for lcm: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/svnlcm</nowiki>
+  * for arni: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/svnarni</nowiki>
 ===== Quick User Guide =====
@@ Line 139: / Line 140: @@
 ------------------------------------------------------------------------
 </code>
+===== Personal Repositories =====
+you can always create a personal repository in your homedir by doing:
+  - ssh into server: <code>ssh lth.epfl.ch</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 =====
+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 =====
-  - try to import into subversion ONLY the SOURCES and not the files that are generated from the sources;
+  - try to import into subversion ONLY the SOURCES and not the files that are generated from the sources; use [[makegallery|Makefiles]] for automatically generating dependent files from sources.
   - try to keep the repository as clean as possible. If the repository is shared among various users, it is better to meet once and agree on a common strategy for file/directories naming schemes;
   - Unless you have a good reason, do not commit incomplete or buggy files;