User Tools

Site Tools


svn

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
svn [2010/05/06 08:35] damirsvn [2011/02/18 14:14] cangiani
Line 1: Line 1:
 ====== Subversion ====== ====== 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: Everyone can create his own subversion repository in his homedirectory with the following command:
 <code> <code>
Line 10: Line 10:
 </code> </code>
 where ''DIRECTORY_NAME'' name could be for example ''/home/cangiani/SVN'' where ''DIRECTORY_NAME'' name could be for example ''/home/cangiani/SVN''
- 
- 
 ===== Standard connection methods for our central repositories ===== ===== Standard connection methods for our central repositories =====
  
 For group projects, it is better to use the common repository which is 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 algo: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/repos/algo/REPONAME/</nowiki> 
-  * for licos: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/svnlicos/</nowiki> +  * for licos: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/repos/licos/REPONAME/</nowiki> 
-  * for lth: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/svnlth/</nowiki> +  * for lth: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/repos/lth/REPONAME</nowiki> 
-  * for lcm: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/svnlcm</nowiki> +  * for lcm: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/repos/lcm/REPONAME/</nowiki> 
-  * for arni: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/svnarni</nowiki>+  * for arni: <nowiki>svn+ssh://USERNAME@lth.epfl.ch/repos/arni/REPONAME</nowiki
 + 
 +Where ''REPONAME'' is the name of the repository. You can see a list of repositories with ''ls''.  
 +For example: 
 + 
 +<code> 
 +|~>ls /repos/lth 
 +CDMA introsc scaling 
 +CS iryna scripts 
 +LDPCequal isit05 shortcourse 
 +SourceCoding it2010-11 signalpc 
 +SourceCodingBP iterations sim 
 +aaaaa kr sim.donotuse 
 +abdel ldlc sim1 
 +alsan ldpcdemo sim_zip 
 +ara leshouches sparsematrices 
 +aref limex stability 
 +book mac statphys 
 +cap matlabde statphys2010-11 
 +cdi maxup subroutines 
 +comm maxwell talks 
 +commnet minsum temp 
 +consensus mobility test 
 +corrdecay ncaref test1 
 +coupled netflix testacl 
 +cyclecodes networkcoding testacl1 
 +densevol newintrosc testdamir 
 +density_evolution paris05 thesiskorada 
 +dsp2010-11 pdc treereconstruction 
 +errorfloor polargaussian turbo 
 +flipping polarization turboweight2 
 +gf pspin twod 
 +girthvsdiam puncturing vinodhPhD 
 +gossip racodes vish 
 +graphreconstruction ratesplitting weight_conc 
 +ibm samplede 
 +</code>
  
 ===== Quick User Guide ===== ===== Quick User Guide =====
Line 141: Line 175:
 </code> </code>
  
-===== New Repository - Quick Guide =====+===== Personal Repositories ===== 
 + 
 +you can always create a personal repository in your homedir by doing: 
   - ssh into server: <code>ssh lth.epfl.ch</code>   - ssh into server: <code>ssh lth.epfl.ch</code>
-  - Create empty repository: <code>svnadmin create /svnlcm/<name_of_repository></code> (replace ''svnlcm'' with ''svnlth'', ''svnlicos'' as needed) +  - create an empty repository: <code>svnadmin create <name_of_repository></code>  
-  - From the client machine do a checkout, e.g: <code>svn co svn+ssh://lth.epfl.ch/svnlcm/<name_of_repository></code> +  - use the standard svn subcommands to checkout, list or commit to the repository 
-  - Copy or create files in this empty "local copy"+ 
-  - Add the new files to the repository: <code>svn add *</code> + 
-  - Commit (i.e., check in): <code>svn ci</code>+===== 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 ===== ===== Few general recommendations =====
svn.txt · Last modified: 2012/02/17 14:54 by damir