[svnbook] r5177 committed - trunk/en/book/ch05-repository-admin.xml
lyalyakin at users.sourceforge.net
lyalyakin at users.sourceforge.net
Wed Jun 29 11:12:00 CDT 2016
Revision: 5177
http://sourceforge.net/p/svnbook/source/5177
Author: lyalyakin
Date: 2016-06-29 16:11:59 +0000 (Wed, 29 Jun 2016)
Log Message:
-----------
Read-thru of SVNBook 1.8.
* en/book/ch05-repository-admin.xml
(svn.reposadmin): Clean-up extra whitespaces.
Modified Paths:
--------------
trunk/en/book/ch05-repository-admin.xml
Modified: trunk/en/book/ch05-repository-admin.xml
===================================================================
--- trunk/en/book/ch05-repository-admin.xml 2016-06-29 15:57:56 UTC (rev 5176)
+++ trunk/en/book/ch05-repository-admin.xml 2016-06-29 16:11:59 UTC (rev 5177)
@@ -207,7 +207,7 @@
</sidebar>
</sect1>
-
+
<!-- ================================================================= -->
<!-- ================================================================= -->
<!-- ================================================================= -->
@@ -488,7 +488,7 @@
</sect2>
</sect1>
-
+
<!-- ================================================================= -->
<!-- ================================================================= -->
<!-- ================================================================= -->
@@ -507,7 +507,7 @@
<!-- =============================================================== -->
<sect2 id="svn.reposadmin.basics.creating">
<title>Creating the Repository</title>
-
+
<para>Subversion repository creation is an incredibly simple
task. The <command>svnadmin</command> utility that comes with
Subversion provides a subcommand (<command>svnadmin
@@ -520,7 +520,7 @@
$
</screen>
</informalexample>
-
+
<para>Assuming that the parent directory
<filename>/var/svn</filename> exists and that you have
sufficient permissions to modify that directory, the previous
@@ -546,7 +546,7 @@
$
</screen>
</informalexample>
-
+
<para>After running this simple command, you have a Subversion
repository. Depending on how users will access this new
repository, you might need to fiddle with its filesystem
@@ -3100,7 +3100,7 @@
repository data that has changed since the previous
backup.</para>
- <para>As far as full backups go, the naïve approach might seem
+ <para>As far as full backups go, the naïve approach might seem
like a sane one, but unless you temporarily disable all other
access to your repository, simply doing a recursive directory
copy runs the risk of generating a faulty backup. In the case
More information about the svnbook-dev
mailing list