|
Size: 348
Comment:
|
Size: 1825
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
Yoichi will write something here. |
It is a secret. Use the method below even from the control room computers. |
| Line 11: | Line 10: |
| You can do something like this: | There are two methods. Use the first method whenever possible. |
| Line 13: | Line 12: |
| {{{svn co svn+ssh://controls@nodus.ligo.caltech.edu/cvs/cds/caltech/svn/trunk/medm}}} | Checking out trunk/chans directory {{{ svn co --username svn40m https://nodus.ligo.caltech.edu:30889/svn/trunk/chans}}} The password is written in the standard place. Alternative way: {{{svn co svn+ssh://controls@nodus.ligo.caltech.edu/cvs/cds/caltech/svn/trunk/chans}}} == A sample session == '''Task''': Making your own directory under trunk/docs/ and put a draft of your potentially Nobel prize winning paper. (1) Make your own directory in the repository. {{{svn mkdir --username svn40m https://nodus.ligo.caltech.edu:30889/svn/trunk/docs/mydir}}} (2) Check out the directory you just created to your machine. {{{svn co --username svn40m https://nodus.ligo.caltech.edu:30889/svn/trunk/docs/mydir}}} (3) Change directory to the checked out directory. {{{cd mydir}}} (4) Put your draft into the directory. {{{cp /somewhere/ProofOfEverything.tex . }}} (5) Put the file under the svn's control. {{{svn add ProofOfEverything.tex}}} (6) Check it in to the svn repository. {{{svn ci -m "The first draft"}}} You have to put your comment after {{{-m}}} (7) Update your working copy. {{{svn up}}} (8) Delete the file from the repository because you realized your paper is totally a bullshit. {{{svn delete ProofOfEverything.tex}}} {{{svn ci -m "Oops, I was wrong"}}} However, your crappy paper can still be retrieved from the repository by requesting an old version, because all the history is recorded in the svn world. |
SVN! aka, Subversion!
We are in the process of installing the 40m directory tree into SVN version control.
Using SVN in the control room
It is a secret. Use the method below even from the control room computers.
Getting files from off-site
There are two methods. Use the first method whenever possible.
Checking out trunk/chans directory
svn co --username svn40m https://nodus.ligo.caltech.edu:30889/svn/trunk/chans
The password is written in the standard place.
Alternative way:
svn co svn+ssh://controls@nodus.ligo.caltech.edu/cvs/cds/caltech/svn/trunk/chans
A sample session
Task: Making your own directory under trunk/docs/ and put a draft of your potentially Nobel prize winning paper.
(1) Make your own directory in the repository.
svn mkdir --username svn40m https://nodus.ligo.caltech.edu:30889/svn/trunk/docs/mydir
(2) Check out the directory you just created to your machine.
svn co --username svn40m https://nodus.ligo.caltech.edu:30889/svn/trunk/docs/mydir
(3) Change directory to the checked out directory.
cd mydir
(4) Put your draft into the directory.
cp /somewhere/ProofOfEverything.tex .
(5) Put the file under the svn's control.
svn add ProofOfEverything.tex
(6) Check it in to the svn repository.
svn ci -m "The first draft"
You have to put your comment after -m
(7) Update your working copy.
svn up
(8) Delete the file from the repository because you realized your paper is totally a bullshit.
svn delete ProofOfEverything.tex
svn ci -m "Oops, I was wrong"
However, your crappy paper can still be retrieved from the repository by requesting an old version, because all the history is recorded in the svn world.