SubVersion: Difference between revisions

Revision as of 12:17, 27 November 2007

Installation

Configuration

mkdir C:\Uwes\Programme\Subversion\repositories\uweheuer => directory for repository
svnadmin create \Uwes\Programme\Subversion\repositories\uweheuer => create repository

Concepts

Subversion can be used without running the server. The repository can be stored on your local file system and accessed by a Subversion client directly. The data is stored in a repository. The repository stores the data in a filesystem tree. Unlike most version control systems, Subversion's revision numbers apply to entire trees, not individual files. Each revision number selects an entire tree, a particular state of the repository after some committed change. Another way to think about it is that revision N represents the state of the repository filesystem after the Nth commit. When Subversion users talk about “revision 5 of foo.c”, they really mean “foo.c as it appears in revision 5.”

check out (copy) => working copy: svn checkout <???>
publish: svn commit <???>

Tools

svn

svn is the command line client.

@@ Line 8: / Line 8: @@
 ==Concepts==
 Subversion can be used without running the server. The repository can be stored on your local file system and accessed by a Subversion client directly.
-The data is stored in a repository. The repository stores the data in a filesystem tree.
+The data is stored in a '''repository'''. The repository stores the data in a filesystem tree. Unlike most version control systems, Subversion's '''revision''' numbers apply to entire trees, not individual files. Each revision number selects an entire tree, a particular state of the repository after some committed change. Another way to think about it is that revision N represents the state of the repository filesystem after the Nth commit. When Subversion users talk about “revision 5 of foo.c”, they really mean “foo.c as it appears in revision 5.”
 #check out (copy) => working copy: svn checkout <???>