[svnbook] r5650 committed - branches/1.8/zh/book/ch05-repository-admin.xml

[wuzhouhui at users.sourceforge.net]

Revision: 5650
          http://sourceforge.net/p/svnbook/source/5650
Author:   wuzhouhui
Date:     2018-03-07 14:31:03 +0000 (Wed, 07 Mar 2018)
Log Message:
-----------
1.8/zh: translation of chapter 5 in progress

Modified Paths:
--------------
    branches/1.8/zh/book/ch05-repository-admin.xml

Modified: branches/1.8/zh/book/ch05-repository-admin.xml
===================================================================
--- branches/1.8/zh/book/ch05-repository-admin.xml	2018-03-04 03:38:48 UTC (rev 5649)
+++ branches/1.8/zh/book/ch05-repository-admin.xml	2018-03-07 14:31:03 UTC (rev 5650)
@@ -4586,6 +4586,7 @@
           UUID (默认情况下并不相同), 关于仓库 UUID 的更多内容, 见
           <xref linkend="svn.reposadmin.maint.uuids" />.</para>
         
+      <!--
         <para>Once the two repositories have the same UUID, you can use
           <command>svn relocate</command> to point your working
           copy to whichever of the repositories you wish to operate
@@ -4603,7 +4604,19 @@
           repository is up to date, or backdate your working copy to a
           revision you know is present in the sync repository, and
           then retry the relocation.</para>
+      -->
+        <para>一旦两个仓库拥有相同的 UUID, 用户就可以用命令 <command>svn
+            relocate</command> 把工作副本重定向到任意一个仓库, 见
+          <xref linkend="svn.ref.svn"/> 的 <xref
+            linkend="svn.ref.svn.c.relocate" />. 但其中有一个潜在的问题: 如果
+          主仓库和镜像仓库不是完全同步, 而工作副本当前指向主仓库, 并且处于最
+          新的状态, 如果此时把工作副本重定向到过时的镜像仓库, 工作副本就会
+          报错, 因为本来应该存在的版本号突然无缘无故的消失了. 如果发生了这种
+          情况, 可以再把工作副本重定向回原来的主仓库, 然后等镜像仓库与主仓库
+          完全同步, 或者把工作副本回退到在镜像仓库中存在的版本号, 然后再重
+          定向工作副本.</para>
 
+      <!--
         <para>Finally, be aware that the revision-based replication
           provided by <command>svnsync</command> is only
           that—replication of revisions.  Only the kinds of
@@ -4617,6 +4630,14 @@
           such things as the hook implementations, repository or
           server configuration data, uncommitted transactions, or
           information about user locks on repository paths.</para>
+      -->
+        <para>最后, 要注意 <command>svnsync</command> 所提供的基于版本号的
+          复制流程只会复制版本号. 只有仓库转储文件格式所携带的信息类似才能
+          用于复制, 因此, <command>svnsync</command> (以及
+          <command>svnrdump</command>, 见
+          <xref linkend="svn.reposadmin.maint.migrate.svnrdump" />) 受到的
+          限制与仓库转储流受到的限制类似, 它们不会复制已实现的钩子, 仓库或
+          服务器的配置, 未提交的事务, 或用户施加在仓库路径上的锁.</para>
 
       </sect3>
 
@@ -4624,7 +4645,10 @@
 
     <!-- =============================================================== -->
     <sect2 id="svn.reposadmin.maint.backup">
+      <!--
       <title>Repository Backup</title>
+      -->
+      <title>仓库备份</title>
 
       <para>Despite numerous advances in technology since the birth of
         the modern computer, one thing unfortunately rings true with