Subversion Tutorial - Revision history

Alexander Kogtenkov: Replaced the template "nota" with "note".

2019-05-21T06:04:51Z

Replaced the template "nota" with "note".

Titleistfour: /* Checkout your working copy */

2006-09-28T11:37:16Z

‎Checkout your working copy

Titleistfour at 11:34, 28 September 2006

2006-09-28T11:34:24Z

Titleistfour: /* Create the repository */

2006-09-28T11:15:49Z

‎Create the repository

Titleistfour: /* Importing into a repository */

2006-09-28T11:12:16Z

‎Importing into a repository

Manus: Tutorial for SVN

2006-04-05T22:12:19Z

Tutorial for SVN

Show changes

@@ Line 165: / Line 165: @@
 ; C foo : File foo received Conflicting changes from the server. The changes from the server directly overlap your own changes to the file. No need to panic, though. This overlap needs to be resolved by a human (you); we discuss this situation later in this chapter.
 </div>
-{{nota|CVS user: do not use '''svn -n update''' to check the status of your working copy, use svn status for that. <br/>This is much more powerful}}
+{{note|CVS user: do not use '''svn -n update''' to check the status of your working copy, use svn status for that. <br/>This is much more powerful}}
 === svn resolved ===
@@ Line 374: / Line 374: @@
 I would advice the second method, because if case of large folder to "branch", this will avoid copying all the files and folder in your working directory (indeed, often when you create a branch, it is for later or other).
-{{nota|Cheap Copies : Subversion's repository has a special design. When you copy a directory, you don't need to worry about the repository growing huge—Subversion doesn't actually duplicate any data. Instead, it creates a new directory entry that points to an existing tree. }}
+{{note|Cheap Copies : Subversion's repository has a special design. When you copy a directory, you don't need to worry about the repository growing huge—Subversion doesn't actually duplicate any data. Instead, it creates a new directory entry that points to an existing tree. }}
 === Working with Your Branch ===
@@ Line 415: / Line 415: @@
    Last Changed Date: 2005-09-30 09:27:38 -0700 (Fri, 30 Sep 2005)
-'''Nota:''' The Key Concepts Behind Branches
+'''Note:''' The Key Concepts Behind Branches
 # Unlike many other version control systems, Subversion's branches exist as normal filesystem directories in the repository, not in an extra dimension. These directories just happen to carry some extra historical information.
@@ Line 649: / Line 649: @@
   svn revert src/dating/date.txt
-{{Nota|it is recommended that you use the --dry-run to simulate the merging, this way you will see which files will be changed, added, conflicted...}}
+{{Note|it is recommended that you use the --dry-run to simulate the merging, this way you will see which files will be changed, added, conflicted...}}
   if you want to merge all differences from "project/trunk/src" into "v1/src"

@@ Line 102: / Line 102: @@
 * svn checkout URL  or  svn co URL
   For instance
-  svn co svn://username@svn_svr_address/test/
+  svn co svn://username@svn_svr_address/svn/test/
   svn co http://username@svn_svr_address/svn/test/

@@ Line 32: / Line 32: @@
 In a repository you will find a few folders and files
- '''conf'''
+<div style="padding-left: 30px">
-    A directory containing repository configuration files.
+;conf : A directory containing repository configuration files.
- '''dav'''
+;dav : A directory provided to Apache and mod_dav_svn for their private housekeeping data.
-    A directory provided to Apache and mod_dav_svn for their private housekeeping data.
+;db : Where all of your versioned data resides. This directory is either a Berkeley DB environment (full of DB tables and other things), or is an FSFS environment containing revision files.
- '''db'''
+;format :  A file whose contents are a single integer value that dictates the version number of the repository layout.
-    Where all of your versioned data resides. This directory is either a Berkeley DB environment (full of DB tables and other things), or is an FSFS environment containing revision files.
+;hooks : A directory full of hook script templates (and hook scripts themselves, once you've installed some).
-  '''format'''
+;locks : A directory for Subversion's repository locking data, used for tracking accessors to the repository.
-    A file whose contents are a single integer value that dictates the version number of the repository layout.
+;README.txt : A file which merely informs its readers that they are looking at a Subversion repository.
- '''hooks'''
+</div>
-    A directory full of hook script templates (and hook scripts themselves, once you've installed some).
- '''locks'''
-    A directory for Subversion's repository locking data, used for tracking accessors to the repository.
- '''README.txt'''
-    A file which merely informs its readers that they are looking at a Subversion repository.
 You don't need to access those files, unless you are the repository's administrator. In this case you will edit the conf/snvserve.conf.

@@ Line 452: / Line 452: @@
   (change this value to your own path)
-  cd $MYSVNDIR/repo
+  cd $MYSVN_DIR/repo
   svnadmin create example/
   export MYSVN_URL=file://$MYSVN_DIR/repo/example

@@ Line 67: / Line 67: @@
 ==== Importing into a repository ====
 * svn import [PATH] URL
-  svn import e:\my_src\test file:///home/svn/my_repo/projects/test
+  svn import e:\my_src\test file:///home/svn/my_repo/test
   if PATH is ommitted, it will use the current directory  '.'