svn cheat sheet ( revised )

:: HINT COPY PASTE THE WHOLE TEST THE :: STANDS FOR COMMENTS IN CMD AND WILL NOT BE INCLUDED
::SOURCE:
::http://www.abbeyworkshop.com/howto/misc/svn01/

:: Setting up a Subversion Server under Windows

::ADD THE subversion bin directory to your PATH environmental variable
::


::ADD THE FOLLOWING ENVIRONMENTAL VARIABLE ENV
SVN_EDITOR
::AND THE VALUE the path to your favorite text editor with " " around the path !!!
"C:\Program Files\TextPad 5\textpad.exe"
pause

::GET HELP FOR SVN
svn help
pause

::GET HELP FOR SVN COMMAND
svn help revert
pause

::CREATE NEW REPOSITORY
svnadmin create d:/svn
pause

::EDIT THE USER NAME AND THE PASS IN THE REPOSITORY
START /MAX TEXTPAD "D:\svn\conf\svnserve.conf"
pause

::uncoment the following lines
[general]
anon-access = read
auth-access = write
password-db = passwd

::NOW MAKE THE DIRECTORY STRUCTURE
mkdir D:\svn\poc
mkdir D:\svn\poc\branches
mkdir D:\svn\poc\tags
mkdir D:\svn\poc\trunk

::uncomment the following lines ( replace for you users and passwords )
start /max textpad D:\svn\conf\passwd :
[users]
user1 = pass1
user2 = pass2

:: Start the subversion server by issuing this command in the command window:
:: THE CMD /C will start new version of the cmd.exe
start /max CMD /C "svnserve --daemon --root d:\SVN"


::JUST CHANGE TO THE D:\ DRIVE
d:

::NOW CHANGE TO THE DIRECTORY OF your project
:: ASSUMING THAT THE PROJECT IS BELLLOW THE D:\poc folder
cd D:\

::import for first time the project name
svn import poc file:///d:/svn/poc -m "Log Message"


::TO START USING THE VERSION CONTROL FEATURES CHECK OUT A PROJECT INTO YOUR LOCAL WORKING DIRECTORY, CREATE THE DIRECTORY TO WHICH
mkdir D:\temp\poc


::NOW GO TO THE WORKING DIRECTORY
mkdir D:\temp\poc
cd D:\temp\poc
::now checkout the poc project
svn checkout file:///d:/svn/poc/trunk poc

::TO GET A LIST OF THE CURRENT PROJECTS STORED IN A REPOSITORY, YOU CAN USE THE FOLLOWING COMMAND
svn list --verbose file:///svn/poc

svn status

::SUBVERSION DOES NOT TRACK THE VERSION NUMBERS FOR INDIVIDUAL PROJECTS AUTOMATICALLY. INSTEAD, IT TRACKS EACH UPDATE TO THE REPOSITORY AND TRACKS THE VERSIONS OF THESE UPDATES. TO CREATE INTERIM PROJECT RELEASES, YOU MUST CREATE "TAGS" WHICH IDENTIFY A SPECIFY VERSION OF A PROJECT. THIS IS DONE BY MAKING A VIRTUAL COPY OF A PROJECT IN THE TAGS DIRECTORY. FOR EXAMPLE
svn copy http://ysg/svn/poc/trunk http://ysg/svn/poc/tags/0.1.0 -m "Tagging the 0.1.0 release of the poc"

::THIS CREATES A SORT OF BOOKMARK OR SNAPSHOT WHICH RECORDS THE CURRENT STATE OF THE PROJECT. THEN, YOU CAN CHECKOUT THE PROJECT IN THIS STATE AT ANY TIME BY SIMPLY REFERRING TO THAT RELEASE NUMBER.

::TO GET A LIST OF THE RELEASES FOR A PROJECT.
svn list http://localhost/svn/repos/poc/tags 0.1.0/
ipconfig
svn list http://192.168.0.153/svn/repos/poc/tags 0.1.0/

The typical work cycle looks like this:

Update your working copy
svn update
Make changes
svn add
svn delete
svn copy
svn move
Examine your changes
svn status
svn diff
svn revert
Merge others' changes into your working copy
svn update
svn resolved
Commit your changes
svn commit

Update Your Working Copy

When working on a project with a team, you'll want to update your working copy to receive any changes made since your last update by other developers on the project. Use svn update to bring your working copy into sync with the latest revision in the repository.
$ svn update
U foo.c
U bar.c
Updated to revision 2.

L abc.c # svn has a lock in its .svn directory for abc.c
M bar.c # the content in bar.c has local modifications
M baz.c # baz.c has property but no content modifications
X 3rd_party # this dir is part of an externals definition
? foo.o # svn doesn't manage foo.o
! some_dir # svn manages this, but it's either missing or incomplete
~ qux # versioned as file/dir/link, but type has changed
I .screenrc # svn doesn't manage this, and is configured to ignore it
A + moved_dir # added with history of where it came from
M + moved_dir/README # added with history and has local modifications
D stuff/fish.c # this file is scheduled for deletion
A stuff/loot/bloo.h # this file is scheduled for addition
C stuff/loot/lump.c # this file has conflicts from an update
R xyz.c # this file is scheduled for replacement
S stuff/squawk # this file or dir has been switched to a branch