[svnbook] r5656 committed - branches/1.8/zh/book/ch05-repository-admin.xml
wuzhouhui at users.sourceforge.net
wuzhouhui at users.sourceforge.net
Tue Mar 20 09:08:14 CDT 2018
Revision: 5656
http://sourceforge.net/p/svnbook/source/5656
Author: wuzhouhui
Date: 2018-03-20 14:08:14 +0000 (Tue, 20 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-18 03:28:43 UTC (rev 5655)
+++ branches/1.8/zh/book/ch05-repository-admin.xml 2018-03-20 14:08:14 UTC (rev 5656)
@@ -4891,6 +4891,7 @@
的情况下, 如果某个版本号已经包含在前一次备份中, 它的属性在后来被修改
了, 那么修改将不会包含在后面的增量备份中.</para>
+ <!--
<para>Generally speaking, only the truly paranoid would need to
back up their entire repository, say, every time a commit
occurred. However, assuming that a given repository has some
@@ -4900,6 +4901,11 @@
repository administrator would want to include as part of a
system-wide nightly backup. It's your data—protect it
as much as you'd like.</para>
+ -->
+ <para>一般来说, 只有真正偏执的人才想在每次提交后备份整个仓库, 然而,
+ 如果仓库已经具备了一些相对细致的冗余机制 (例如每次提交后的邮件通知
+ 或增量转储), 那么仓库管理员可能会把数据库的热拷贝作为每夜例行工作的
+ 一部分去执行. 这是你的数据—你想怎么保护它们都不为过.</para>
<para>Often, the best approach to repository backups is a
diversified one that leverages combinations of the methods
More information about the svnbook-dev
mailing list