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

wuzhouhui at users.sourceforge.net wuzhouhui at users.sourceforge.net
Sat Feb 3 21:48:01 CST 2018

Revision: 5624
Author:   wuzhouhui
Date:     2018-02-04 03:48:01 +0000 (Sun, 04 Feb 2018)
Log Message:
1.8/zh: translation of chapter 5 in progress

Modified Paths:

Modified: branches/1.8/zh/book/ch05-repository-admin.xml
--- branches/1.8/zh/book/ch05-repository-admin.xml	2018-02-03 03:26:16 UTC (rev 5623)
+++ branches/1.8/zh/book/ch05-repository-admin.xml	2018-02-04 03:48:01 UTC (rev 5624)
@@ -2931,6 +2931,7 @@
+      <!--
         <para>As Subversion dumps each new revision, it outputs only
           enough information to allow a future loader to re-create that
           revision based on the previous one.  In other words, for any
@@ -2939,7 +2940,14 @@
           exception to this rule is the first revision that is dumped
           with the current <command>svnadmin dump</command>
+      -->
+        <para>Subversion 在转储新的版本号时, 输出的信息仅能满足加载过程根据
+          前面的版本号, 重新创建新的版本号. 换句话说, 对于转储文件中给定的
+          任意一个版本号, 只有在该版本号中被修改了的项目, 才会出现在转储文件
+          里, 唯一的例外是被当前 <command>svnadmin dump</command> 转储的第一
+          个版本号.</para>
+      <!--
         <para>By default, Subversion will not express the first dumped
           revision as merely differences to be applied to the previous
           revision.  For one thing, there is no previous revision in the
@@ -2950,12 +2958,21 @@
           self-sufficient, the first dumped revision is, by default, a
           full representation of every directory, file, and property in
           that revision of the repository.</para>
+      -->
+        <para>默认情况下, Subversion 不会把第一个被转储的版本号表示成与前一
+          个版本号的差异. 第一个原因是对于第一个版本号来说, 它的前一个版本号
+          在转储文件中不存在, 第二个原因是 Subversion 无法预知加载转储文件的
+          仓库状态. 为了确保每次执行 <command>svnadmin dump</command> 所产生
+          的输出是自给自足的, Subversion 在默认情况下将会完整地表示被转储的
+          第一个版本号, 包括它的每一个目录, 文件, 和版本号的每一个属性.</para>
+      <!--
         <para>However, you can change this default behavior.  If you add
-          the <option>--incremental</option> option when you dump your
+          the <option>- -incremental</option> option when you dump your
           repository, <command>svnadmin</command> will compare the first
           dumped revision against the previous revision in the
           repository—the same way it treats every other revision that
+          ### TODO
           gets dumped.  It will then output the first revision exactly
           as it does the rest of the revisions in the dump
           range—mentioning only the changes that occurred in that
@@ -2962,6 +2979,13 @@
           revision.  The benefit of this is that you can create several
           small dump files that can be loaded in succession, instead of
           one large one, like so:</para>
+      -->
+        <para>然而, 管理员可以修改这种默认行为. 如果在转储时添加了选项
+          <option>--incremental</option>, <command>svnadmin</command> 会把
+          转储的第一个版本号与前一个版本号作比较—就像对待其他被转储的
+          版本号那样, 只输出在版本号中被修改了的内容. 这样做的好处是管理员
+          可以创建出几个较小的转储文件—而不是一整个大文件—它们被
+          加载时可以连续进行, 就像下面这样:</para>

More information about the svnbook-dev mailing list