> svn checkout https://subversive.cims.nyu.edu/exact/svn-testor, to list the files in this directory, you can do:
> svn ls https://subversive.cims.nyu.edu/exact/svn-testYou should see the two files there (named "test" and "nontest").
> svn checkout --depth immediates \ https://subversive.cims.nyu.edu/exact/corelib2/trunk \ core2This creates a folder "core2" in your current local directory, with all the top level files and folders of Core Library.
> cd core2 > make zerothNow follow in instructions in the README file to get started.
> svn checkout --username yap https://subversive.cims.nyu.edu/exact/collab/macor (if you have a Courant account "yap")
> svn checkout https://yap@subversive.cims.nyu.edu/exact/collab/macNOTE: instead of using a command terminal, you could use an interface or app such as TortoiseSVN that is available on standard OS platforms.
> svn mkdir --username yap https://subversive.cims.nyu.edu/exact/collab/test
> ssh exact@access.cims.nyu.edu > su exact > htpasswd /home/svn/exact/auth/passwd [user-name]You will be asked to provide a password for the user. If [user-name] is already in the system, this will just update the password.
> ssh exact@access.cims.nyu.edu > gvim /home/svn/exact/auth/accessThe format for this access file is illustrated in Courant Subversion Info page
> svnadmin create /home/exact/svn/exactActually, this repository is locally administered by exact.
> cvs2svn -s /home/exact/svn/exact/corelib2 /home/exact/cvsroot/exact/corelib2 >c vs2svn -s /home/svn/exact/corelib2 /home/exact/cvsroot/exact/corelib2
>svnserve -d
> export SVN_EDITOR=vimProject developers can access the SVN through SSH protocol.
> export SVN_ROOT=svn+ssh://exact@access.cims.nyu.edu/home/exact/svn/exact
> svn co $SVN_ROOT/corelib2 [LOCALDIR]This will check out corelib2 to [LOCALDIR]. Although [LOCALDIR] is optional, it is useful to have (else you get a long path).
> svn resolved [filename] > svn commit [filename]
> svn add [file-or-dirname] > svn delete [file-or-dirname]
> svn move [orig-filename] [new-filename] > svn copy [source-filename] [destination-filename]
> cd NEWDIR > svn import [PATH=.] https://subversive.cims.nyu.edu/exact/collab/etc/etc.Note that PATH is optional (defaults to ".").
> svn co --depth immediates $(SVN_ROOT)/[foobar] [local-foobar]will checkout only the top-level files and folders to [local-foobar]. Instead of "immediates", you may want "files" or "empty". Default depth is "infinity". For selective checkouts, use "empty" or "immediates".
> svn up --set-depth infinity [local-foobar]/[folder1]Note that we call "svn up" not "svn co" here. If you want to find out the current depth of a folder foobar, do this:
> svn info [foobar] | grep "Depth"Nothing is printed if the Depth is infinity. Otherwise, it might print "Depth: immediates" or similar.
> svn log [foo]There are probably many output lines with this format:
r4321 | yap | 2019-02-01 15:32:49 -0400 (Sat, 01 Feb 2019) | 1 lineindicating revision No.4321 with one line change was commited by yap on Feb 1st, 2019.
> svn cat -r 4321 [foo] > foo-v4321or just look at this version on the screen using programs such as "more" or "less":
> svn cat -r 4321 [foo] | lessOf course, you can also update your latest version to v.4321:
> svn update -r 4321 [foo]
> svn diff [foo] > svn diff [foo] > [bar] > svn diff -r4321 [foo]The first form is simplest. The second form is used to re-direct the screen output into a file called [bar]. The third form is equivalent the first two forms provided the latest revision number of [foo] is 4321. Of course, you can replace 4321 by any older revision number.
> svn log [foo]From the output, suppose you decide to compare revisions 4321 and 4322. Then do:
> svn diff -r 4321:4322 [foo]