[svnbook] r5566 committed - branches/1.8/zh/book/ch05-repository-admin.xml
wuzhouhui at users.sourceforge.net
wuzhouhui at users.sourceforge.net
Wed Jan 3 07:58:37 CST 2018
Revision: 5566
http://sourceforge.net/p/svnbook/source/5566
Author: wuzhouhui
Date: 2018-01-03 13:58:37 +0000 (Wed, 03 Jan 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-01-02 12:13:22 UTC (rev 5565)
+++ branches/1.8/zh/book/ch05-repository-admin.xml 2018-01-03 13:58:37 UTC (rev 5566)
@@ -1221,6 +1221,7 @@
<para>仓库的钩子脚本可以提供非常多的用处, 但大多数都可以简单地归类成
以下几种: 通知, 验证和重复.</para>
+ <!--
<para>Notification scripts are those which tell someone that
something happened. The most common of these found in a
Subversion service offering involve programs which send
@@ -1230,7 +1231,14 @@
other notification approaches, from issue tracker integration
scripts to scripts which operate as IRC bots to announce
that something's changed in the repository.</para>
+ -->
+ <para>通知脚本用于通知用户发生了某些事情. 最常见的用法是把每次提交的
+ 修改以邮件的形式发送给项目的每一位成员, 用到的钩子是
+ post-commit 和 (或) post-revprop-change. 除此之外还有很多其他形式的
+ 通知, 例如整合了问题跟踪的脚本, 或者是充当 IRC 机器人的脚本, 当仓库
+ 发生变化时向大家通报.</para>
+ <!--
<para>On the validation side of things, the start-commit and
pre-commit hooks are widely used to allow or disallow
commits based on various criteria: the author of the commit,
@@ -1242,6 +1250,13 @@
considering the fact that revision properties are not
themselves versioned, and can therefore only be modified
destructively.</para>
+ -->
+ <para>站在验证的角度, 人们经常使用钩子 start-commit 和 pre-commit,
+ 根据不同的标准去禁止或允许提交, 常用的判断标准有提交的作者, 描述
+ 提交的日志消息的格式和 (或) 内容, 甚至是所提交的修改的底层细节.
+ 同样地, 钩子 pre-revprop-change 充当的是版本号属性修改的看门狗,
+ 考虑到版本号属性不属于版本控制的范畴, pre-revprop-change 在保护
+ 版本号属性免受破坏性修改这一点上, 非常重要.</para>
<para>One special class of change validation that has seen
widespread use since Subversion 1.5 was released is
More information about the svnbook-dev
mailing list