If you want a pretty Win32 GUI, TortoiseSVN integrates nicely with the Windows Explorer. Note: - TortoisSVN is a separate project. Please post questions and + TortoiseSVN is a separate project. Please post questions and problems to the TortoiseSVN project's own mailing lists., not Subversion's mailing Index: www/variance-adjusted-patching.html =================================================================== --- www/variance-adjusted-patching.html (revision 9933) +++ www/variance-adjusted-patching.html (working copy) @@ -44,7 +44,7 @@ for differences that have arisen in the target text since the patch was generated, so that the new patch will be applicable to the new target text and yet still have the "same" effect as the old patch. It -is, in essense, patching a patch. For example, suppose a branch B +is, in essence, patching a patch. For example, suppose a branch B diverges from a trunk T, and in an engineer wants to merge the change from revision T:18 to T:19 into B:10, creating B:11. If B:10 is too dissimilar to T:18, the merge may fail due to textual conflicts, even Index: www/webdav-usage.html =================================================================== --- www/webdav-usage.html (revision 9933) +++ www/webdav-usage.html (working copy) @@ -844,7 +844,7 @@
Based on the client design, it may be important to specify other read-only live properties for information about versions. For - examply, how many lines were added/removed in a particular + example, how many lines were added/removed in a particular checkin for a file? Creating these live properties will be quite straight-forward, and driven by the client design over time.
@@ -1248,7 +1248,7 @@ Subversion will work great with caching proxies. There is no longer a need for specialized tools like "cvsup". Just drop in a caching proxy, and you've already got your distributed read-only - repository. That european dev team can just drop in the cache + repository. That European dev team can just drop in the cache between them and the US server and their checkouts/updates will get cached for the benefit of the other team members. Commits will flow through, back to the US-based server. Index: doc/book/tools/readme-dblite.html =================================================================== --- doc/book/tools/readme-dblite.html (revision 9933) +++ doc/book/tools/readme-dblite.html (working copy) @@ -1407,7 +1407,7 @@A marker that imports a <footnote> where there would otherwise be a redundant footnote -defintion. +definition.
When you commit a change to the repository, make sure your change reflects a single purpose: the fixing of a specific bug, the addition of a new feature, or some particular task. Your commit will create a -new revsision number which can forever be used as a "name" for the +new revision number which can forever be used as a "name" for the change. You can mention this revision number in bug databases, or use it as an argument to svn merge should you want to undo the change or port it to another branch.
Index: doc/user/cvs-crossover-guide.html =================================================================== --- doc/user/cvs-crossover-guide.html (revision 9933) +++ doc/user/cvs-crossover-guide.html (working copy) @@ -719,7 +719,7 @@ will trace history back through the original copy-source. The svn move command is exactly equivalent to running svn copy, followed by an svn delete on the - copy-source: the result is a new item scheduled for additon + copy-source: the result is a new item scheduled for addition (with copy-history attached) and the original item scheduled for deletion. Index: INSTALL =================================================================== --- INSTALL (revision 9933) +++ INSTALL (working copy) @@ -452,7 +452,7 @@ Since the resulting binary depends on shared libraries, the destination library directory must be identified in your operating system's library search path. That is in either - /etc/ld.so.conf or $LD_LIBRARY_PATH for linux systems and in + /etc/ld.so.conf or $LD_LIBRARY_PATH for Linux systems and in /etc/rc.conf for FreeBSD, followed by a run of the 'ldconfig' program. Check your system documentation for details. By identifying the destination directory, Subversion will be able @@ -585,7 +585,7 @@ http://www.winimage.com/zLibDll/zlib114dll.zip. * Openssl 0.9.7d or higher obtained from http://www.openssl.org/source/openssl-0.9.7d.tar.gz - * An assembler, e.g., nasm which is avaliable from + * An assembler, e.g., nasm which is available from http://www.kernel.org/pub/software/devel/nasm/binaries/win32/ * For localization gnu gettext is needed. Get gettext-runtime-0.12.1.bin.woe32.zip, @@ -631,7 +631,7 @@ E.3 Preparation - This section descibes how to unpack the files to make a build tree. + This section describes how to unpack the files to make a build tree. * Make a directory SVN and cd into it. * Checkout Subversion: