hgbook
changeset 1050:add323f1ff4e
1.6.2 finished,and first 2 paras of 1.6.3 refined
author | Zhaoping Sun <zhaopingsun@gmail.com> |
---|---|
date | Tue Nov 10 19:05:24 2009 -0500 (2009-11-10) |
parents | 3c372169a7ce e7ce6a9f50c7 |
children | 42952a9cc848 |
files | po/zh.po |
line diff
1.1 --- a/po/zh.po Mon Nov 09 23:30:35 2009 -0500 1.2 +++ b/po/zh.po Tue Nov 10 19:05:24 2009 -0500 1.3 @@ -3259,6 +3259,11 @@ 1.4 "freshly packed Git repository is slightly smaller than a Mercurial " 1.5 "repository, but an unpacked repository is several orders of magnitude larger." 1.6 msgstr "" 1.7 +"Mercurial的版本库不需要维护,但Git的版本库需要频繁的手工维护,将其元数据" 1.8 +"<quote>repacks</quote>,如果不这样做,性能就会下降,磁盘空间也会迅速增加。有多" 1.9 +"个Git版本库的服务器需要严格和频繁的重新打包,否则在备份的时候就会成为严重的瓶" 1.10 +"颈,曾经有每日备份运行超过24小时的例子。一个新打包的Git版本库比Mercurial稍小一" 1.11 +"些,但是未打包的版本库则会大几个数量级。" 1.12 1.13 #. type: Content of: <book><chapter><sect1><sect2><para> 1.14 #: ../en/ch01-intro.xml:520 1.15 @@ -3268,11 +3273,13 @@ 1.16 "encountered several instances where scripts charged along blindly in the " 1.17 "presence of errors that should have been fatal." 1.18 msgstr "" 1.19 +"Git的核心由C语言编写,许多Git命令是用shell或者perl脚本实现的,这些脚本的质量差" 1.20 +"别很大。我碰到过几次这样的情况,明明已经出现了致命错误了,脚本还在盲目的执行。" 1.21 1.22 #. type: Content of: <book><chapter><sect1><sect2><para> 1.23 #: ../en/ch01-intro.xml:526 1.24 msgid "Mercurial can import revision history from a Git repository." 1.25 -msgstr "" 1.26 +msgstr "Mercurial可以从Git的版本库中导入版本历史。" 1.27 1.28 #. type: Content of: <book><chapter><sect1><sect2><para> 1.29 #: ../en/ch01-intro.xml:534 1.30 @@ -3281,6 +3288,8 @@ 1.31 "to its age and internal untidiness, it has been only lightly maintained for " 1.32 "many years." 1.33 msgstr "" 1.34 +"CVS可能是世界上使用最广泛的版本控制工具。因为它是太古老和内部实现很混乱,许多" 1.35 +"年来都处于维护状态。" 1.36 1.37 #. type: Content of: <book><chapter><sect1><sect2><para> 1.38 #: ../en/ch01-intro.xml:538 1.39 @@ -3295,6 +3304,11 @@ 1.40 "timestamps of the changes made to each file involved (if you even know what " 1.41 "those files were)." 1.42 msgstr "" 1.43 +"CVS采用的是集中式客户/服务器结构。它不会将相关的文件变更一起作为原子提交,这使" 1.44 +"得它很容易<quote>破坏构建</quote>:一个人成功的提交了一部分更改,然后要停下来" 1.45 +"处理合并,这使得其他人只能看见他们的部分工作。这样也会影响你和项目历史的工作方" 1.46 +"式。如果你想看到其他人针对他的那部分任务做的全部修改,你必须手动检查每个受影响" 1.47 +"的文件的变更描述和时间戳(假如你知道是哪些文件)。" 1.48 1.49 #. type: Content of: <book><chapter><sect1><sect2><para> 1.50 #: ../en/ch01-intro.xml:550