安装步骤: 1.安装apache server 中间有一个地方需要输入服务器IP 原文:Make sure that you enter the server-URL correctly (if you don't have a DNS name for your server, just enter the IP-address). I recommend to install Apache for All Users, on Port 80, as a Service. Note: if you already have IIS or any other program running which listens on port 80 the installation might fail. If that happens, go to the programs directory, /Apache Group/Apache2/conf and locate the file httpd.conf. Edit that file so that Listen 80 is changed to a free port, e.g. Listen 81. Then restart the installation - this time it should finish without problems.
原文: Subversion (usually c:/program files/Subversion) and find the files /httpd/mod_dav_svn.so and mod_authz_svn.so. Copy these files to the Apache modules directory (usually c:/program files/apache group/apache2/modules ). 4. Copy the file /bin/libdb*.dll and /bin/intl3_svn.dll from the Subversion installation directory to the Apache bin directory. 5. Edit Apache's configuration file (usually C:/Program Files/Apache Group/Apache2/conf/httpd.conf) with a text editor such as Notepad and make the following changes: Uncomment (remove the '#' mark) the following lines: #LoadModule dav_fs_module modules/mod_dav_fs.so #LoadModule dav_module modules/mod_dav.so Add the following two lines to the end of the LoadModule section. LoadModule dav_svn_module modules/mod_dav_svn.so LoadModule authz_svn_module modules/mod_authz_svn.so
阅读TortniseSVN的手册的笔记 2.3.4. How Working Copies Track the Repository Unchanged, and current 工作目录下的文件没有改变 Locally changed, and current 本地目录的文件改变了,但是还没有commit到版本库中。此时commit会把更改提交到版本库,而update会从新从版本库下载最后一次更新的文件到本地。 Unchanged, and out-of-date 版本库中的文件改变了,而在本地的工作目录中,改文件还没有更新。此时commit操作什么都不做,而update操作会从版本库下载最新的文件到本地。 Locally changed, and out-of-date 本地文件和版本库中的文件都发生了改变。此时,首先要做的是从版本库下载(update)最新的文件到本地目录,而此时的下载(update)会把合并版本库上的更改和本地的更改。 (The file has been changed both in the working directory, and in the repository. A commit of the file will fail with an out-of-date error. The file should be updated first; an update command will attempt to merge the public changes with the local changes. If Subversion can't complete the merge in a plausible way automatically, it leaves it to the user to resolve the conflict. )
4.1.5. Repository Layout There are some standard, recommended ways to organize a repository. Most people create a trunk directory to hold the “main line” of development, a branches directory to contain branch copies, and a tags directory to contain tag copies. If a repository holds only one project, then often people create these top-level directories: /trunk /branches /tags
If a repository contains multiple projects, people often index their layout by branch: /trunk/paint /trunk/calc /branches/paint /branches/calc /tags/paint /tags/calc
...or by project: /paint/trunk /paint/branches /paint/tags /calc/trunk /calc/branches /calc/tags