hgbook
view po/zh.po @ 642:a4b71115602d
Typo fix
| author | Dongsheng Song <dongsheng.song@gmail.com> |
|---|---|
| date | Tue Mar 17 16:09:57 2009 +0800 (2009-03-17) |
| parents | 8b73656f95c9 |
| children | 61ac4138e086 |
line source
1 #
2 # Simplified Chinese translation for hgbook
3 # This file is distributed under the same license as the hgbook.
4 #
5 # Authors:
6 # Dongsheng Song <dongsheng.song@gmail.com>, 2009
7 #
8 # Update to new pot:
9 # msgmerge --update zh.po hgbook.pot
10 #
11 # Check translation:
12 # msgfmt --statistics -c -o zh.mo zh.po
13 #
14 # Please format your translation before commit:
15 # msgcat --sort-by-file --width=80 -o zh_new.po zh.po
16 # mv -f zh_new.po zh.po
17 #
18 # Dictionary:
19 # blame 追溯
20 # branch 分支
21 # changes 修改
22 # changeset 修改集
23 # checkout 检出
24 # remove 移除(从版本库删除)
25 # delete 删除(只从文件系统删除)
26 # patchset 补丁集
27 # pushing to 推到
28 # pulling from 拉自，抓取
29 # rename 改名
30 # repository 版本库
31 # revert 恢复
32 # revision 版本
33 # tag 标签
34 # tip 顶点
35 # undo 撤销
36 # unversioned 未版本控制
37 # versioned 受版本控制
38 # working copy 工作副本
39 # ...
40 #
41 msgid ""
42 msgstr ""
43 "Project-Id-Version: hgbook 1.2\n"
44 "POT-Creation-Date: 2009-03-17 10:44+0800\n"
45 "PO-Revision-Date: 2009-03-16 18:32+0800\n"
46 "Last-Translator: \n"
47 "Language-Team: Simplified Chinese <i18n-zh@googlegroups.com >\n"
48 "MIME-Version: 1.0\n"
49 "Content-Type: text/plain; charset=UTF-8\n"
50 "Content-Transfer-Encoding: 8bit\n"
51 "X-Poedit-Language: Chinese\n"
52 "X-Poedit-Country: CHINA\n"
53 "X-Poedit-SourceCharset: utf-8\n"
55 #. type: Content of: <book><title>
56 #: ../en/00book.xml:41
57 msgid "Mercurial: The Definitive Guide"
58 msgstr "Mercurial 权威指南"
60 #. type: Content of: <book><subtitle>
61 #: ../en/00book.xml:46
62 msgid "Compiled from $rev_id$"
63 msgstr "编译自 $rev_id$"
65 #. type: Content of: <book><bookinfo><authorgroup><author><firstname>
66 #: ../en/00book.xml:50
67 msgid "Bryan"
68 msgstr ""
70 #. type: Content of: <book><bookinfo><authorgroup><author><surname>
71 #: ../en/00book.xml:51
72 msgid "O'Sullivan"
73 msgstr ""
75 #. type: Content of: <book><bookinfo>
76 #: ../en/00book.xml:55
77 msgid ""
78 "<editor> <firstname>Mike</firstname> <surname>Loukides</surname> </editor> "
79 "<copyright> <year>2006</year> <year>2007</year> <year>2008</year> <year>2009</"
80 "year> <holder>Bryan O'Sullivan</holder> </copyright>"
81 msgstr ""
83 #. type: Content of: <book><appendix><title>
84 #: ../en/appA-cmdref.xml:4
85 msgid "Command reference"
86 msgstr "命令参考"
88 #. type: Content of: <book><appendix><para>
89 #: ../en/appA-cmdref.xml:6
90 msgid ""
91 "\\cmdref{add}{add files at the next commit} \\optref{add}{I}{include} \\optref"
92 "{add}{X}{exclude} \\optref{add}{n}{dry-run}"
93 msgstr ""
95 #. type: Content of: <book><appendix><para>
96 #: ../en/appA-cmdref.xml:11
97 msgid "\\cmdref{diff}{print changes in history or working directory}"
98 msgstr ""
100 #. type: Content of: <book><appendix><para>
101 #: ../en/appA-cmdref.xml:13
102 msgid ""
103 "Show differences between revisions for the specified files or directories, "
104 "using the unified diff format. For a description of the unified diff format, "
105 "see section <xref linkend=\"sec.mq.patch\"/>."
106 msgstr ""
108 #. type: Content of: <book><appendix><para>
109 #: ../en/appA-cmdref.xml:17
110 msgid ""
111 "By default, this command does not print diffs for files that Mercurial "
112 "considers to contain binary data. To control this behaviour, see the <option "
113 "role=\"hg-opt-diff\">-a</option> and <option role=\"hg-opt-diff\">--git</"
114 "option> options."
115 msgstr ""
117 #. type: Content of: <book><appendix><sect2><title>
118 #: ../en/appA-cmdref.xml:22
119 msgid "Options"
120 msgstr "选项"
122 #. type: Content of: <book><appendix><sect2><para>
123 #: ../en/appA-cmdref.xml:24
124 msgid "\\loptref{diff}{nodates}"
125 msgstr ""
127 #. type: Content of: <book><appendix><sect2><para>
128 #: ../en/appA-cmdref.xml:26
129 msgid "Omit date and time information when printing diff headers."
130 msgstr ""
132 #. type: Content of: <book><appendix><sect2><para>
133 #: ../en/appA-cmdref.xml:28
134 msgid "\\optref{diff}{B}{ignore-blank-lines}"
135 msgstr ""
137 #. type: Content of: <book><appendix><sect2><para>
138 #: ../en/appA-cmdref.xml:30
139 msgid ""
140 "Do not print changes that only insert or delete blank lines. A line that "
141 "contains only whitespace is not considered blank."
142 msgstr ""
144 #. type: Content of: <book><appendix><sect2><para>
145 #: ../en/appA-cmdref.xml:34
146 msgid "\\optref{diff}{I}{include}"
147 msgstr ""
149 #. type: Content of: <book><appendix><sect2><para>
150 #: ../en/appA-cmdref.xml:37
151 msgid "Include files and directories whose names match the given patterns."
152 msgstr ""
154 #. type: Content of: <book><appendix><sect2><para>
155 #: ../en/appA-cmdref.xml:40
156 msgid "\\optref{diff}{X}{exclude}"
157 msgstr ""
159 #. type: Content of: <book><appendix><sect2><para>
160 #: ../en/appA-cmdref.xml:43
161 msgid "Exclude files and directories whose names match the given patterns."
162 msgstr ""
164 #. type: Content of: <book><appendix><sect2><para>
165 #: ../en/appA-cmdref.xml:46
166 msgid "\\optref{diff}{a}{text}"
167 msgstr ""
169 #. type: Content of: <book><appendix><sect2><para>
170 #: ../en/appA-cmdref.xml:49
171 msgid ""
172 "If this option is not specified, <command role=\"hg-cmd\">hg diff</command> "
173 "will refuse to print diffs for files that it detects as binary. Specifying "
174 "<option role=\"hg-opt-diff\">-a</option> forces <command role=\"hg-cmd\">hg "
175 "diff</command> to treat all files as text, and generate diffs for all of them."
176 msgstr ""
178 #. type: Content of: <book><appendix><sect2><para>
179 #: ../en/appA-cmdref.xml:55
180 msgid ""
181 "This option is useful for files that are <quote>mostly text</quote> but have "
182 "a few embedded NUL characters. If you use it on files that contain a lot of "
183 "binary data, its output will be incomprehensible."
184 msgstr ""
186 #. type: Content of: <book><appendix><sect2><para>
187 #: ../en/appA-cmdref.xml:60
188 msgid "\\optref{diff}{b}{ignore-space-change}"
189 msgstr ""
191 #. type: Content of: <book><appendix><sect2><para>
192 #: ../en/appA-cmdref.xml:63
193 msgid ""
194 "Do not print a line if the only change to that line is in the amount of white "
195 "space it contains."
196 msgstr ""
198 #. type: Content of: <book><appendix><sect2><para>
199 #: ../en/appA-cmdref.xml:67
200 msgid "\\optref{diff}{g}{git}"
201 msgstr ""
203 #. type: Content of: <book><appendix><sect2><para>
204 #: ../en/appA-cmdref.xml:70
205 msgid ""
206 "Print <command>git</command>-compatible diffs. XXX reference a format "
207 "description."
208 msgstr ""
210 #. type: Content of: <book><appendix><sect2><para>
211 #: ../en/appA-cmdref.xml:74
212 msgid "\\optref{diff}{p}{show-function}"
213 msgstr ""
215 #. type: Content of: <book><appendix><sect2><para>
216 #: ../en/appA-cmdref.xml:77
217 msgid ""
218 "Display the name of the enclosing function in a hunk header, using a simple "
219 "heuristic. This functionality is enabled by default, so the <option role="
220 "\"hg-opt-diff\">-p</option> option has no effect unless you change the value "
221 "of the <envar role=\"rc-item-diff\">showfunc</envar> config item, as in the "
222 "following example."
223 msgstr ""
225 #. type: Content of: <book><appendix><sect2><para>
226 #: ../en/appA-cmdref.xml:84
227 msgid "\\optref{diff}{r}{rev}"
228 msgstr ""
230 #. type: Content of: <book><appendix><sect2><para>
231 #: ../en/appA-cmdref.xml:87
232 msgid ""
233 "Specify one or more revisions to compare. The <command role=\"hg-cmd\">hg "
234 "diff</command> command accepts up to two <option role=\"hg-opt-diff\">-r</"
235 "option> options to specify the revisions to compare."
236 msgstr ""
238 #. type: Content of: <book><appendix><sect2><orderedlist><listitem><para>
239 #: ../en/appA-cmdref.xml:93
240 msgid ""
241 "Display the differences between the parent revision of the working directory "
242 "and the working directory."
243 msgstr ""
245 #. type: Content of: <book><appendix><sect2><orderedlist><listitem><para>
246 #: ../en/appA-cmdref.xml:97
247 msgid ""
248 "Display the differences between the specified changeset and the working "
249 "directory."
250 msgstr ""
252 #. type: Content of: <book><appendix><sect2><orderedlist><listitem><para>
253 #: ../en/appA-cmdref.xml:101
254 msgid "Display the differences between the two specified changesets."
255 msgstr ""
257 #. type: Content of: <book><appendix><sect2><para>
258 #: ../en/appA-cmdref.xml:105
259 msgid ""
260 "You can specify two revisions using either two <option role=\"hg-opt-diff\">-"
261 "r</option> options or revision range notation. For example, the two revision "
262 "specifications below are equivalent."
263 msgstr ""
265 #. type: Content of: <book><appendix><sect2><para>
266 #: ../en/appA-cmdref.xml:112
267 msgid ""
268 "When you provide two revisions, Mercurial treats the order of those revisions "
269 "as significant. Thus, <command role=\"hg-cmd\">hg diff -r10:20</command> "
270 "will produce a diff that will transform files from their contents as of "
271 "revision 10 to their contents as of revision 20, while <command role=\"hg-cmd"
272 "\">hg diff -r20:10</command> means the opposite: the diff that will transform "
273 "files from their revision 20 contents to their revision 10 contents. You "
274 "cannot reverse the ordering in this way if you are diffing against the "
275 "working directory."
276 msgstr ""
278 #. type: Content of: <book><appendix><sect2><para>
279 #: ../en/appA-cmdref.xml:122
280 msgid "\\optref{diff}{w}{ignore-all-space}"
281 msgstr ""
283 #. type: Content of: <book><appendix><sect2><para>
284 #: ../en/appA-cmdref.xml:125
285 msgid "\\cmdref{version}{print version and copyright information}"
286 msgstr ""
288 #. type: Content of: <book><appendix><sect2><para>
289 #: ../en/appA-cmdref.xml:128
290 msgid ""
291 "This command displays the version of Mercurial you are running, and its "
292 "copyright license. There are four kinds of version string that you may see."
293 msgstr ""
295 #. type: Content of: <book><appendix><sect2><itemizedlist><listitem><para>
296 #: ../en/appA-cmdref.xml:133
297 msgid ""
298 "The string <quote><literal>unknown</literal></quote>. This version of "
299 "Mercurial was not built in a Mercurial repository, and cannot determine its "
300 "own version."
301 msgstr ""
303 #. type: Content of: <book><appendix><sect2><itemizedlist><listitem><para>
304 #: ../en/appA-cmdref.xml:138
305 msgid ""
306 "A short numeric string, such as <quote><literal>1.1</literal></quote>. This "
307 "is a build of a revision of Mercurial that was identified by a specific tag "
308 "in the repository where it was built. (This doesn't necessarily mean that "
309 "you're running an official release; someone else could have added that tag to "
310 "any revision in the repository where they built Mercurial.)"
311 msgstr ""
313 #. type: Content of: <book><appendix><sect2><itemizedlist><listitem><para>
314 #: ../en/appA-cmdref.xml:146
315 msgid ""
316 "A hexadecimal string, such as <quote><literal>875489e31abe</literal></"
317 "quote>. This is a build of the given revision of Mercurial."
318 msgstr ""
320 #. type: Content of: <book><appendix><sect2><itemizedlist><listitem><para>
321 #: ../en/appA-cmdref.xml:150
322 msgid ""
323 "A hexadecimal string followed by a date, such as <quote><literal>875489e31abe"
324 "+20070205</literal></quote>. This is a build of the given revision of "
325 "Mercurial, where the build repository contained some local changes that had "
326 "not been committed."
327 msgstr ""
329 #. type: Content of: <book><appendix><sect2><title>
330 #: ../en/appA-cmdref.xml:159
331 msgid "Tips and tricks"
332 msgstr ""
334 #. type: Content of: <book><appendix><sect2><sect3><title>
335 #: ../en/appA-cmdref.xml:162
336 msgid ""
337 "Why do the results of <command role=\"hg-cmd\">hg diff</command> and <command "
338 "role=\"hg-cmd\">hg status</command> differ?"
339 msgstr ""
340 "为什么 <command role=\"hg-cmd\">hg diff</command> 与 <command role=\"hg-cmd"
341 "\">hg status</command> 的结果不同 ?"
343 #. type: Content of: <book><appendix><sect2><sect3><para>
344 #: ../en/appA-cmdref.xml:164
345 msgid ""
346 "When you run the <command role=\"hg-cmd\">hg status</command> command, you'll "
347 "see a list of files that Mercurial will record changes for the next time you "
348 "perform a commit. If you run the <command role=\"hg-cmd\">hg diff</command> "
349 "command, you may notice that it prints diffs for only a <emphasis>subset</"
350 "emphasis> of the files that <command role=\"hg-cmd\">hg status</command> "
351 "listed. There are two possible reasons for this."
352 msgstr ""
354 #. type: Content of: <book><appendix><sect2><sect3><para>
355 #: ../en/appA-cmdref.xml:171
356 msgid ""
357 "The first is that <command role=\"hg-cmd\">hg status</command> prints some "
358 "kinds of modifications that <command role=\"hg-cmd\">hg diff</command> "
359 "doesn't normally display. The <command role=\"hg-cmd\">hg diff</command> "
360 "command normally outputs unified diffs, which don't have the ability to "
361 "represent some changes that Mercurial can track. Most notably, traditional "
362 "diffs can't represent a change in whether or not a file is executable, but "
363 "Mercurial records this information."
364 msgstr ""
366 #. type: Content of: <book><appendix><sect2><sect3><para>
367 #: ../en/appA-cmdref.xml:179
368 msgid ""
369 "If you use the <option role=\"hg-opt-diff\">--git</option> option to <command "
370 "role=\"hg-cmd\">hg diff</command>, it will display <command>git</command>-"
371 "compatible diffs that <emphasis>can</emphasis> display this extra information."
372 msgstr ""
374 #. type: Content of: <book><appendix><sect2><sect3><para>
375 #: ../en/appA-cmdref.xml:184
376 msgid ""
377 "The second possible reason that <command role=\"hg-cmd\">hg diff</command> "
378 "might be printing diffs for a subset of the files displayed by <command role="
379 "\"hg-cmd\">hg status</command> is that if you invoke it without any "
380 "arguments, <command role=\"hg-cmd\">hg diff</command> prints diffs against "
381 "the first parent of the working directory. If you have run <command role="
382 "\"hg-cmd\">hg merge</command> to merge two changesets, but you haven't yet "
383 "committed the results of the merge, your working directory has two parents "
384 "(use <command role=\"hg-cmd\">hg parents</command> to see them). While "
385 "<command role=\"hg-cmd\">hg status</command> prints modifications relative to "
386 "<emphasis>both</emphasis> parents after an uncommitted merge, <command role="
387 "\"hg-cmd\">hg diff</command> still operates relative only to the first "
388 "parent. You can get it to print diffs relative to the second parent by "
389 "specifying that parent with the <option role=\"hg-opt-diff\">-r</option> "
390 "option. There is no way to print diffs relative to both parents."
391 msgstr ""
393 #. type: Content of: <book><appendix><sect2><sect3><title>
394 #: ../en/appA-cmdref.xml:200
395 msgid "Generating safe binary diffs"
396 msgstr "生成安全的二进制差异"
398 #. type: Content of: <book><appendix><sect2><sect3><para>
399 #: ../en/appA-cmdref.xml:202
400 msgid ""
401 "If you use the <option role=\"hg-opt-diff\">-a</option> option to force "
402 "Mercurial to print diffs of files that are either <quote>mostly text</quote> "
403 "or contain lots of binary data, those diffs cannot subsequently be applied by "
404 "either Mercurial's <command role=\"hg-cmd\">hg import</command> command or "
405 "the system's <command>patch</command> command."
406 msgstr ""
408 #. type: Content of: <book><appendix><sect2><sect3><para>
409 #: ../en/appA-cmdref.xml:209
410 msgid ""
411 "If you want to generate a diff of a binary file that is safe to use as input "
412 "for <command role=\"hg-cmd\">hg import</command>, use the <command role=\"hg-"
413 "cmd\">hg diff</command>{--git} option when you generate the patch. The "
414 "system <command>patch</command> command cannot handle binary patches at all."
415 msgstr ""
417 #. type: Content of: <book><appendix><title>
418 #: ../en/appB-mq-ref.xml:5
419 msgid "Mercurial Queues reference"
420 msgstr "Mercurial 队列参考"
422 #. type: Content of: <book><appendix><sect1><title>
423 #: ../en/appB-mq-ref.xml:8
424 msgid "MQ command reference"
425 msgstr "MQ 命令参考"
427 #. type: Content of: <book><appendix><sect1><para>
428 #: ../en/appB-mq-ref.xml:10
429 msgid ""
430 "For an overview of the commands provided by MQ, use the command <command role="
431 "\"hg-cmd\">hg help mq</command>."
432 msgstr ""
434 #. type: Content of: <book><appendix><sect1><sect2><title>
435 #: ../en/appB-mq-ref.xml:14
436 msgid ""
437 "<command role=\"hg-ext-mq\">qapplied</command>&emdash;print applied patches"
438 msgstr "<command role=\"hg-ext-mq\">qapplied</command>&emdash;显示已应用的补丁"
440 #. type: Content of: <book><appendix><sect1><sect2><para>
441 #: ../en/appB-mq-ref.xml:17
442 msgid ""
443 "The <command role=\"hg-ext-mq\">qapplied</command> command prints the current "
444 "stack of applied patches. Patches are printed in oldest-to-newest order, so "
445 "the last patch in the list is the <quote>top</quote> patch."
446 msgstr ""
448 #. type: Content of: <book><appendix><sect1><sect2><title>
449 #: ../en/appB-mq-ref.xml:24
450 msgid ""
451 "<command role=\"hg-ext-mq\">qcommit</command>&emdash;commit changes in the "
452 "queue repository"
453 msgstr "<command role=\"hg-ext-mq\">qcommit</command>&emdash;提交队列中的修改"
455 #. type: Content of: <book><appendix><sect1><sect2><para>
456 #: ../en/appB-mq-ref.xml:27
457 msgid ""
458 "The <command role=\"hg-ext-mq\">qcommit</command> command commits any "
459 "outstanding changes in the <filename role=\"special\" class=\"directory\">.hg/"
460 "patches</filename> repository. This command only works if the <filename role="
461 "\"special\" class=\"directory\">.hg/patches</filename> directory is a "
462 "repository, i.e. you created the directory using <command role=\"hg-cmd\">hg "
463 "qinit <option role=\"hg-ext-mq-cmd-qinit-opt\">-c</option></command> or ran "
464 "<command role=\"hg-cmd\">hg init</command> in the directory after running "
465 "<command role=\"hg-ext-mq\">qinit</command>."
466 msgstr ""
468 #. type: Content of: <book><appendix><sect1><sect2><para>
469 #: ../en/appB-mq-ref.xml:39
470 msgid ""
471 "This command is shorthand for <command role=\"hg-cmd\">hg commit --cwd .hg/"
472 "patches</command>."
473 msgstr ""
475 #. type: Content of: <book><appendix><sect1><sect2><para>
476 #: ../en/appB-mq-ref.xml:42
477 msgid ""
478 "\\subsection{<command role=\"hg-ext-mq\">qdelete</command>&emdash;delete a "
479 "patch from the <filename role=\"special\">series</filename> file}"
480 msgstr ""
482 #. type: Content of: <book><appendix><sect1><sect2><para>
483 #: ../en/appB-mq-ref.xml:47
484 msgid ""
485 "The <command role=\"hg-ext-mq\">qdelete</command> command removes the entry "
486 "for a patch from the <filename role=\"special\">series</filename> file in the "
487 "<filename role=\"special\" class=\"directory\">.hg/patches</filename> "
488 "directory. It does not pop the patch if the patch is already applied. By "
489 "default, it does not delete the patch file; use the <option role=\"hg-ext-mq-"
490 "cmd-qdel-opt\">-f</option> option to do that."
491 msgstr ""
493 #. type: Content of: <book><appendix><sect1><sect2><para>
494 #: ../en/appB-mq-ref.xml:56 ../en/appB-mq-ref.xml:98 ../en/appB-mq-ref.xml:156
495 #: ../en/appB-mq-ref.xml:196 ../en/appB-mq-ref.xml:263
496 #: ../en/appB-mq-ref.xml:334 ../en/appB-mq-ref.xml:403
497 #: ../en/appB-mq-ref.xml:496
498 msgid "Options:"
499 msgstr ""
501 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
502 #: ../en/appB-mq-ref.xml:58
503 msgid ""
504 "<option role=\"hg-ext-mq-cmd-qdel-opt\">-f</option>: Delete the patch file."
505 msgstr ""
507 #. type: Content of: <book><appendix><sect1><sect2><title>
508 #: ../en/appB-mq-ref.xml:65
509 msgid ""
510 "<command role=\"hg-ext-mq\">qdiff</command>&emdash;print a diff of the "
511 "topmost applied patch"
512 msgstr ""
513 "<command role=\"hg-ext-mq\">qdiff</command>&emdash;显示最新应用补丁的差异"
515 #. type: Content of: <book><appendix><sect1><sect2><para>
516 #: ../en/appB-mq-ref.xml:68
517 msgid ""
518 "The <command role=\"hg-ext-mq\">qdiff</command> command prints a diff of the "
519 "topmost applied patch. It is equivalent to <command role=\"hg-cmd\">hg diff -"
520 "r-2:-1</command>."
521 msgstr ""
523 #. type: Content of: <book><appendix><sect1><sect2><title>
524 #: ../en/appB-mq-ref.xml:74
525 msgid ""
526 "<command role=\"hg-ext-mq\">qfold</command>&emdash;merge (<quote>fold</"
527 "quote>) several patches into one"
528 msgstr ""
529 "<command role=\"hg-ext-mq\">qfold</command>&emdash;将多个补丁合并(<quote>折叠"
530 "</quote>)成一个"
532 #. type: Content of: <book><appendix><sect1><sect2><para>
533 #: ../en/appB-mq-ref.xml:77
534 msgid ""
535 "The <command role=\"hg-ext-mq\">qfold</command> command merges multiple "
536 "patches into the topmost applied patch, so that the topmost applied patch "
537 "makes the union of all of the changes in the patches in question."
538 msgstr ""
540 #. type: Content of: <book><appendix><sect1><sect2><para>
541 #: ../en/appB-mq-ref.xml:82
542 msgid ""
543 "The patches to fold must not be applied; <command role=\"hg-ext-mq\">qfold</"
544 "command> will exit with an error if any is. The order in which patches are "
545 "folded is significant; <command role=\"hg-cmd\">hg qfold a b</command> means "
546 "<quote>apply the current topmost patch, followed by <literal>a</literal>, "
547 "followed by <literal>b</literal></quote>."
548 msgstr ""
550 #. type: Content of: <book><appendix><sect1><sect2><para>
551 #: ../en/appB-mq-ref.xml:90
552 msgid ""
553 "The comments from the folded patches are appended to the comments of the "
554 "destination patch, with each block of comments separated by three asterisk "
555 "(<quote><literal>*</literal></quote>) characters. Use the <option role=\"hg-"
556 "ext-mq-cmd-qfold-opt\">-e</option> option to edit the commit message for the "
557 "combined patch/changeset after the folding has completed."
558 msgstr ""
560 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
561 #: ../en/appB-mq-ref.xml:100
562 msgid ""
563 "<option role=\"hg-ext-mq-cmd-qfold-opt\">-e</option>: Edit the commit message "
564 "and patch description for the newly folded patch."
565 msgstr ""
567 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
568 #: ../en/appB-mq-ref.xml:105
569 msgid ""
570 "<option role=\"hg-ext-mq-cmd-qfold-opt\">-l</option>: Use the contents of the "
571 "given file as the new commit message and patch description for the folded "
572 "patch."
573 msgstr ""
575 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
576 #: ../en/appB-mq-ref.xml:110
577 msgid ""
578 "<option role=\"hg-ext-mq-cmd-qfold-opt\">-m</option>: Use the given text as "
579 "the new commit message and patch description for the folded patch."
580 msgstr ""
582 #. type: Content of: <book><appendix><sect1><sect2><title>
583 #: ../en/appB-mq-ref.xml:118
584 msgid ""
585 "<command role=\"hg-ext-mq\">qheader</command>&emdash;display the header/"
586 "description of a patch"
587 msgstr "<command role=\"hg-ext-mq\">qheader</command>&emdash;显示补丁头部描述"
589 #. type: Content of: <book><appendix><sect1><sect2><para>
590 #: ../en/appB-mq-ref.xml:122
591 msgid ""
592 "The <command role=\"hg-ext-mq\">qheader</command> command prints the header, "
593 "or description, of a patch. By default, it prints the header of the topmost "
594 "applied patch. Given an argument, it prints the header of the named patch."
595 msgstr ""
597 #. type: Content of: <book><appendix><sect1><sect2><title>
598 #: ../en/appB-mq-ref.xml:129
599 msgid ""
600 "<command role=\"hg-ext-mq\">qimport</command>&emdash;import a third-party "
601 "patch into the queue"
602 msgstr ""
603 "<command role=\"hg-ext-mq\">qimport</command>&emdash;将第三方补丁导入队列"
605 #. type: Content of: <book><appendix><sect1><sect2><para>
606 #: ../en/appB-mq-ref.xml:132
607 msgid ""
608 "The <command role=\"hg-ext-mq\">qimport</command> command adds an entry for "
609 "an external patch to the <filename role=\"special\">series</filename> file, "
610 "and copies the patch into the <filename role=\"special\" class=\"directory\">."
611 "hg/patches</filename> directory. It adds the entry immediately after the "
612 "topmost applied patch, but does not push the patch."
613 msgstr ""
615 #. type: Content of: <book><appendix><sect1><sect2><para>
616 #: ../en/appB-mq-ref.xml:140
617 msgid ""
618 "If the <filename role=\"special\" class=\"directory\">.hg/patches</filename> "
619 "directory is a repository, <command role=\"hg-ext-mq\">qimport</command> "
620 "automatically does an <command role=\"hg-cmd\">hg add</command> of the "
621 "imported patch."
622 msgstr ""
624 #. type: Content of: <book><appendix><sect1><sect2><title>
625 #: ../en/appB-mq-ref.xml:148
626 msgid ""
627 "<command role=\"hg-ext-mq\">qinit</command>&emdash;prepare a repository to "
628 "work with MQ"
629 msgstr "<command role=\"hg-ext-mq\">qinit</command>&emdash;为使用 MQ 配置版本库"
631 #. type: Content of: <book><appendix><sect1><sect2><para>
632 #: ../en/appB-mq-ref.xml:151
633 msgid ""
634 "The <command role=\"hg-ext-mq\">qinit</command> command prepares a repository "
635 "to work with MQ. It creates a directory called <filename role=\"special\" "
636 "class=\"directory\">.hg/patches</filename>."
637 msgstr ""
639 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
640 #: ../en/appB-mq-ref.xml:158
641 msgid ""
642 "<option role=\"hg-ext-mq-cmd-qinit-opt\">-c</option>: Create <filename role="
643 "\"special\" class=\"directory\">.hg/patches</filename> as a repository in its "
644 "own right. Also creates a <filename role=\"special\">.hgignore</filename> "
645 "file that will ignore the <filename role=\"special\">status</filename> file."
646 msgstr ""
648 #. type: Content of: <book><appendix><sect1><sect2><para>
649 #: ../en/appB-mq-ref.xml:168
650 msgid ""
651 "When the <filename role=\"special\" class=\"directory\">.hg/patches</"
652 "filename> directory is a repository, the <command role=\"hg-ext-mq\">qimport</"
653 "command> and <command role=\"hg-ext-mq\">qnew</command> commands "
654 "automatically <command role=\"hg-cmd\">hg add</command> new patches."
655 msgstr ""
657 #. type: Content of: <book><appendix><sect1><sect2><title>
658 #: ../en/appB-mq-ref.xml:177
659 msgid "<command role=\"hg-ext-mq\">qnew</command>&emdash;create a new patch"
660 msgstr "<command role=\"hg-ext-mq\">qnew</command>&emdash;创建新补丁"
662 #. type: Content of: <book><appendix><sect1><sect2><para>
663 #: ../en/appB-mq-ref.xml:180
664 msgid ""
665 "The <command role=\"hg-ext-mq\">qnew</command> command creates a new patch. "
666 "It takes one mandatory argument, the name to use for the patch file. The "
667 "newly created patch is created empty by default. It is added to the "
668 "<filename role=\"special\">series</filename> file after the current topmost "
669 "applied patch, and is immediately pushed on top of that patch."
670 msgstr ""
672 #. type: Content of: <book><appendix><sect1><sect2><para>
673 #: ../en/appB-mq-ref.xml:188
674 msgid ""
675 "If <command role=\"hg-ext-mq\">qnew</command> finds modified files in the "
676 "working directory, it will refuse to create a new patch unless the <option "
677 "role=\"hg-ext-mq-cmd-qnew-opt\">-f</option> option is used (see below). This "
678 "behaviour allows you to <command role=\"hg-ext-mq\">qrefresh</command> your "
679 "topmost applied patch before you apply a new patch on top of it."
680 msgstr ""
682 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
683 #: ../en/appB-mq-ref.xml:198
684 msgid ""
685 "<option role=\"hg-ext-mq-cmd-qnew-opt\">-f</option>: Create a new patch if "
686 "the contents of the working directory are modified. Any outstanding "
687 "modifications are added to the newly created patch, so after this command "
688 "completes, the working directory will no longer be modified."
689 msgstr ""
691 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
692 #: ../en/appB-mq-ref.xml:205
693 msgid ""
694 "<option role=\"hg-ext-mq-cmd-qnew-opt\">-m</option>: Use the given text as "
695 "the commit message. This text will be stored at the beginning of the patch "
696 "file, before the patch data."
697 msgstr ""
699 #. type: Content of: <book><appendix><sect1><sect2><title>
700 #: ../en/appB-mq-ref.xml:214
701 msgid ""
702 "<command role=\"hg-ext-mq\">qnext</command>&emdash;print the name of the next "
703 "patch"
704 msgstr "<command role=\"hg-ext-mq\">qnext</command>&emdash;显示下个补丁的名称"
706 #. type: Content of: <book><appendix><sect1><sect2><para>
707 #: ../en/appB-mq-ref.xml:217
708 msgid ""
709 "The <command role=\"hg-ext-mq\">qnext</command> command prints the name name "
710 "of the next patch in the <filename role=\"special\">series</filename> file "
711 "after the topmost applied patch. This patch will become the topmost applied "
712 "patch if you run <command role=\"hg-ext-mq\">qpush</command>."
713 msgstr ""
715 #. type: Content of: <book><appendix><sect1><sect2><title>
716 #: ../en/appB-mq-ref.xml:226
717 msgid ""
718 "<command role=\"hg-ext-mq\">qpop</command>&emdash;pop patches off the stack"
719 msgstr "<command role=\"hg-ext-mq\">qpop</command>&emdash;删除堆栈顶部的补丁"
721 #. type: Content of: <book><appendix><sect1><sect2><para>
722 #: ../en/appB-mq-ref.xml:229
723 msgid ""
724 "The <command role=\"hg-ext-mq\">qpop</command> command removes applied "
725 "patches from the top of the stack of applied patches. By default, it removes "
726 "only one patch."
727 msgstr ""
729 #. type: Content of: <book><appendix><sect1><sect2><para>
730 #: ../en/appB-mq-ref.xml:233
731 msgid ""
732 "This command removes the changesets that represent the popped patches from "
733 "the repository, and updates the working directory to undo the effects of the "
734 "patches."
735 msgstr ""
737 #. type: Content of: <book><appendix><sect1><sect2><para>
738 #: ../en/appB-mq-ref.xml:237
739 msgid ""
740 "This command takes an optional argument, which it uses as the name or index "
741 "of the patch to pop to. If given a name, it will pop patches until the named "
742 "patch is the topmost applied patch. If given a number, <command role=\"hg-"
743 "ext-mq\">qpop</command> treats the number as an index into the entries in the "
744 "series file, counting from zero (empty lines and lines containing only "
745 "comments do not count). It pops patches until the patch identified by the "
746 "given index is the topmost applied patch."
747 msgstr ""
749 #. type: Content of: <book><appendix><sect1><sect2><para>
750 #: ../en/appB-mq-ref.xml:247
751 msgid ""
752 "The <command role=\"hg-ext-mq\">qpop</command> command does not read or write "
753 "patches or the <filename role=\"special\">series</filename> file. It is thus "
754 "safe to <command role=\"hg-ext-mq\">qpop</command> a patch that you have "
755 "removed from the <filename role=\"special\">series</filename> file, or a "
756 "patch that you have renamed or deleted entirely. In the latter two cases, "
757 "use the name of the patch as it was when you applied it."
758 msgstr ""
760 #. type: Content of: <book><appendix><sect1><sect2><para>
761 #: ../en/appB-mq-ref.xml:256
762 msgid ""
763 "By default, the <command role=\"hg-ext-mq\">qpop</command> command will not "
764 "pop any patches if the working directory has been modified. You can override "
765 "this behaviour using the <option role=\"hg-ext-mq-cmd-qpop-opt\">-f</option> "
766 "option, which reverts all modifications in the working directory."
767 msgstr ""
769 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
770 #: ../en/appB-mq-ref.xml:265
771 msgid ""
772 "<option role=\"hg-ext-mq-cmd-qpop-opt\">-a</option>: Pop all applied "
773 "patches. This returns the repository to its state before you applied any "
774 "patches."
775 msgstr ""
777 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
778 #: ../en/appB-mq-ref.xml:270
779 msgid ""
780 "<option role=\"hg-ext-mq-cmd-qpop-opt\">-f</option>: Forcibly revert any "
781 "modifications to the working directory when popping."
782 msgstr ""
784 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
785 #: ../en/appB-mq-ref.xml:275
786 msgid ""
787 "<option role=\"hg-ext-mq-cmd-qpop-opt\">-n</option>: Pop a patch from the "
788 "named queue."
789 msgstr ""
791 #. type: Content of: <book><appendix><sect1><sect2><para>
792 #: ../en/appB-mq-ref.xml:280
793 msgid ""
794 "The <command role=\"hg-ext-mq\">qpop</command> command removes one line from "
795 "the end of the <filename role=\"special\">status</filename> file for each "
796 "patch that it pops."
797 msgstr ""
799 #. type: Content of: <book><appendix><sect1><sect2><title>
800 #: ../en/appB-mq-ref.xml:287
801 msgid ""
802 "<command role=\"hg-ext-mq\">qprev</command>&emdash;print the name of the "
803 "previous patch"
804 msgstr "<command role=\"hg-ext-mq\">qprev</command>&emdash;显示上个补丁的名称"
806 #. type: Content of: <book><appendix><sect1><sect2><para>
807 #: ../en/appB-mq-ref.xml:290
808 msgid ""
809 "The <command role=\"hg-ext-mq\">qprev</command> command prints the name of "
810 "the patch in the <filename role=\"special\">series</filename> file that comes "
811 "before the topmost applied patch. This will become the topmost applied patch "
812 "if you run <command role=\"hg-ext-mq\">qpop</command>."
813 msgstr ""
815 #. type: Content of: <book><appendix><sect1><sect2><title>
816 #: ../en/appB-mq-ref.xml:299
817 msgid ""
818 "<command role=\"hg-ext-mq\">qpush</command>&emdash;push patches onto the stack"
819 msgstr "<command role=\"hg-ext-mq\">qpush</command>&emdash;增加补丁到堆栈"
821 #. type: Content of: <book><appendix><sect1><sect2><para>
822 #: ../en/appB-mq-ref.xml:302
823 msgid ""
824 "The <command role=\"hg-ext-mq\">qpush</command> command adds patches onto the "
825 "applied stack. By default, it adds only one patch."
826 msgstr ""
828 #. type: Content of: <book><appendix><sect1><sect2><para>
829 #: ../en/appB-mq-ref.xml:306
830 msgid ""
831 "This command creates a new changeset to represent each applied patch, and "
832 "updates the working directory to apply the effects of the patches."
833 msgstr ""
835 #. type: Content of: <book><appendix><sect1><sect2><para>
836 #: ../en/appB-mq-ref.xml:310
837 msgid "The default data used when creating a changeset are as follows:"
838 msgstr ""
840 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
841 #: ../en/appB-mq-ref.xml:313
842 msgid ""
843 "The commit date and time zone are the current date and time zone. Because "
844 "these data are used to compute the identity of a changeset, this means that "
845 "if you <command role=\"hg-ext-mq\">qpop</command> a patch and <command role="
846 "\"hg-ext-mq\">qpush</command> it again, the changeset that you push will have "
847 "a different identity than the changeset you popped."
848 msgstr ""
850 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
851 #: ../en/appB-mq-ref.xml:321
852 msgid ""
853 "The author is the same as the default used by the <command role=\"hg-cmd\">hg "
854 "commit</command> command."
855 msgstr ""
857 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
858 #: ../en/appB-mq-ref.xml:325
859 msgid ""
860 "The commit message is any text from the patch file that comes before the "
861 "first diff header. If there is no such text, a default commit message is "
862 "used that identifies the name of the patch."
863 msgstr ""
865 #. type: Content of: <book><appendix><sect1><sect2><para>
866 #: ../en/appB-mq-ref.xml:330
867 msgid ""
868 "If a patch contains a Mercurial patch header (XXX add link), the information "
869 "in the patch header overrides these defaults."
870 msgstr ""
872 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
873 #: ../en/appB-mq-ref.xml:336
874 msgid ""
875 "<option role=\"hg-ext-mq-cmd-qpush-opt\">-a</option>: Push all unapplied "
876 "patches from the <filename role=\"special\">series</filename> file until "
877 "there are none left to push."
878 msgstr ""
880 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
881 #: ../en/appB-mq-ref.xml:342
882 msgid ""
883 "<option role=\"hg-ext-mq-cmd-qpush-opt\">-l</option>: Add the name of the "
884 "patch to the end of the commit message."
885 msgstr ""
887 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
888 #: ../en/appB-mq-ref.xml:346
889 msgid ""
890 "<option role=\"hg-ext-mq-cmd-qpush-opt\">-m</option>: If a patch fails to "
891 "apply cleanly, use the entry for the patch in another saved queue to compute "
892 "the parameters for a three-way merge, and perform a three-way merge using the "
893 "normal Mercurial merge machinery. Use the resolution of the merge as the new "
894 "patch content."
895 msgstr ""
897 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
898 #: ../en/appB-mq-ref.xml:354
899 msgid ""
900 "<option role=\"hg-ext-mq-cmd-qpush-opt\">-n</option>: Use the named queue if "
901 "merging while pushing."
902 msgstr ""
904 #. type: Content of: <book><appendix><sect1><sect2><para>
905 #: ../en/appB-mq-ref.xml:359
906 msgid ""
907 "The <command role=\"hg-ext-mq\">qpush</command> command reads, but does not "
908 "modify, the <filename role=\"special\">series</filename> file. It appends "
909 "one line to the <command role=\"hg-cmd\">hg status</command> file for each "
910 "patch that it pushes."
911 msgstr ""
913 #. type: Content of: <book><appendix><sect1><sect2><title>
914 #: ../en/appB-mq-ref.xml:367
915 msgid ""
916 "<command role=\"hg-ext-mq\">qrefresh</command>&emdash;update the topmost "
917 "applied patch"
918 msgstr "<command role=\"hg-ext-mq\">qrefresh</command>&emdash;更新最新的补丁"
920 #. type: Content of: <book><appendix><sect1><sect2><para>
921 #: ../en/appB-mq-ref.xml:371
922 msgid ""
923 "The <command role=\"hg-ext-mq\">qrefresh</command> command updates the "
924 "topmost applied patch. It modifies the patch, removes the old changeset that "
925 "represented the patch, and creates a new changeset to represent the modified "
926 "patch."
927 msgstr ""
929 #. type: Content of: <book><appendix><sect1><sect2><para>
930 #: ../en/appB-mq-ref.xml:377
931 msgid ""
932 "The <command role=\"hg-ext-mq\">qrefresh</command> command looks for the "
933 "following modifications:"
934 msgstr ""
936 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
937 #: ../en/appB-mq-ref.xml:380
938 msgid ""
939 "Changes to the commit message, i.e. the text before the first diff header in "
940 "the patch file, are reflected in the new changeset that represents the patch."
941 msgstr ""
943 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
944 #: ../en/appB-mq-ref.xml:385
945 msgid ""
946 "Modifications to tracked files in the working directory are added to the "
947 "patch."
948 msgstr ""
950 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
951 #: ../en/appB-mq-ref.xml:388
952 msgid ""
953 "Changes to the files tracked using <command role=\"hg-cmd\">hg add</command>, "
954 "<command role=\"hg-cmd\">hg copy</command>, <command role=\"hg-cmd\">hg "
955 "remove</command>, or <command role=\"hg-cmd\">hg rename</command>. Added "
956 "files and copy and rename destinations are added to the patch, while removed "
957 "files and rename sources are removed."
958 msgstr ""
960 #. type: Content of: <book><appendix><sect1><sect2><para>
961 #: ../en/appB-mq-ref.xml:397
962 msgid ""
963 "Even if <command role=\"hg-ext-mq\">qrefresh</command> detects no changes, it "
964 "still recreates the changeset that represents the patch. This causes the "
965 "identity of the changeset to differ from the previous changeset that "
966 "identified the patch."
967 msgstr ""
969 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
970 #: ../en/appB-mq-ref.xml:405
971 msgid ""
972 "<option role=\"hg-ext-mq-cmd-qrefresh-opt\">-e</option>: Modify the commit "
973 "and patch description, using the preferred text editor."
974 msgstr ""
976 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
977 #: ../en/appB-mq-ref.xml:410
978 msgid ""
979 "<option role=\"hg-ext-mq-cmd-qrefresh-opt\">-m</option>: Modify the commit "
980 "message and patch description, using the given text."
981 msgstr ""
983 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
984 #: ../en/appB-mq-ref.xml:415
985 msgid ""
986 "<option role=\"hg-ext-mq-cmd-qrefresh-opt\">-l</option>: Modify the commit "
987 "message and patch description, using text from the given file."
988 msgstr ""
990 #. type: Content of: <book><appendix><sect1><sect2><title>
991 #: ../en/appB-mq-ref.xml:423
992 msgid "<command role=\"hg-ext-mq\">qrename</command>&emdash;rename a patch"
993 msgstr "<command role=\"hg-ext-mq\">qrename</command>&emdash;改名补丁"
995 #. type: Content of: <book><appendix><sect1><sect2><para>
996 #: ../en/appB-mq-ref.xml:426
997 msgid ""
998 "The <command role=\"hg-ext-mq\">qrename</command> command renames a patch, "
999 "and changes the entry for the patch in the <filename role=\"special\">series</"
1000 "filename> file."
1001 msgstr ""
1003 #. type: Content of: <book><appendix><sect1><sect2><para>
1004 #: ../en/appB-mq-ref.xml:430
1005 msgid ""
1006 "With a single argument, <command role=\"hg-ext-mq\">qrename</command> renames "
1007 "the topmost applied patch. With two arguments, it renames its first argument "
1008 "to its second."
1009 msgstr ""
1011 #. type: Content of: <book><appendix><sect1><sect2><title>
1012 #: ../en/appB-mq-ref.xml:437
1013 msgid ""
1014 "<command role=\"hg-ext-mq\">qrestore</command>&emdash;restore saved queue "
1015 "state"
1016 msgstr "<command role=\"hg-ext-mq\">qrestore</command>&emdash;恢复保存的队列"
1018 #. type: Content of: <book><appendix><sect1><sect2><para>
1019 #: ../en/appB-mq-ref.xml:441
1020 msgid "XXX No idea what this does."
1021 msgstr ""
1023 #. type: Content of: <book><appendix><sect1><sect2><title>
1024 #: ../en/appB-mq-ref.xml:445
1025 msgid ""
1026 "<command role=\"hg-ext-mq\">qsave</command>&emdash;save current queue state"
1027 msgstr "<command role=\"hg-ext-mq\">qsave</command>&emdash;保存当前的队列状态"
1029 #. type: Content of: <book><appendix><sect1><sect2><para>
1030 #: ../en/appB-mq-ref.xml:448
1031 msgid "XXX Likewise."
1032 msgstr ""
1034 #. type: Content of: <book><appendix><sect1><sect2><title>
1035 #: ../en/appB-mq-ref.xml:452
1036 msgid ""
1037 "<command role=\"hg-ext-mq\">qseries</command>&emdash;print the entire patch "
1038 "series"
1039 msgstr "<command role=\"hg-ext-mq\">qseries</command>&emdash;显示补丁序列"
1041 #. type: Content of: <book><appendix><sect1><sect2><para>
1042 #: ../en/appB-mq-ref.xml:455
1043 msgid ""
1044 "The <command role=\"hg-ext-mq\">qseries</command> command prints the entire "
1045 "patch series from the <filename role=\"special\">series</filename> file. It "
1046 "prints only patch names, not empty lines or comments. It prints in order "
1047 "from first to be applied to last."
1048 msgstr ""
1050 #. type: Content of: <book><appendix><sect1><sect2><title>
1051 #: ../en/appB-mq-ref.xml:463
1052 msgid ""
1053 "<command role=\"hg-ext-mq\">qtop</command>&emdash;print the name of the "
1054 "current patch"
1055 msgstr "<command role=\"hg-ext-mq\">qtop</command>&emdash;显示当前补丁的名称"
1057 #. type: Content of: <book><appendix><sect1><sect2><para>
1058 #: ../en/appB-mq-ref.xml:466
1059 msgid ""
1060 "The <command role=\"hg-ext-mq\">qtop</command> prints the name of the topmost "
1061 "currently applied patch."
1062 msgstr ""
1064 #. type: Content of: <book><appendix><sect1><sect2><title>
1065 #: ../en/appB-mq-ref.xml:471
1066 msgid ""
1067 "<command role=\"hg-ext-mq\">qunapplied</command>&emdash;print patches not yet "
1068 "applied"
1069 msgstr ""
1070 "<command role=\"hg-ext-mq\">qunapplied</command>&emdash;显示尚未应用的补丁"
1072 #. type: Content of: <book><appendix><sect1><sect2><para>
1073 #: ../en/appB-mq-ref.xml:475
1074 msgid ""
1075 "The <command role=\"hg-ext-mq\">qunapplied</command> command prints the names "
1076 "of patches from the <filename role=\"special\">series</filename> file that "
1077 "are not yet applied. It prints them in order from the next patch that will "
1078 "be pushed to the last."
1079 msgstr ""
1081 #. type: Content of: <book><appendix><sect1><sect2><title>
1082 #: ../en/appB-mq-ref.xml:483
1083 msgid ""
1084 "<command role=\"hg-cmd\">hg strip</command>&emdash;remove a revision and "
1085 "descendants"
1086 msgstr "<command role=\"hg-cmd\">hg strip</command>&emdash;删除一个版本及其后继"
1088 #. type: Content of: <book><appendix><sect1><sect2><para>
1089 #: ../en/appB-mq-ref.xml:486
1090 msgid ""
1091 "The <command role=\"hg-cmd\">hg strip</command> command removes a revision, "
1092 "and all of its descendants, from the repository. It undoes the effects of "
1093 "the removed revisions from the repository, and updates the working directory "
1094 "to the first parent of the removed revision."
1095 msgstr ""
1097 #. type: Content of: <book><appendix><sect1><sect2><para>
1098 #: ../en/appB-mq-ref.xml:492
1099 msgid ""
1100 "The <command role=\"hg-cmd\">hg strip</command> command saves a backup of the "
1101 "removed changesets in a bundle, so that they can be reapplied if removed in "
1102 "error."
1103 msgstr ""
1105 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
1106 #: ../en/appB-mq-ref.xml:498
1107 msgid ""
1108 "<option role=\"hg-opt-strip\">-b</option>: Save unrelated changesets that are "
1109 "intermixed with the stripped changesets in the backup bundle."
1110 msgstr ""
1112 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
1113 #: ../en/appB-mq-ref.xml:502
1114 msgid ""
1115 "<option role=\"hg-opt-strip\">-f</option>: If a branch has multiple heads, "
1116 "remove all heads. XXX This should be renamed, and use <literal>-f</literal> "
1117 "to strip revs when there are pending changes."
1118 msgstr ""
1120 #. type: Content of: <book><appendix><sect1><sect2><itemizedlist><listitem><para>
1121 #: ../en/appB-mq-ref.xml:507
1122 msgid "<option role=\"hg-opt-strip\">-n</option>: Do not save a backup bundle."
1123 msgstr ""
1125 #. type: Content of: <book><appendix><sect1><title>
1126 #: ../en/appB-mq-ref.xml:514
1127 msgid "MQ file reference"
1128 msgstr "MQ 文件参考"
1130 #. type: Content of: <book><appendix><sect1><sect2><title>
1131 #: ../en/appB-mq-ref.xml:517
1132 msgid "The <filename role=\"special\">series</filename> file"
1133 msgstr "<filename role=\"special\">序列</filename>文件"
1135 #. type: Content of: <book><appendix><sect1><sect2><para>
1136 #: ../en/appB-mq-ref.xml:520
1137 msgid ""
1138 "The <filename role=\"special\">series</filename> file contains a list of the "
1139 "names of all patches that MQ can apply. It is represented as a list of "
1140 "names, with one name saved per line. Leading and trailing white space in "
1141 "each line are ignored."
1142 msgstr ""
1144 #. type: Content of: <book><appendix><sect1><sect2><para>
1145 #: ../en/appB-mq-ref.xml:526
1146 msgid ""
1147 "Lines may contain comments. A comment begins with the <quote><literal>#</"
1148 "literal></quote> character, and extends to the end of the line. Empty lines, "
1149 "and lines that contain only comments, are ignored."
1150 msgstr ""
1152 #. type: Content of: <book><appendix><sect1><sect2><para>
1153 #: ../en/appB-mq-ref.xml:531
1154 msgid ""
1155 "You will often need to edit the <filename role=\"special\">series</filename> "
1156 "file by hand, hence the support for comments and empty lines noted above. "
1157 "For example, you can comment out a patch temporarily, and <command role=\"hg-"
1158 "ext-mq\">qpush</command> will skip over that patch when applying patches. "
1159 "You can also change the order in which patches are applied by reordering "
1160 "their entries in the <filename role=\"special\">series</filename> file."
1161 msgstr ""
1163 #. type: Content of: <book><appendix><sect1><sect2><para>
1164 #: ../en/appB-mq-ref.xml:540
1165 msgid ""
1166 "Placing the <filename role=\"special\">series</filename> file under revision "
1167 "control is also supported; it is a good idea to place all of the patches that "
1168 "it refers to under revision control, as well. If you create a patch "
1169 "directory using the <option role=\"hg-ext-mq-cmd-qinit-opt\">-c</option> "
1170 "option to <command role=\"hg-ext-mq\">qinit</command>, this will be done for "
1171 "you automatically."
1172 msgstr ""
1174 #. type: Content of: <book><appendix><sect1><sect2><title>
1175 #: ../en/appB-mq-ref.xml:550
1176 msgid "The <filename role=\"special\">status</filename> file"
1177 msgstr "<filename role=\"special\">状态</filename>文件"
1179 #. type: Content of: <book><appendix><sect1><sect2><para>
1180 #: ../en/appB-mq-ref.xml:553
1181 msgid ""
1182 "The <filename role=\"special\">status</filename> file contains the names and "
1183 "changeset hashes of all patches that MQ currently has applied. Unlike the "
1184 "<filename role=\"special\">series</filename> file, this file is not intended "
1185 "for editing. You should not place this file under revision control, or "
1186 "modify it in any way. It is used by MQ strictly for internal book-keeping."
1187 msgstr ""
1189 #. type: Content of: <book><appendix><title>
1190 #: ../en/appC-srcinstall.xml:5
1191 msgid "Installing Mercurial from source"
1192 msgstr "从源代码安装 Mercurial"
1194 #. type: Content of: <book><appendix><sect1><title>
1195 #: ../en/appC-srcinstall.xml:8
1196 msgid "On a Unix-like system"
1197 msgstr "类 Unix 系统"
1199 #. type: Content of: <book><appendix><sect1><para>
1200 #: ../en/appC-srcinstall.xml:10
1201 msgid ""
1202 "If you are using a Unix-like system that has a sufficiently recent version of "
1203 "Python (2.3 or newer) available, it is easy to install Mercurial from source."
1204 msgstr ""
1206 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1207 #: ../en/appC-srcinstall.xml:14
1208 msgid ""
1209 "Download a recent source tarball from <ulink url=\"http://www.selenic.com/"
1210 "mercurial/download\">http://www.selenic.com/mercurial/download</ulink>."
1211 msgstr ""
1213 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1214 #: ../en/appC-srcinstall.xml:17
1215 msgid "Unpack the tarball:"
1216 msgstr ""
1218 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1219 #: ../en/appC-srcinstall.xml:20
1220 msgid ""
1221 "Go into the source directory and run the installer script. This will build "
1222 "Mercurial and install it in your home directory."
1223 msgstr ""
1225 #. type: Content of: <book><appendix><sect1><para>
1226 #: ../en/appC-srcinstall.xml:27
1227 msgid ""
1228 "Once the install finishes, Mercurial will be in the <literal>bin</literal> "
1229 "subdirectory of your home directory. Don't forget to make sure that this "
1230 "directory is present in your shell's search path."
1231 msgstr ""
1233 #. type: Content of: <book><appendix><sect1><para>
1234 #: ../en/appC-srcinstall.xml:32
1235 msgid ""
1236 "You will probably need to set the <envar>PYTHONPATH</envar> environment "
1237 "variable so that the Mercurial executable can find the rest of the Mercurial "
1238 "packages. For example, on my laptop, I have set it to <literal>/home/bos/lib/"
1239 "python</literal>. The exact path that you will need to use depends on how "
1240 "Python was built for your system, but should be easy to figure out. If "
1241 "you're uncertain, look through the output of the installer script above, and "
1242 "see where the contents of the <literal>mercurial</literal> directory were "
1243 "installed to."
1244 msgstr ""
1246 #. type: Content of: <book><appendix><sect1><title>
1247 #: ../en/appC-srcinstall.xml:44
1248 msgid "On Windows"
1249 msgstr "Windows 系统"
1251 #. type: Content of: <book><appendix><sect1><para>
1252 #: ../en/appC-srcinstall.xml:46
1253 msgid ""
1254 "Building and installing Mercurial on Windows requires a variety of tools, a "
1255 "fair amount of technical knowledge, and considerable patience. I very much "
1256 "<emphasis>do not recommend</emphasis> this route if you are a <quote>casual "
1257 "user</quote>. Unless you intend to hack on Mercurial, I strongly suggest "
1258 "that you use a binary package instead."
1259 msgstr ""
1261 #. type: Content of: <book><appendix><sect1><para>
1262 #: ../en/appC-srcinstall.xml:53
1263 msgid ""
1264 "If you are intent on building Mercurial from source on Windows, follow the "
1265 "<quote>hard way</quote> directions on the Mercurial wiki at <ulink url="
1266 "\"http://www.selenic.com/mercurial/wiki/index.cgi/WindowsInstall\">http://www."
1267 "selenic.com/mercurial/wiki/index.cgi/WindowsInstall</ulink>, and expect the "
1268 "process to involve a lot of fiddly work."
1269 msgstr ""
1271 #. type: Content of: <book><appendix><title>
1272 #: ../en/appD-license.xml:5
1273 msgid "Open Publication License"
1274 msgstr ""
1276 #. type: Content of: <book><appendix><para>
1277 #: ../en/appD-license.xml:7
1278 msgid "Version 1.0, 8 June 1999"
1279 msgstr ""
1281 #. type: Content of: <book><appendix><sect1><title>
1282 #: ../en/appD-license.xml:10
1283 msgid "Requirements on both unmodified and modified versions"
1284 msgstr ""
1286 #. type: Content of: <book><appendix><sect1><para>
1287 #: ../en/appD-license.xml:13
1288 msgid ""
1289 "The Open Publication works may be reproduced and distributed in whole or in "
1290 "part, in any medium physical or electronic, provided that the terms of this "
1291 "license are adhered to, and that this license or an incorporation of it by "
1292 "reference (with any options elected by the author(s) and/or publisher) is "
1293 "displayed in the reproduction."
1294 msgstr ""
1296 #. type: Content of: <book><appendix><sect1><para>
1297 #: ../en/appD-license.xml:20
1298 msgid "Proper form for an incorporation by reference is as follows:"
1299 msgstr ""
1301 #. type: Content of: <book><appendix><sect1><blockquote><para>
1302 #: ../en/appD-license.xml:24
1303 msgid ""
1304 "Copyright (c) <emphasis>year</emphasis> by <emphasis>author's name or "
1305 "designee</emphasis>. This material may be distributed only subject to the "
1306 "terms and conditions set forth in the Open Publication License, v<emphasis>x."
1307 "y</emphasis> or later (the latest version is presently available at <ulink "
1308 "url=\"http://www.opencontent.org/openpub/\">http://www.opencontent.org/"
1309 "openpub/</ulink>)."
1310 msgstr ""
1312 #. type: Content of: <book><appendix><sect1><para>
1313 #: ../en/appD-license.xml:33
1314 msgid ""
1315 "The reference must be immediately followed with any options elected by the "
1316 "author(s) and/or publisher of the document (see section <xref linkend=\"sec."
1317 "opl.options\"/>)."
1318 msgstr ""
1320 #. type: Content of: <book><appendix><sect1><para>
1321 #: ../en/appD-license.xml:37
1322 msgid ""
1323 "Commercial redistribution of Open Publication-licensed material is permitted."
1324 msgstr ""
1326 #. type: Content of: <book><appendix><sect1><para>
1327 #: ../en/appD-license.xml:40
1328 msgid ""
1329 "Any publication in standard (paper) book form shall require the citation of "
1330 "the original publisher and author. The publisher and author's names shall "
1331 "appear on all outer surfaces of the book. On all outer surfaces of the book "
1332 "the original publisher's name shall be as large as the title of the work and "
1333 "cited as possessive with respect to the title."
1334 msgstr ""
1336 #. type: Content of: <book><appendix><sect1><title>
1337 #: ../en/appD-license.xml:49
1338 msgid "Copyright"
1339 msgstr ""
1341 #. type: Content of: <book><appendix><sect1><para>
1342 #: ../en/appD-license.xml:51
1343 msgid ""
1344 "The copyright to each Open Publication is owned by its author(s) or designee."
1345 msgstr ""
1347 #. type: Content of: <book><appendix><sect1><title>
1348 #: ../en/appD-license.xml:56
1349 msgid "Scope of license"
1350 msgstr ""
1352 #. type: Content of: <book><appendix><sect1><para>
1353 #: ../en/appD-license.xml:58
1354 msgid ""
1355 "The following license terms apply to all Open Publication works, unless "
1356 "otherwise explicitly stated in the document."
1357 msgstr ""
1359 #. type: Content of: <book><appendix><sect1><para>
1360 #: ../en/appD-license.xml:62
1361 msgid ""
1362 "Mere aggregation of Open Publication works or a portion of an Open "
1363 "Publication work with other works or programs on the same media shall not "
1364 "cause this license to apply to those other works. The aggregate work shall "
1365 "contain a notice specifying the inclusion of the Open Publication material "
1366 "and appropriate copyright notice."
1367 msgstr ""
1369 #. type: Content of: <book><appendix><sect1><para>
1370 #: ../en/appD-license.xml:69
1371 msgid ""
1372 "<emphasis role=\"bold\">Severability</emphasis>. If any part of this license "
1373 "is found to be unenforceable in any jurisdiction, the remaining portions of "
1374 "the license remain in force."
1375 msgstr ""
1377 #. type: Content of: <book><appendix><sect1><para>
1378 #: ../en/appD-license.xml:74
1379 msgid ""
1380 "<emphasis role=\"bold\">No warranty</emphasis>. Open Publication works are "
1381 "licensed and provided <quote>as is</quote> without warranty of any kind, "
1382 "express or implied, including, but not limited to, the implied warranties of "
1383 "merchantability and fitness for a particular purpose or a warranty of non-"
1384 "infringement."
1385 msgstr ""
1387 #. type: Content of: <book><appendix><sect1><title>
1388 #: ../en/appD-license.xml:83
1389 msgid "Requirements on modified works"
1390 msgstr ""
1392 #. type: Content of: <book><appendix><sect1><para>
1393 #: ../en/appD-license.xml:85
1394 msgid ""
1395 "All modified versions of documents covered by this license, including "
1396 "translations, anthologies, compilations and partial documents, must meet the "
1397 "following requirements:"
1398 msgstr ""
1400 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1401 #: ../en/appD-license.xml:90
1402 msgid "The modified version must be labeled as such."
1403 msgstr ""
1405 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1406 #: ../en/appD-license.xml:93
1407 msgid ""
1408 "The person making the modifications must be identified and the modifications "
1409 "dated."
1410 msgstr ""
1412 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1413 #: ../en/appD-license.xml:96
1414 msgid ""
1415 "Acknowledgement of the original author and publisher if applicable must be "
1416 "retained according to normal academic citation practices."
1417 msgstr ""
1419 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1420 #: ../en/appD-license.xml:100
1421 msgid "The location of the original unmodified document must be identified."
1422 msgstr ""
1424 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1425 #: ../en/appD-license.xml:103
1426 msgid ""
1427 "The original author's (or authors') name(s) may not be used to assert or "
1428 "imply endorsement of the resulting document without the original author's (or "
1429 "authors') permission."
1430 msgstr ""
1432 #. type: Content of: <book><appendix><sect1><title>
1433 #: ../en/appD-license.xml:111
1434 msgid "Good-practice recommendations"
1435 msgstr ""
1437 #. type: Content of: <book><appendix><sect1><para>
1438 #: ../en/appD-license.xml:113
1439 msgid ""
1440 "In addition to the requirements of this license, it is requested from and "
1441 "strongly recommended of redistributors that:"
1442 msgstr ""
1444 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1445 #: ../en/appD-license.xml:118
1446 msgid ""
1447 "If you are distributing Open Publication works on hardcopy or CD-ROM, you "
1448 "provide email notification to the authors of your intent to redistribute at "
1449 "least thirty days before your manuscript or media freeze, to give the authors "
1450 "time to provide updated documents. This notification should describe "
1451 "modifications, if any, made to the document."
1452 msgstr ""
1454 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1455 #: ../en/appD-license.xml:125
1456 msgid ""
1457 "All substantive modifications (including deletions) be either clearly marked "
1458 "up in the document or else described in an attachment to the document."
1459 msgstr ""
1461 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1462 #: ../en/appD-license.xml:129
1463 msgid ""
1464 "Finally, while it is not mandatory under this license, it is considered good "
1465 "form to offer a free copy of any hardcopy and CD-ROM expression of an Open "
1466 "Publication-licensed work to its author(s)."
1467 msgstr ""
1469 #. type: Content of: <book><appendix><sect1><title>
1470 #: ../en/appD-license.xml:137
1471 msgid "License options"
1472 msgstr ""
1474 #. type: Content of: <book><appendix><sect1><para>
1475 #: ../en/appD-license.xml:139
1476 msgid ""
1477 "The author(s) and/or publisher of an Open Publication-licensed document may "
1478 "elect certain options by appending language to the reference to or copy of "
1479 "the license. These options are considered part of the license instance and "
1480 "must be included with the license (or its incorporation by reference) in "
1481 "derived works."
1482 msgstr ""
1484 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1485 #: ../en/appD-license.xml:147
1486 msgid ""
1487 "To prohibit distribution of substantively modified versions without the "
1488 "explicit permission of the author(s). <quote>Substantive modification</quote> "
1489 "is defined as a change to the semantic content of the document, and excludes "
1490 "mere changes in format or typographical corrections."
1491 msgstr ""
1493 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1494 #: ../en/appD-license.xml:154
1495 msgid ""
1496 "To accomplish this, add the phrase <quote>Distribution of substantively "
1497 "modified versions of this document is prohibited without the explicit "
1498 "permission of the copyright holder.</quote> to the license reference or copy."
1499 msgstr ""
1501 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1502 #: ../en/appD-license.xml:160
1503 msgid ""
1504 "To prohibit any publication of this work or derivative works in whole or in "
1505 "part in standard (paper) book form for commercial purposes is prohibited "
1506 "unless prior permission is obtained from the copyright holder."
1507 msgstr ""
1509 #. type: Content of: <book><appendix><sect1><orderedlist><listitem><para>
1510 #: ../en/appD-license.xml:165
1511 msgid ""
1512 "To accomplish this, add the phrase <quote>Distribution of the work or "
1513 "derivative of the work in any standard (paper) book form is prohibited unless "
1514 "prior permission is obtained from the copyright holder.</quote> to the "
1515 "license reference or copy."
1516 msgstr ""
1518 #. type: Content of: <book><chapter><title>
1519 #: ../en/ch01-intro.xml:5
1520 msgid "Introduction"
1521 msgstr "简介"
1523 #. type: Content of: <book><chapter><sect1><title>
1524 #: ../en/ch01-intro.xml:8
1525 msgid "About revision control"
1526 msgstr "关于版本控制"
1528 #. type: Content of: <book><chapter><sect1><para>
1529 #: ../en/ch01-intro.xml:10
1530 msgid ""
1531 "Revision control is the process of managing multiple versions of a piece of "
1532 "information. In its simplest form, this is something that many people do by "
1533 "hand: every time you modify a file, save it under a new name that contains a "
1534 "number, each one higher than the number of the preceding version."
1535 msgstr ""
1537 #. type: Content of: <book><chapter><sect1><para>
1538 #: ../en/ch01-intro.xml:16
1539 msgid ""
1540 "Manually managing multiple versions of even a single file is an error-prone "
1541 "task, though, so software tools to help automate this process have long been "
1542 "available. The earliest automated revision control tools were intended to "
1543 "help a single user to manage revisions of a single file. Over the past few "
1544 "decades, the scope of revision control tools has expanded greatly; they now "
1545 "manage multiple files, and help multiple people to work together. The best "
1546 "modern revision control tools have no problem coping with thousands of people "
1547 "working together on projects that consist of hundreds of thousands of files."
1548 msgstr ""
1550 #. type: Content of: <book><chapter><sect1><sect2><title>
1551 #: ../en/ch01-intro.xml:28
1552 msgid "Why use revision control?"
1553 msgstr "为什么使用版本控制?"
1555 #. type: Content of: <book><chapter><sect1><sect2><para>
1556 #: ../en/ch01-intro.xml:30
1557 msgid ""
1558 "There are a number of reasons why you or your team might want to use an "
1559 "automated revision control tool for a project."
1560 msgstr ""
1562 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
1563 #: ../en/ch01-intro.xml:34
1564 msgid ""
1565 "It will track the history and evolution of your project, so you don't have "
1566 "to. For every change, you'll have a log of <emphasis>who</emphasis> made it; "
1567 "<emphasis>why</emphasis> they made it; <emphasis>when</emphasis> they made "
1568 "it; and <emphasis>what</emphasis> the change was."
1569 msgstr ""
1571 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
1572 #: ../en/ch01-intro.xml:41
1573 msgid ""
1574 "When you're working with other people, revision control software makes it "
1575 "easier for you to collaborate. For example, when people more or less "
1576 "simultaneously make potentially incompatible changes, the software will help "
1577 "you to identify and resolve those conflicts."
1578 msgstr ""
1580 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
1581 #: ../en/ch01-intro.xml:47
1582 msgid ""
1583 "It can help you to recover from mistakes. If you make a change that later "
1584 "turns out to be in error, you can revert to an earlier version of one or more "
1585 "files. In fact, a <emphasis>really</emphasis> good revision control tool "
1586 "will even help you to efficiently figure out exactly when a problem was "
1587 "introduced (see section <xref linkend=\"sec.undo.bisect\"/> for details)."
1588 msgstr ""
1590 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
1591 #: ../en/ch01-intro.xml:54
1592 msgid ""
1593 "It will help you to work simultaneously on, and manage the drift between, "
1594 "multiple versions of your project."
1595 msgstr ""
1597 #. type: Content of: <book><chapter><sect1><sect2><para>
1598 #: ../en/ch01-intro.xml:57
1599 msgid ""
1600 "Most of these reasons are equally valid---at least in theory---whether you're "
1601 "working on a project by yourself, or with a hundred other people."
1602 msgstr ""
1604 #. type: Content of: <book><chapter><sect1><sect2><para>
1605 #: ../en/ch01-intro.xml:61
1606 msgid ""
1607 "A key question about the practicality of revision control at these two "
1608 "different scales (<quote>lone hacker</quote> and <quote>huge team</quote>) is "
1609 "how its <emphasis>benefits</emphasis> compare to its <emphasis>costs</"
1610 "emphasis>. A revision control tool that's difficult to understand or use is "
1611 "going to impose a high cost."
1612 msgstr ""
1614 #. type: Content of: <book><chapter><sect1><sect2><para>
1615 #: ../en/ch01-intro.xml:69
1616 msgid ""
1617 "A five-hundred-person project is likely to collapse under its own weight "
1618 "almost immediately without a revision control tool and process. In this case, "
1619 "the cost of using revision control might hardly seem worth considering, since "
1620 "<emphasis>without</emphasis> it, failure is almost guaranteed."
1621 msgstr ""
1623 #. type: Content of: <book><chapter><sect1><sect2><para>
1624 #: ../en/ch01-intro.xml:76
1625 msgid ""
1626 "On the other hand, a one-person <quote>quick hack</quote> might seem like a "
1627 "poor place to use a revision control tool, because surely the cost of using "
1628 "one must be close to the overall cost of the project. Right?"
1629 msgstr ""
1631 #. type: Content of: <book><chapter><sect1><sect2><para>
1632 #: ../en/ch01-intro.xml:81
1633 msgid ""
1634 "Mercurial uniquely supports <emphasis>both</emphasis> of these scales of "
1635 "development. You can learn the basics in just a few minutes, and due to its "
1636 "low overhead, you can apply revision control to the smallest of projects with "
1637 "ease. Its simplicity means you won't have a lot of abstruse concepts or "
1638 "command sequences competing for mental space with whatever you're "
1639 "<emphasis>really</emphasis> trying to do. At the same time, Mercurial's high "
1640 "performance and peer-to-peer nature let you scale painlessly to handle large "
1641 "projects."
1642 msgstr ""
1644 #. type: Content of: <book><chapter><sect1><sect2><para>
1645 #: ../en/ch01-intro.xml:91
1646 msgid ""
1647 "No revision control tool can rescue a poorly run project, but a good choice "
1648 "of tools can make a huge difference to the fluidity with which you can work "
1649 "on a project."
1650 msgstr ""
1652 #. type: Content of: <book><chapter><sect1><sect2><title>
1653 #: ../en/ch01-intro.xml:97
1654 msgid "The many names of revision control"
1655 msgstr "版本控制的别名"
1657 #. type: Content of: <book><chapter><sect1><sect2><para>
1658 #: ../en/ch01-intro.xml:99
1659 msgid ""
1660 "Revision control is a diverse field, so much so that it doesn't actually have "
1661 "a single name or acronym. Here are a few of the more common names and "
1662 "acronyms you'll encounter:"
1663 msgstr ""
1665 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
1666 #: ../en/ch01-intro.xml:104
1667 msgid "Revision control (RCS)"
1668 msgstr ""
1670 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
1671 #: ../en/ch01-intro.xml:105
1672 msgid "Software configuration management (SCM), or configuration management"
1673 msgstr ""
1675 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
1676 #: ../en/ch01-intro.xml:107
1677 msgid "Source code management"
1678 msgstr ""
1680 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
1681 #: ../en/ch01-intro.xml:108
1682 msgid "Source code control, or source control"
1683 msgstr ""
1685 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
1686 #: ../en/ch01-intro.xml:110
1687 msgid "Version control (VCS)"
1688 msgstr ""
1690 #. type: Content of: <book><chapter><sect1><sect2><para>
1691 #: ../en/ch01-intro.xml:112
1692 msgid ""
1693 "Some people claim that these terms actually have different meanings, but in "
1694 "practice they overlap so much that there's no agreed or even useful way to "
1695 "tease them apart."
1696 msgstr ""
1698 #. type: Content of: <book><chapter><sect1><title>
1699 #: ../en/ch01-intro.xml:119
1700 msgid "A short history of revision control"
1701 msgstr "版本控制简史"
1703 #. type: Content of: <book><chapter><sect1><para>
1704 #: ../en/ch01-intro.xml:121
1705 msgid ""
1706 "The best known of the old-time revision control tools is SCCS (Source Code "
1707 "Control System), which Marc Rochkind wrote at Bell Labs, in the early 1970s. "
1708 "SCCS operated on individual files, and required every person working on a "
1709 "project to have access to a shared workspace on a single system. Only one "
1710 "person could modify a file at any time; arbitration for access to files was "
1711 "via locks. It was common for people to lock files, and later forget to "
1712 "unlock them, preventing anyone else from modifying those files without the "
1713 "help of an administrator."
1714 msgstr ""
1716 #. type: Content of: <book><chapter><sect1><para>
1717 #: ../en/ch01-intro.xml:132
1718 msgid ""
1719 "Walter Tichy developed a free alternative to SCCS in the early 1980s; he "
1720 "called his program RCS (Revision Control System). Like SCCS, RCS required "
1721 "developers to work in a single shared workspace, and to lock files to prevent "
1722 "multiple people from modifying them simultaneously."
1723 msgstr ""
1725 #. type: Content of: <book><chapter><sect1><para>
1726 #: ../en/ch01-intro.xml:138
1727 msgid ""
1728 "Later in the 1980s, Dick Grune used RCS as a building block for a set of "
1729 "shell scripts he initially called cmt, but then renamed to CVS (Concurrent "
1730 "Versions System). The big innovation of CVS was that it let developers work "
1731 "simultaneously and somewhat independently in their own personal workspaces. "
1732 "The personal workspaces prevented developers from stepping on each other's "
1733 "toes all the time, as was common with SCCS and RCS. Each developer had a copy "
1734 "of every project file, and could modify their copies independently. They had "
1735 "to merge their edits prior to committing changes to the central repository."
1736 msgstr ""
1738 #. type: Content of: <book><chapter><sect1><para>
1739 #: ../en/ch01-intro.xml:149
1740 msgid ""
1741 "Brian Berliner took Grune's original scripts and rewrote them in C, releasing "
1742 "in 1989 the code that has since developed into the modern version of CVS. "
1743 "CVS subsequently acquired the ability to operate over a network connection, "
1744 "giving it a client/server architecture. CVS's architecture is centralised; "
1745 "only the server has a copy of the history of the project. Client workspaces "
1746 "just contain copies of recent versions of the project's files, and a little "
1747 "metadata to tell them where the server is. CVS has been enormously "
1748 "successful; it is probably the world's most widely used revision control "
1749 "system."
1750 msgstr ""
1752 #. type: Content of: <book><chapter><sect1><para>
1753 #: ../en/ch01-intro.xml:160
1754 msgid ""
1755 "In the early 1990s, Sun Microsystems developed an early distributed revision "
1756 "control system, called TeamWare. A TeamWare workspace contains a complete "
1757 "copy of the project's history. TeamWare has no notion of a central "
1758 "repository. (CVS relied upon RCS for its history storage; TeamWare used "
1759 "SCCS.)"
1760 msgstr ""
1762 #. type: Content of: <book><chapter><sect1><para>
1763 #: ../en/ch01-intro.xml:167
1764 msgid ""
1765 "As the 1990s progressed, awareness grew of a number of problems with CVS. It "
1766 "records simultaneous changes to multiple files individually, instead of "
1767 "grouping them together as a single logically atomic operation. It does not "
1768 "manage its file hierarchy well; it is easy to make a mess of a repository by "
1769 "renaming files and directories. Worse, its source code is difficult to read "
1770 "and maintain, which made the <quote>pain level</quote> of fixing these "
1771 "architectural problems prohibitive."
1772 msgstr ""
1774 #. type: Content of: <book><chapter><sect1><para>
1775 #: ../en/ch01-intro.xml:177
1776 msgid ""
1777 "In 2001, Jim Blandy and Karl Fogel, two developers who had worked on CVS, "
1778 "started a project to replace it with a tool that would have a better "
1779 "architecture and cleaner code. The result, Subversion, does not stray from "
1780 "CVS's centralised client/server model, but it adds multi-file atomic commits, "
1781 "better namespace management, and a number of other features that make it a "
1782 "generally better tool than CVS. Since its initial release, it has rapidly "
1783 "grown in popularity."
1784 msgstr ""
1786 #. type: Content of: <book><chapter><sect1><para>
1787 #: ../en/ch01-intro.xml:186
1788 msgid ""
1789 "More or less simultaneously, Graydon Hoare began working on an ambitious "
1790 "distributed revision control system that he named Monotone. While Monotone "
1791 "addresses many of CVS's design flaws and has a peer-to-peer architecture, it "
1792 "goes beyond earlier (and subsequent) revision control tools in a number of "
1793 "innovative ways. It uses cryptographic hashes as identifiers, and has an "
1794 "integral notion of <quote>trust</quote> for code from different sources."
1795 msgstr ""
1797 #. type: Content of: <book><chapter><sect1><para>
1798 #: ../en/ch01-intro.xml:195
1799 msgid ""
1800 "Mercurial began life in 2005. While a few aspects of its design are "
1801 "influenced by Monotone, Mercurial focuses on ease of use, high performance, "
1802 "and scalability to very large projects."
1803 msgstr ""
1805 #. type: Content of: <book><chapter><sect1><title>
1806 #: ../en/ch01-intro.xml:202
1807 msgid "Trends in revision control"
1808 msgstr "版本控制的发展趋势"
1810 #. type: Content of: <book><chapter><sect1><para>
1811 #: ../en/ch01-intro.xml:204
1812 msgid ""
1813 "There has been an unmistakable trend in the development and use of revision "
1814 "control tools over the past four decades, as people have become familiar with "
1815 "the capabilities of their tools and constrained by their limitations."
1816 msgstr ""
1818 #. type: Content of: <book><chapter><sect1><para>
1819 #: ../en/ch01-intro.xml:209
1820 msgid ""
1821 "The first generation began by managing single files on individual computers. "
1822 "Although these tools represented a huge advance over ad-hoc manual revision "
1823 "control, their locking model and reliance on a single computer limited them "
1824 "to small, tightly-knit teams."
1825 msgstr ""
1827 #. type: Content of: <book><chapter><sect1><para>
1828 #: ../en/ch01-intro.xml:215
1829 msgid ""
1830 "The second generation loosened these constraints by moving to network-"
1831 "centered architectures, and managing entire projects at a time. As projects "
1832 "grew larger, they ran into new problems. With clients needing to talk to "
1833 "servers very frequently, server scaling became an issue for large projects. "
1834 "An unreliable network connection could prevent remote users from being able "
1835 "to talk to the server at all. As open source projects started making read-"
1836 "only access available anonymously to anyone, people without commit privileges "
1837 "found that they could not use the tools to interact with a project in a "
1838 "natural way, as they could not record their changes."
1839 msgstr ""
1841 #. type: Content of: <book><chapter><sect1><para>
1842 #: ../en/ch01-intro.xml:227
1843 msgid ""
1844 "The current generation of revision control tools is peer-to-peer in nature. "
1845 "All of these systems have dropped the dependency on a single central server, "
1846 "and allow people to distribute their revision control data to where it's "
1847 "actually needed. Collaboration over the Internet has moved from constrained "
1848 "by technology to a matter of choice and consensus. Modern tools can operate "
1849 "offline indefinitely and autonomously, with a network connection only needed "
1850 "when syncing changes with another repository."
1851 msgstr ""
1853 #. type: Content of: <book><chapter><sect1><title>
1854 #: ../en/ch01-intro.xml:239
1855 msgid "A few of the advantages of distributed revision control"
1856 msgstr "分布版本控制的优点"
1858 #. type: Content of: <book><chapter><sect1><para>
1859 #: ../en/ch01-intro.xml:242
1860 msgid ""
1861 "Even though distributed revision control tools have for several years been as "
1862 "robust and usable as their previous-generation counterparts, people using "
1863 "older tools have not yet necessarily woken up to their advantages. There are "
1864 "a number of ways in which distributed tools shine relative to centralised "
1865 "ones."
1866 msgstr ""
1868 #. type: Content of: <book><chapter><sect1><para>
1869 #: ../en/ch01-intro.xml:249
1870 msgid ""
1871 "For an individual developer, distributed tools are almost always much faster "
1872 "than centralised tools. This is for a simple reason: a centralised tool "
1873 "needs to talk over the network for many common operations, because most "
1874 "metadata is stored in a single copy on the central server. A distributed "
1875 "tool stores all of its metadata locally. All else being equal, talking over "
1876 "the network adds overhead to a centralised tool. Don't underestimate the "
1877 "value of a snappy, responsive tool: you're going to spend a lot of time "
1878 "interacting with your revision control software."
1879 msgstr ""
1881 #. type: Content of: <book><chapter><sect1><para>
1882 #: ../en/ch01-intro.xml:260
1883 msgid ""
1884 "Distributed tools are indifferent to the vagaries of your server "
1885 "infrastructure, again because they replicate metadata to so many locations. "
1886 "If you use a centralised system and your server catches fire, you'd better "
1887 "hope that your backup media are reliable, and that your last backup was "
1888 "recent and actually worked. With a distributed tool, you have many backups "
1889 "available on every contributor's computer."
1890 msgstr ""
1892 #. type: Content of: <book><chapter><sect1><para>
1893 #: ../en/ch01-intro.xml:268
1894 msgid ""
1895 "The reliability of your network will affect distributed tools far less than "
1896 "it will centralised tools. You can't even use a centralised tool without a "
1897 "network connection, except for a few highly constrained commands. With a "
1898 "distributed tool, if your network connection goes down while you're working, "
1899 "you may not even notice. The only thing you won't be able to do is talk to "
1900 "repositories on other computers, something that is relatively rare compared "
1901 "with local operations. If you have a far-flung team of collaborators, this "
1902 "may be significant."
1903 msgstr ""
1905 #. type: Content of: <book><chapter><sect1><sect2><title>
1906 #: ../en/ch01-intro.xml:279
1907 msgid "Advantages for open source projects"
1908 msgstr "开源项目的优点"
1910 #. type: Content of: <book><chapter><sect1><sect2><para>
1911 #: ../en/ch01-intro.xml:281
1912 msgid ""
1913 "If you take a shine to an open source project and decide that you would like "
1914 "to start hacking on it, and that project uses a distributed revision control "
1915 "tool, you are at once a peer with the people who consider themselves the "
1916 "<quote>core</quote> of that project. If they publish their repositories, you "
1917 "can immediately copy their project history, start making changes, and record "
1918 "your work, using the same tools in the same ways as insiders. By contrast, "
1919 "with a centralised tool, you must use the software in a <quote>read only</"
1920 "quote> mode unless someone grants you permission to commit changes to their "
1921 "central server. Until then, you won't be able to record changes, and your "
1922 "local modifications will be at risk of corruption any time you try to update "
1923 "your client's view of the repository."
1924 msgstr ""
1926 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
1927 #: ../en/ch01-intro.xml:297
1928 msgid "The forking non-problem"
1929 msgstr ""
1931 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
1932 #: ../en/ch01-intro.xml:299
1933 msgid ""
1934 "It has been suggested that distributed revision control tools pose some sort "
1935 "of risk to open source projects because they make it easy to <quote>fork</"
1936 "quote> the development of a project. A fork happens when there are "
1937 "differences in opinion or attitude between groups of developers that cause "
1938 "them to decide that they can't work together any longer. Each side takes a "
1939 "more or less complete copy of the project's source code, and goes off in its "
1940 "own direction."
1941 msgstr ""
1943 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
1944 #: ../en/ch01-intro.xml:309
1945 msgid ""
1946 "Sometimes the camps in a fork decide to reconcile their differences. With a "
1947 "centralised revision control system, the <emphasis>technical</emphasis> "
1948 "process of reconciliation is painful, and has to be performed largely by "
1949 "hand. You have to decide whose revision history is going to <quote>win</"
1950 "quote>, and graft the other team's changes into the tree somehow. This "
1951 "usually loses some or all of one side's revision history."
1952 msgstr ""
1954 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
1955 #: ../en/ch01-intro.xml:318
1956 msgid ""
1957 "What distributed tools do with respect to forking is they make forking the "
1958 "<emphasis>only</emphasis> way to develop a project. Every single change that "
1959 "you make is potentially a fork point. The great strength of this approach is "
1960 "that a distributed revision control tool has to be really good at "
1961 "<emphasis>merging</emphasis> forks, because forks are absolutely fundamental: "
1962 "they happen all the time."
1963 msgstr ""
1965 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
1966 #: ../en/ch01-intro.xml:327
1967 msgid ""
1968 "If every piece of work that everybody does, all the time, is framed in terms "
1969 "of forking and merging, then what the open source world refers to as a "
1970 "<quote>fork</quote> becomes <emphasis>purely</emphasis> a social issue. If "
1971 "anything, distributed tools <emphasis>lower</emphasis> the likelihood of a "
1972 "fork:"
1973 msgstr ""
1975 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
1976 #: ../en/ch01-intro.xml:334
1977 msgid ""
1978 "They eliminate the social distinction that centralised tools impose: that "
1979 "between insiders (people with commit access) and outsiders (people without)."
1980 msgstr ""
1982 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
1983 #: ../en/ch01-intro.xml:338
1984 msgid ""
1985 "They make it easier to reconcile after a social fork, because all that's "
1986 "involved from the perspective of the revision control software is just "
1987 "another merge."
1988 msgstr ""
1990 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
1991 #: ../en/ch01-intro.xml:343
1992 msgid ""
1993 "Some people resist distributed tools because they want to retain tight "
1994 "control over their projects, and they believe that centralised tools give "
1995 "them this control. However, if you're of this belief, and you publish your "
1996 "CVS or Subversion repositories publicly, there are plenty of tools available "
1997 "that can pull out your entire project's history (albeit slowly) and recreate "
1998 "it somewhere that you don't control. So while your control in this case is "
1999 "illusory, you are forgoing the ability to fluidly collaborate with whatever "
2000 "people feel compelled to mirror and fork your history."
2001 msgstr ""
2003 #. type: Content of: <book><chapter><sect1><sect2><title>
2004 #: ../en/ch01-intro.xml:358
2005 msgid "Advantages for commercial projects"
2006 msgstr "商业项目的优点"
2008 #. type: Content of: <book><chapter><sect1><sect2><para>
2009 #: ../en/ch01-intro.xml:360
2010 msgid ""
2011 "Many commercial projects are undertaken by teams that are scattered across "
2012 "the globe. Contributors who are far from a central server will see slower "
2013 "command execution and perhaps less reliability. Commercial revision control "
2014 "systems attempt to ameliorate these problems with remote-site replication add-"
2015 "ons that are typically expensive to buy and cantankerous to administer. A "
2016 "distributed system doesn't suffer from these problems in the first place. "
2017 "Better yet, you can easily set up multiple authoritative servers, say one per "
2018 "site, so that there's no redundant communication between repositories over "
2019 "expensive long-haul network links."
2020 msgstr ""
2022 #. type: Content of: <book><chapter><sect1><sect2><para>
2023 #: ../en/ch01-intro.xml:372
2024 msgid ""
2025 "Centralised revision control systems tend to have relatively low "
2026 "scalability. It's not unusual for an expensive centralised system to fall "
2027 "over under the combined load of just a few dozen concurrent users. Once "
2028 "again, the typical response tends to be an expensive and clunky replication "
2029 "facility. Since the load on a central server---if you have one at all---is "
2030 "many times lower with a distributed tool (because all of the data is "
2031 "replicated everywhere), a single cheap server can handle the needs of a much "
2032 "larger team, and replication to balance load becomes a simple matter of "
2033 "scripting."
2034 msgstr ""
2036 #. type: Content of: <book><chapter><sect1><sect2><para>
2037 #: ../en/ch01-intro.xml:384
2038 msgid ""
2039 "If you have an employee in the field, troubleshooting a problem at a "
2040 "customer's site, they'll benefit from distributed revision control. The tool "
2041 "will let them generate custom builds, try different fixes in isolation from "
2042 "each other, and search efficiently through history for the sources of bugs "
2043 "and regressions in the customer's environment, all without needing to connect "
2044 "to your company's network."
2045 msgstr ""
2047 #. type: Content of: <book><chapter><sect1><title>
2048 #: ../en/ch01-intro.xml:395
2049 msgid "Why choose Mercurial?"
2050 msgstr "为什么选择 Mercurial?"
2052 #. type: Content of: <book><chapter><sect1><para>
2053 #: ../en/ch01-intro.xml:397
2054 msgid ""
2055 "Mercurial has a unique set of properties that make it a particularly good "
2056 "choice as a revision control system."
2057 msgstr ""
2059 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2060 #: ../en/ch01-intro.xml:400
2061 msgid "It is easy to learn and use."
2062 msgstr ""
2064 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2065 #: ../en/ch01-intro.xml:401
2066 msgid "It is lightweight."
2067 msgstr ""
2069 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2070 #: ../en/ch01-intro.xml:402
2071 msgid "It scales excellently."
2072 msgstr ""
2074 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2075 #: ../en/ch01-intro.xml:403
2076 msgid "It is easy to customise."
2077 msgstr ""
2079 #. type: Content of: <book><chapter><sect1><para>
2080 #: ../en/ch01-intro.xml:406
2081 msgid ""
2082 "If you are at all familiar with revision control systems, you should be able "
2083 "to get up and running with Mercurial in less than five minutes. Even if not, "
2084 "it will take no more than a few minutes longer. Mercurial's command and "
2085 "feature sets are generally uniform and consistent, so you can keep track of a "
2086 "few general rules instead of a host of exceptions."
2087 msgstr ""
2089 #. type: Content of: <book><chapter><sect1><para>
2090 #: ../en/ch01-intro.xml:413
2091 msgid ""
2092 "On a small project, you can start working with Mercurial in moments. Creating "
2093 "new changes and branches; transferring changes around (whether locally or "
2094 "over a network); and history and status operations are all fast. Mercurial "
2095 "attempts to stay nimble and largely out of your way by combining low "
2096 "cognitive overhead with blazingly fast operations."
2097 msgstr ""
2099 #. type: Content of: <book><chapter><sect1><para>
2100 #: ../en/ch01-intro.xml:420
2101 msgid ""
2102 "The usefulness of Mercurial is not limited to small projects: it is used by "
2103 "projects with hundreds to thousands of contributors, each containing tens of "
2104 "thousands of files and hundreds of megabytes of source code."
2105 msgstr ""
2107 #. type: Content of: <book><chapter><sect1><para>
2108 #: ../en/ch01-intro.xml:425
2109 msgid ""
2110 "If the core functionality of Mercurial is not enough for you, it's easy to "
2111 "build on. Mercurial is well suited to scripting tasks, and its clean "
2112 "internals and implementation in Python make it easy to add features in the "
2113 "form of extensions. There are a number of popular and useful extensions "
2114 "already available, ranging from helping to identify bugs to improving "
2115 "performance."
2116 msgstr ""
2118 #. type: Content of: <book><chapter><sect1><title>
2119 #: ../en/ch01-intro.xml:435
2120 msgid "Mercurial compared with other tools"
2121 msgstr "Mercurial 与其它工具的比较"
2123 #. type: Content of: <book><chapter><sect1><para>
2124 #: ../en/ch01-intro.xml:437
2125 msgid ""
2126 "Before you read on, please understand that this section necessarily reflects "
2127 "my own experiences, interests, and (dare I say it) biases. I have used every "
2128 "one of the revision control tools listed below, in most cases for several "
2129 "years at a time."
2130 msgstr ""
2132 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2133 #: ../en/ch01-intro.xml:445 ../en/ch01-intro.xml:656
2134 msgid "Subversion"
2135 msgstr ""
2137 #. type: Content of: <book><chapter><sect1><sect2><para>
2138 #: ../en/ch01-intro.xml:447
2139 msgid ""
2140 "Subversion is a popular revision control tool, developed to replace CVS. It "
2141 "has a centralised client/server architecture."
2142 msgstr ""
2144 #. type: Content of: <book><chapter><sect1><sect2><para>
2145 #: ../en/ch01-intro.xml:451
2146 msgid ""
2147 "Subversion and Mercurial have similarly named commands for performing the "
2148 "same operations, so if you're familiar with one, it is easy to learn to use "
2149 "the other. Both tools are portable to all popular operating systems."
2150 msgstr ""
2152 #. type: Content of: <book><chapter><sect1><sect2><para>
2153 #: ../en/ch01-intro.xml:456
2154 msgid ""
2155 "Prior to version 1.5, Subversion had no useful support for merges. At the "
2156 "time of writing, its merge tracking capability is new, and known to be <ulink "
2157 "url=\"http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced."
2158 "html#svn.branchmerge.advanced.finalword\">complicated and buggy</ulink>."
2159 msgstr ""
2161 #. type: Content of: <book><chapter><sect1><sect2><para>
2162 #: ../en/ch01-intro.xml:462
2163 msgid ""
2164 "Mercurial has a substantial performance advantage over Subversion on every "
2165 "revision control operation I have benchmarked. I have measured its advantage "
2166 "as ranging from a factor of two to a factor of six when compared with "
2167 "Subversion 1.4.3's <emphasis>ra_local</emphasis> file store, which is the "
2168 "fastest access method available. In more realistic deployments involving a "
2169 "network-based store, Subversion will be at a substantially larger "
2170 "disadvantage. Because many Subversion commands must talk to the server and "
2171 "Subversion does not have useful replication facilities, server capacity and "
2172 "network bandwidth become bottlenecks for modestly large projects."
2173 msgstr ""
2175 #. type: Content of: <book><chapter><sect1><sect2><para>
2176 #: ../en/ch01-intro.xml:475
2177 msgid ""
2178 "Additionally, Subversion incurs substantial storage overhead to avoid network "
2179 "transactions for a few common operations, such as finding modified files "
2180 "(<literal>status</literal>) and displaying modifications against the current "
2181 "revision (<literal>diff</literal>). As a result, a Subversion working copy "
2182 "is often the same size as, or larger than, a Mercurial repository and working "
2183 "directory, even though the Mercurial repository contains a complete history "
2184 "of the project."
2185 msgstr ""
2187 #. type: Content of: <book><chapter><sect1><sect2><para>
2188 #: ../en/ch01-intro.xml:485
2189 msgid ""
2190 "Subversion is widely supported by third party tools. Mercurial currently "
2191 "lags considerably in this area. This gap is closing, however, and indeed "
2192 "some of Mercurial's GUI tools now outshine their Subversion equivalents. "
2193 "Like Mercurial, Subversion has an excellent user manual."
2194 msgstr ""
2196 #. type: Content of: <book><chapter><sect1><sect2><para>
2197 #: ../en/ch01-intro.xml:491
2198 msgid ""
2199 "Because Subversion doesn't store revision history on the client, it is well "
2200 "suited to managing projects that deal with lots of large, opaque binary "
2201 "files. If you check in fifty revisions to an incompressible 10MB file, "
2202 "Subversion's client-side space usage stays constant The space used by any "
2203 "distributed SCM will grow rapidly in proportion to the number of revisions, "
2204 "because the differences between each revision are large."
2205 msgstr ""
2207 #. type: Content of: <book><chapter><sect1><sect2><para>
2208 #: ../en/ch01-intro.xml:500
2209 msgid ""
2210 "In addition, it's often difficult or, more usually, impossible to merge "
2211 "different versions of a binary file. Subversion's ability to let a user lock "
2212 "a file, so that they temporarily have the exclusive right to commit changes "
2213 "to it, can be a significant advantage to a project where binary files are "
2214 "widely used."
2215 msgstr ""
2217 #. type: Content of: <book><chapter><sect1><sect2><para>
2218 #: ../en/ch01-intro.xml:507
2219 msgid ""
2220 "Mercurial can import revision history from a Subversion repository. It can "
2221 "also export revision history to a Subversion repository. This makes it easy "
2222 "to <quote>test the waters</quote> and use Mercurial and Subversion in "
2223 "parallel before deciding to switch. History conversion is incremental, so "
2224 "you can perform an initial conversion, then small additional conversions "
2225 "afterwards to bring in new changes."
2226 msgstr ""
2228 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2229 #: ../en/ch01-intro.xml:519 ../en/ch01-intro.xml:658
2230 msgid "Git"
2231 msgstr ""
2233 #. type: Content of: <book><chapter><sect1><sect2><para>
2234 #: ../en/ch01-intro.xml:521
2235 msgid ""
2236 "Git is a distributed revision control tool that was developed for managing "
2237 "the Linux kernel source tree. Like Mercurial, its early design was somewhat "
2238 "influenced by Monotone."
2239 msgstr ""
2241 #. type: Content of: <book><chapter><sect1><sect2><para>
2242 #: ../en/ch01-intro.xml:526
2243 msgid ""
2244 "Git has a very large command set, with version 1.5.0 providing 139 individual "
2245 "commands. It has something of a reputation for being difficult to learn. "
2246 "Compared to Git, Mercurial has a strong focus on simplicity."
2247 msgstr ""
2249 #. type: Content of: <book><chapter><sect1><sect2><para>
2250 #: ../en/ch01-intro.xml:531
2251 msgid ""
2252 "In terms of performance, Git is extremely fast. In several cases, it is "
2253 "faster than Mercurial, at least on Linux, while Mercurial performs better on "
2254 "other operations. However, on Windows, the performance and general level of "
2255 "support that Git provides is, at the time of writing, far behind that of "
2256 "Mercurial."
2257 msgstr ""
2259 #. type: Content of: <book><chapter><sect1><sect2><para>
2260 #: ../en/ch01-intro.xml:538
2261 msgid ""
2262 "While a Mercurial repository needs no maintenance, a Git repository requires "
2263 "frequent manual <quote>repacks</quote> of its metadata. Without these, "
2264 "performance degrades, while space usage grows rapidly. A server that "
2265 "contains many Git repositories that are not rigorously and frequently "
2266 "repacked will become heavily disk-bound during backups, and there have been "
2267 "instances of daily backups taking far longer than 24 hours as a result. A "
2268 "freshly packed Git repository is slightly smaller than a Mercurial "
2269 "repository, but an unpacked repository is several orders of magnitude larger."
2270 msgstr ""
2272 #. type: Content of: <book><chapter><sect1><sect2><para>
2273 #: ../en/ch01-intro.xml:549
2274 msgid ""
2275 "The core of Git is written in C. Many Git commands are implemented as shell "
2276 "or Perl scripts, and the quality of these scripts varies widely. I have "
2277 "encountered several instances where scripts charged along blindly in the "
2278 "presence of errors that should have been fatal."
2279 msgstr ""
2281 #. type: Content of: <book><chapter><sect1><sect2><para>
2282 #: ../en/ch01-intro.xml:555
2283 msgid "Mercurial can import revision history from a Git repository."
2284 msgstr ""
2286 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2287 #: ../en/ch01-intro.xml:561 ../en/ch01-intro.xml:657
2288 msgid "CVS"
2289 msgstr ""
2291 #. type: Content of: <book><chapter><sect1><sect2><para>
2292 #: ../en/ch01-intro.xml:563
2293 msgid ""
2294 "CVS is probably the most widely used revision control tool in the world. Due "
2295 "to its age and internal untidiness, it has been only lightly maintained for "
2296 "many years."
2297 msgstr ""
2299 #. type: Content of: <book><chapter><sect1><sect2><para>
2300 #: ../en/ch01-intro.xml:567
2301 msgid ""
2302 "It has a centralised client/server architecture. It does not group related "
2303 "file changes into atomic commits, making it easy for people to <quote>break "
2304 "the build</quote>: one person can successfully commit part of a change and "
2305 "then be blocked by the need for a merge, causing other people to see only a "
2306 "portion of the work they intended to do. This also affects how you work with "
2307 "project history. If you want to see all of the modifications someone made as "
2308 "part of a task, you will need to manually inspect the descriptions and "
2309 "timestamps of the changes made to each file involved (if you even know what "
2310 "those files were)."
2311 msgstr ""
2313 #. type: Content of: <book><chapter><sect1><sect2><para>
2314 #: ../en/ch01-intro.xml:579
2315 msgid ""
2316 "CVS has a muddled notion of tags and branches that I will not attempt to even "
2317 "describe. It does not support renaming of files or directories well, making "
2318 "it easy to corrupt a repository. It has almost no internal consistency "
2319 "checking capabilities, so it is usually not even possible to tell whether or "
2320 "how a repository is corrupt. I would not recommend CVS for any project, "
2321 "existing or new."
2322 msgstr ""
2324 #. type: Content of: <book><chapter><sect1><sect2><para>
2325 #: ../en/ch01-intro.xml:587
2326 msgid ""
2327 "Mercurial can import CVS revision history. However, there are a few caveats "
2328 "that apply; these are true of every other revision control tool's CVS "
2329 "importer, too. Due to CVS's lack of atomic changes and unversioned "
2330 "filesystem hierarchy, it is not possible to reconstruct CVS history "
2331 "completely accurately; some guesswork is involved, and renames will usually "
2332 "not show up. Because a lot of advanced CVS administration has to be done by "
2333 "hand and is hence error-prone, it's common for CVS importers to run into "
2334 "multiple problems with corrupted repositories (completely bogus revision "
2335 "timestamps and files that have remained locked for over a decade are just two "
2336 "of the less interesting problems I can recall from personal experience)."
2337 msgstr ""
2339 #. type: Content of: <book><chapter><sect1><sect2><para>
2340 #: ../en/ch01-intro.xml:601
2341 msgid "Mercurial can import revision history from a CVS repository."
2342 msgstr ""
2344 #. type: Content of: <book><chapter><sect1><sect2><title>
2345 #: ../en/ch01-intro.xml:607
2346 msgid "Commercial tools"
2347 msgstr "商业工具"
2349 #. type: Content of: <book><chapter><sect1><sect2><para>
2350 #: ../en/ch01-intro.xml:609
2351 msgid ""
2352 "Perforce has a centralised client/server architecture, with no client-side "
2353 "caching of any data. Unlike modern revision control tools, Perforce requires "
2354 "that a user run a command to inform the server about every file they intend "
2355 "to edit."
2356 msgstr ""
2358 #. type: Content of: <book><chapter><sect1><sect2><para>
2359 #: ../en/ch01-intro.xml:615
2360 msgid ""
2361 "The performance of Perforce is quite good for small teams, but it falls off "
2362 "rapidly as the number of users grows beyond a few dozen. Modestly large "
2363 "Perforce installations require the deployment of proxies to cope with the "
2364 "load their users generate."
2365 msgstr ""
2367 #. type: Content of: <book><chapter><sect1><sect2><title>
2368 #: ../en/ch01-intro.xml:624
2369 msgid "Choosing a revision control tool"
2370 msgstr "选择版本控制工具"
2372 #. type: Content of: <book><chapter><sect1><sect2><para>
2373 #: ../en/ch01-intro.xml:626
2374 msgid ""
2375 "With the exception of CVS, all of the tools listed above have unique "
2376 "strengths that suit them to particular styles of work. There is no single "
2377 "revision control tool that is best in all situations."
2378 msgstr ""
2380 #. type: Content of: <book><chapter><sect1><sect2><para>
2381 #: ../en/ch01-intro.xml:631
2382 msgid ""
2383 "As an example, Subversion is a good choice for working with frequently edited "
2384 "binary files, due to its centralised nature and support for file locking."
2385 msgstr ""
2387 #. type: Content of: <book><chapter><sect1><sect2><para>
2388 #: ../en/ch01-intro.xml:635
2389 msgid ""
2390 "I personally find Mercurial's properties of simplicity, performance, and good "
2391 "merge support to be a compelling combination that has served me well for "
2392 "several years."
2393 msgstr ""
2395 #. type: Content of: <book><chapter><sect1><title>
2396 #: ../en/ch01-intro.xml:643
2397 msgid "Switching from another tool to Mercurial"
2398 msgstr "从其它工具切换到 Mercurial"
2400 #. type: Content of: <book><chapter><sect1><para>
2401 #: ../en/ch01-intro.xml:645
2402 msgid ""
2403 "Mercurial is bundled with an extension named <literal role=\"hg-ext"
2404 "\">convert</literal>, which can incrementally import revision history from "
2405 "several other revision control tools. By <quote>incremental</quote>, I mean "
2406 "that you can convert all of a project's history to date in one go, then rerun "
2407 "the conversion later to obtain new changes that happened after the initial "
2408 "conversion."
2409 msgstr ""
2411 #. type: Content of: <book><chapter><sect1><para>
2412 #: ../en/ch01-intro.xml:653
2413 msgid ""
2414 "The revision control tools supported by <literal role=\"hg-ext\">convert</"
2415 "literal> are as follows:"
2416 msgstr ""
2418 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2419 #: ../en/ch01-intro.xml:659
2420 msgid "Darcs"
2421 msgstr ""
2423 #. type: Content of: <book><chapter><sect1><para>
2424 #: ../en/ch01-intro.xml:661
2425 msgid ""
2426 "In addition, <literal role=\"hg-ext\">convert</literal> can export changes "
2427 "from Mercurial to Subversion. This makes it possible to try Subversion and "
2428 "Mercurial in parallel before committing to a switchover, without risking the "
2429 "loss of any work."
2430 msgstr ""
2432 #. type: Content of: <book><chapter><sect1><para>
2433 #: ../en/ch01-intro.xml:667
2434 msgid ""
2435 "The <command role=\"hg-ext-conver\">convert</command> command is easy to "
2436 "use. Simply point it at the path or URL of the source repository, optionally "
2437 "give it the name of the destination repository, and it will start working. "
2438 "After the initial conversion, just run the same command again to import new "
2439 "changes."
2440 msgstr ""
2442 #. type: Content of: <book><chapter><title>
2443 #: ../en/ch02-tour-basic.xml:5
2444 msgid "A tour of Mercurial: the basics"
2445 msgstr "Mercurial 教程: 基础知识"
2447 #. type: Content of: <book><chapter><sect1><title>
2448 #: ../en/ch02-tour-basic.xml:8
2449 msgid "Installing Mercurial on your system"
2450 msgstr "安装 Mercurial"
2452 #. type: Content of: <book><chapter><sect1><para>
2453 #: ../en/ch02-tour-basic.xml:10
2454 msgid ""
2455 "Prebuilt binary packages of Mercurial are available for every popular "
2456 "operating system. These make it easy to start using Mercurial on your "
2457 "computer immediately."
2458 msgstr ""
2460 #. type: Content of: <book><chapter><sect1><sect2><title>
2461 #: ../en/ch02-tour-basic.xml:15
2462 msgid "Linux"
2463 msgstr ""
2465 #. type: Content of: <book><chapter><sect1><sect2><para>
2466 #: ../en/ch02-tour-basic.xml:17
2467 msgid ""
2468 "Because each Linux distribution has its own packaging tools, policies, and "
2469 "rate of development, it's difficult to give a comprehensive set of "
2470 "instructions on how to install Mercurial binaries. The version of Mercurial "
2471 "that you will end up with can vary depending on how active the person is who "
2472 "maintains the package for your distribution."
2473 msgstr ""
2475 #. type: Content of: <book><chapter><sect1><sect2><para>
2476 #: ../en/ch02-tour-basic.xml:24
2477 msgid ""
2478 "To keep things simple, I will focus on installing Mercurial from the command "
2479 "line under the most popular Linux distributions. Most of these distributions "
2480 "provide graphical package managers that will let you install Mercurial with a "
2481 "single click; the package name to look for is <literal>mercurial</literal>."
2482 msgstr ""
2484 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
2485 #: ../en/ch02-tour-basic.xml:32
2486 msgid "Debian:"
2487 msgstr ""
2489 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
2490 #: ../en/ch02-tour-basic.xml:35
2491 msgid "Fedora Core:"
2492 msgstr ""
2494 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
2495 #: ../en/ch02-tour-basic.xml:38
2496 msgid "Gentoo:"
2497 msgstr ""
2499 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
2500 #: ../en/ch02-tour-basic.xml:40
2501 msgid "OpenSUSE:"
2502 msgstr ""
2504 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
2505 #: ../en/ch02-tour-basic.xml:43
2506 msgid ""
2507 "Ubuntu: Ubuntu's Mercurial package is based on Debian's. To install it, run "
2508 "the following command."
2509 msgstr ""
2511 #. type: Content of: <book><chapter><sect1><sect2><title>
2512 #: ../en/ch02-tour-basic.xml:52
2513 msgid "Solaris"
2514 msgstr ""
2516 #. type: Content of: <book><chapter><sect1><sect2><para>
2517 #: ../en/ch02-tour-basic.xml:54
2518 msgid ""
2519 "SunFreeWare, at <ulink url=\"http://www.sunfreeware.com\">http://www."
2520 "sunfreeware.com</ulink>, is a good source for a large number of pre-built "
2521 "Solaris packages for 32 and 64 bit Intel and Sparc architectures, including "
2522 "current versions of Mercurial."
2523 msgstr ""
2525 #. type: Content of: <book><chapter><sect1><sect2><title>
2526 #: ../en/ch02-tour-basic.xml:62
2527 msgid "Mac OS X"
2528 msgstr ""
2530 #. type: Content of: <book><chapter><sect1><sect2><para>
2531 #: ../en/ch02-tour-basic.xml:64
2532 msgid ""
2533 "Lee Cantey publishes an installer of Mercurial for Mac OS X at <ulink url="
2534 "\"http://mercurial.berkwood.com\">http://mercurial.berkwood.com</ulink>. "
2535 "This package works on both Intel- and Power-based Macs. Before you can use "
2536 "it, you must install a compatible version of Universal MacPython "
2537 "<citation>web:macpython</citation>. This is easy to do; simply follow the "
2538 "instructions on Lee's site."
2539 msgstr ""
2541 #. type: Content of: <book><chapter><sect1><sect2><para>
2542 #: ../en/ch02-tour-basic.xml:73
2543 msgid ""
2544 "It's also possible to install Mercurial using Fink or MacPorts, two popular "
2545 "free package managers for Mac OS X. If you have Fink, use <command>sudo apt-"
2546 "get install mercurial-py25</command>. If MacPorts, <command>sudo port "
2547 "install mercurial</command>."
2548 msgstr ""
2550 #. type: Content of: <book><chapter><sect1><sect2><title>
2551 #: ../en/ch02-tour-basic.xml:81
2552 msgid "Windows"
2553 msgstr ""
2555 #. type: Content of: <book><chapter><sect1><sect2><para>
2556 #: ../en/ch02-tour-basic.xml:83
2557 msgid ""
2558 "Lee Cantey publishes an installer of Mercurial for Windows at <ulink url="
2559 "\"http://mercurial.berkwood.com\">http://mercurial.berkwood.com</ulink>. "
2560 "This package has no external dependencies; it <quote>just works</quote>."
2561 msgstr ""
2563 #. type: Content of: <book><chapter><sect1><sect2><note><para>
2564 #: ../en/ch02-tour-basic.xml:90
2565 msgid ""
2566 "The Windows version of Mercurial does not automatically convert line endings "
2567 "between Windows and Unix styles. If you want to share work with Unix users, "
2568 "you must do a little additional configuration work. XXX Flesh this out."
2569 msgstr ""
2571 #. type: Content of: <book><chapter><sect1><title>
2572 #: ../en/ch02-tour-basic.xml:100
2573 msgid "Getting started"
2574 msgstr "开始"
2576 #. type: Content of: <book><chapter><sect1><para>
2577 #: ../en/ch02-tour-basic.xml:102
2578 msgid ""
2579 "To begin, we'll use the <command role=\"hg-cmd\">hg version</command> command "
2580 "to find out whether Mercurial is actually installed properly. The actual "
2581 "version information that it prints isn't so important; it's whether it prints "
2582 "anything at all that we care about."
2583 msgstr ""
2585 #. type: Content of: <book><chapter><sect1><sect2><title>
2586 #: ../en/ch02-tour-basic.xml:111
2587 msgid "Built-in help"
2588 msgstr "内置帮助"
2590 #. type: Content of: <book><chapter><sect1><sect2><para>
2591 #: ../en/ch02-tour-basic.xml:113
2592 msgid ""
2593 "Mercurial provides a built-in help system. This is invaluable for those "
2594 "times when you find yourself stuck trying to remember how to run a command. "
2595 "If you are completely stuck, simply run <command role=\"hg-cmd\">hg help</"
2596 "command>; it will print a brief list of commands, along with a description of "
2597 "what each does. If you ask for help on a specific command (as below), it "
2598 "prints more detailed information."
2599 msgstr ""
2601 #. type: Content of: <book><chapter><sect1><sect2><para>
2602 #: ../en/ch02-tour-basic.xml:124
2603 msgid ""
2604 "For a more impressive level of detail (which you won't usually need) run "
2605 "<command role=\"hg-cmd\">hg help <option role=\"hg-opt-global\">-v</option></"
2606 "command>. The <option role=\"hg-opt-global\">-v</option> option is short for "
2607 "<option role=\"hg-opt-global\">--verbose</option>, and tells Mercurial to "
2608 "print more information than it usually would."
2609 msgstr ""
2611 #. type: Content of: <book><chapter><sect1><title>
2612 #: ../en/ch02-tour-basic.xml:135
2613 msgid "Working with a repository"
2614 msgstr "使用版本库"
2616 #. type: Content of: <book><chapter><sect1><para>
2617 #: ../en/ch02-tour-basic.xml:137
2618 msgid ""
2619 "In Mercurial, everything happens inside a <emphasis>repository</emphasis>. "
2620 "The repository for a project contains all of the files that <quote>belong to</"
2621 "quote> that project, along with a historical record of the project's files."
2622 msgstr ""
2624 #. type: Content of: <book><chapter><sect1><para>
2625 #: ../en/ch02-tour-basic.xml:143
2626 msgid ""
2627 "There's nothing particularly magical about a repository; it is simply a "
2628 "directory tree in your filesystem that Mercurial treats as special. You can "
2629 "rename or delete a repository any time you like, using either the command "
2630 "line or your file browser."
2631 msgstr ""
2633 #. type: Content of: <book><chapter><sect1><sect2><title>
2634 #: ../en/ch02-tour-basic.xml:150
2635 msgid "Making a local copy of a repository"
2636 msgstr "创建版本库的工作副本"
2638 #. type: Content of: <book><chapter><sect1><sect2><para>
2639 #: ../en/ch02-tour-basic.xml:152
2640 msgid ""
2641 "<emphasis>Copying</emphasis> a repository is just a little bit special. "
2642 "While you could use a normal file copying command to make a copy of a "
2643 "repository, it's best to use a built-in command that Mercurial provides. "
2644 "This command is called <command role=\"hg-cmd\">hg clone</command>, because "
2645 "it creates an identical copy of an existing repository."
2646 msgstr ""
2648 #. type: Content of: <book><chapter><sect1><sect2><para>
2649 #: ../en/ch02-tour-basic.xml:161
2650 msgid ""
2651 "If our clone succeeded, we should now have a local directory called <filename "
2652 "class=\"directory\">hello</filename>. This directory will contain some files."
2653 msgstr ""
2655 #. type: Content of: <book><chapter><sect1><sect2><para>
2656 #: ../en/ch02-tour-basic.xml:167
2657 msgid ""
2658 "These files have the same contents and history in our repository as they do "
2659 "in the repository we cloned."
2660 msgstr ""
2662 #. type: Content of: <book><chapter><sect1><sect2><para>
2663 #: ../en/ch02-tour-basic.xml:170
2664 msgid ""
2665 "Every Mercurial repository is complete, self-contained, and independent. It "
2666 "contains its own private copy of a project's files and history. A cloned "
2667 "repository remembers the location of the repository it was cloned from, but "
2668 "it does not communicate with that repository, or any other, unless you tell "
2669 "it to."
2670 msgstr ""
2672 #. type: Content of: <book><chapter><sect1><sect2><para>
2673 #: ../en/ch02-tour-basic.xml:177
2674 msgid ""
2675 "What this means for now is that we're free to experiment with our repository, "
2676 "safe in the knowledge that it's a private <quote>sandbox</quote> that won't "
2677 "affect anyone else."
2678 msgstr ""
2680 #. type: Content of: <book><chapter><sect1><sect2><title>
2681 #: ../en/ch02-tour-basic.xml:183
2682 msgid "What's in a repository?"
2683 msgstr "什么是版本库?"
2685 #. type: Content of: <book><chapter><sect1><sect2><para>
2686 #: ../en/ch02-tour-basic.xml:185
2687 msgid ""
2688 "When we take a more detailed look inside a repository, we can see that it "
2689 "contains a directory named <filename class=\"directory\">.hg</filename>. "
2690 "This is where Mercurial keeps all of its metadata for the repository."
2691 msgstr ""
2693 #. type: Content of: <book><chapter><sect1><sect2><para>
2694 #: ../en/ch02-tour-basic.xml:192
2695 msgid ""
2696 "The contents of the <filename class=\"directory\">.hg</filename> directory "
2697 "and its subdirectories are private to Mercurial. Every other file and "
2698 "directory in the repository is yours to do with as you please."
2699 msgstr ""
2701 #. type: Content of: <book><chapter><sect1><sect2><para>
2702 #: ../en/ch02-tour-basic.xml:198
2703 msgid ""
2704 "To introduce a little terminology, the <filename class=\"directory\">.hg</"
2705 "filename> directory is the <quote>real</quote> repository, and all of the "
2706 "files and directories that coexist with it are said to live in the "
2707 "<emphasis>working directory</emphasis>. An easy way to remember the "
2708 "distinction is that the <emphasis>repository</emphasis> contains the "
2709 "<emphasis>history</emphasis> of your project, while the <emphasis>working "
2710 "directory</emphasis> contains a <emphasis>snapshot</emphasis> of your project "
2711 "at a particular point in history."
2712 msgstr ""
2714 #. type: Content of: <book><chapter><sect1><title>
2715 #: ../en/ch02-tour-basic.xml:213
2716 msgid "A tour through history"
2717 msgstr "回溯历史"
2719 #. type: Content of: <book><chapter><sect1><para>
2720 #: ../en/ch02-tour-basic.xml:215
2721 msgid ""
2722 "One of the first things we might want to do with a new, unfamiliar repository "
2723 "is understand its history. The <command role=\"hg-cmd\">hg log</command> "
2724 "command gives us a view of history."
2725 msgstr ""
2727 #. type: Content of: <book><chapter><sect1><para>
2728 #: ../en/ch02-tour-basic.xml:222
2729 msgid ""
2730 "By default, this command prints a brief paragraph of output for each change "
2731 "to the project that was recorded. In Mercurial terminology, we call each of "
2732 "these recorded events a <emphasis>changeset</emphasis>, because it can "
2733 "contain a record of changes to several files."
2734 msgstr ""
2736 #. type: Content of: <book><chapter><sect1><para>
2737 #: ../en/ch02-tour-basic.xml:228
2738 msgid ""
2739 "The fields in a record of output from <command role=\"hg-cmd\">hg log</"
2740 "command> are as follows."
2741 msgstr ""
2743 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2744 #: ../en/ch02-tour-basic.xml:231
2745 msgid ""
2746 "<literal>changeset</literal>: This field has the format of a number, followed "
2747 "by a colon, followed by a hexadecimal string. These are "
2748 "<emphasis>identifiers</emphasis> for the changeset. There are two "
2749 "identifiers because the number is shorter and easier to type than the hex "
2750 "string."
2751 msgstr ""
2753 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2754 #: ../en/ch02-tour-basic.xml:237
2755 msgid ""
2756 "<literal>user</literal>: The identity of the person who created the "
2757 "changeset. This is a free-form field, but it most often contains a person's "
2758 "name and email address."
2759 msgstr ""
2761 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2762 #: ../en/ch02-tour-basic.xml:241
2763 msgid ""
2764 "<literal>date</literal>: The date and time on which the changeset was "
2765 "created, and the timezone in which it was created. (The date and time are "
2766 "local to that timezone; they display what time and date it was for the person "
2767 "who created the changeset.)"
2768 msgstr ""
2770 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2771 #: ../en/ch02-tour-basic.xml:246
2772 msgid ""
2773 "<literal>summary</literal>: The first line of the text message that the "
2774 "creator of the changeset entered to describe the changeset."
2775 msgstr ""
2777 #. type: Content of: <book><chapter><sect1><para>
2778 #: ../en/ch02-tour-basic.xml:249
2779 msgid ""
2780 "The default output printed by <command role=\"hg-cmd\">hg log</command> is "
2781 "purely a summary; it is missing a lot of detail."
2782 msgstr ""
2784 #. type: Content of: <book><chapter><sect1><para>
2785 #: ../en/ch02-tour-basic.xml:253
2786 msgid ""
2787 "Figure <xref endterm=\"fig.tour-basic.history.caption\" linkend=\"fig.tour-"
2788 "basic.history\"/> provides a graphical representation of the history of the "
2789 "<filename class=\"directory\">hello</filename> repository, to make it a "
2790 "little easier to see which direction history is <quote>flowing</quote> in. "
2791 "We'll be returning to this figure several times in this chapter and the "
2792 "chapter that follows."
2793 msgstr ""
2795 #. type: Content of: <book><chapter><sect1><informalfigure><mediaobject>
2796 #: ../en/ch02-tour-basic.xml:264
2797 msgid ""
2798 "<imageobject><imagedata fileref=\"images/tour-history.png\"/></imageobject>"
2799 msgstr ""
2801 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><textobject><phrase>
2802 #: ../en/ch02-tour-basic.xml:265 ../en/ch03-tour-merge.xml:48
2803 #: ../en/ch03-tour-merge.xml:78 ../en/ch03-tour-merge.xml:126
2804 #: ../en/ch03-tour-merge.xml:182 ../en/ch03-tour-merge.xml:254
2805 #: ../en/ch04-concepts.xml:56 ../en/ch04-concepts.xml:108
2806 #: ../en/ch04-concepts.xml:194 ../en/ch04-concepts.xml:301
2807 #: ../en/ch04-concepts.xml:353 ../en/ch04-concepts.xml:370
2808 #: ../en/ch04-concepts.xml:414 ../en/ch04-concepts.xml:436
2809 #: ../en/ch04-concepts.xml:480 ../en/ch06-collab.xml:277
2810 #: ../en/ch09-undo.xml:366 ../en/ch09-undo.xml:417 ../en/ch09-undo.xml:485
2811 #: ../en/ch09-undo.xml:527 ../en/ch12-mq.xml:409
2812 msgid "XXX add text"
2813 msgstr ""
2815 #. type: Content of: <book><chapter><sect1><informalfigure><mediaobject><caption><para>
2816 #: ../en/ch02-tour-basic.xml:266
2817 msgid ""
2818 "Graphical history of the <filename class=\"directory\">hello</filename> "
2819 "repository"
2820 msgstr ""
2822 #. type: Content of: <book><chapter><sect1><sect2><title>
2823 #: ../en/ch02-tour-basic.xml:273
2824 msgid "Changesets, revisions, and talking to other people"
2825 msgstr "改变集，版本，与其它用户交互"
2827 #. type: Content of: <book><chapter><sect1><sect2><para>
2828 #: ../en/ch02-tour-basic.xml:276
2829 msgid ""
2830 "As English is a notoriously sloppy language, and computer science has a "
2831 "hallowed history of terminological confusion (why use one term when four will "
2832 "do?), revision control has a variety of words and phrases that mean the same "
2833 "thing. If you are talking about Mercurial history with other people, you "
2834 "will find that the word <quote>changeset</quote> is often compressed to "
2835 "<quote>change</quote> or (when written) <quote>cset</quote>, and sometimes a "
2836 "changeset is referred to as a <quote>revision</quote> or a <quote>rev</quote>."
2837 msgstr ""
2839 #. type: Content of: <book><chapter><sect1><sect2><para>
2840 #: ../en/ch02-tour-basic.xml:286
2841 msgid ""
2842 "While it doesn't matter what <emphasis>word</emphasis> you use to refer to "
2843 "the concept of <quote>a changeset</quote>, the <emphasis>identifier</"
2844 "emphasis> that you use to refer to <quote>a <emphasis>specific</emphasis> "
2845 "changeset</quote> is of great importance. Recall that the <literal>changeset</"
2846 "literal> field in the output from <command role=\"hg-cmd\">hg log</command> "
2847 "identifies a changeset using both a number and a hexadecimal string."
2848 msgstr ""
2850 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
2851 #: ../en/ch02-tour-basic.xml:295
2852 msgid ""
2853 "The revision number is <emphasis>only valid in that repository</emphasis>,"
2854 msgstr ""
2856 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
2857 #: ../en/ch02-tour-basic.xml:297
2858 msgid ""
2859 "while the hex string is the <emphasis>permanent, unchanging identifier</"
2860 "emphasis> that will always identify that exact changeset in <emphasis>every</"
2861 "emphasis> copy of the repository."
2862 msgstr ""
2864 #. type: Content of: <book><chapter><sect1><sect2><para>
2865 #: ../en/ch02-tour-basic.xml:302
2866 msgid ""
2867 "This distinction is important. If you send someone an email talking about "
2868 "<quote>revision 33</quote>, there's a high likelihood that their revision 33 "
2869 "will <emphasis>not be the same</emphasis> as yours. The reason for this is "
2870 "that a revision number depends on the order in which changes arrived in a "
2871 "repository, and there is no guarantee that the same changes will happen in "
2872 "the same order in different repositories. Three changes $a,b,c$ can easily "
2873 "appear in one repository as $0,1,2$, while in another as $1,0,2$."
2874 msgstr ""
2876 #. type: Content of: <book><chapter><sect1><sect2><para>
2877 #: ../en/ch02-tour-basic.xml:312
2878 msgid ""
2879 "Mercurial uses revision numbers purely as a convenient shorthand. If you "
2880 "need to discuss a changeset with someone, or make a record of a changeset for "
2881 "some other reason (for example, in a bug report), use the hexadecimal "
2882 "identifier."
2883 msgstr ""
2885 #. type: Content of: <book><chapter><sect1><sect2><title>
2886 #: ../en/ch02-tour-basic.xml:320
2887 msgid "Viewing specific revisions"
2888 msgstr "察看指定版本"
2890 #. type: Content of: <book><chapter><sect1><sect2><para>
2891 #: ../en/ch02-tour-basic.xml:322
2892 msgid ""
2893 "To narrow the output of <command role=\"hg-cmd\">hg log</command> down to a "
2894 "single revision, use the <option role=\"hg-opt-log\">-r</option> (or <option "
2895 "role=\"hg-opt-log\">--rev</option>) option. You can use either a revision "
2896 "number or a long-form changeset identifier, and you can provide as many "
2897 "revisions as you want."
2898 msgstr ""
2900 #. type: Content of: <book><chapter><sect1><sect2><para>
2901 #: ../en/ch02-tour-basic.xml:331
2902 msgid ""
2903 "If you want to see the history of several revisions without having to list "
2904 "each one, you can use <emphasis>range notation</emphasis>; this lets you "
2905 "express the idea <quote>I want all revisions between <literal>abc</literal> "
2906 "and <literal>def</literal>, inclusive</quote>."
2907 msgstr ""
2909 #. type: Content of: <book><chapter><sect1><sect2><para>
2910 #: ../en/ch02-tour-basic.xml:339
2911 msgid ""
2912 "Mercurial also honours the order in which you specify revisions, so <command "
2913 "role=\"hg-cmd\">hg log -r 2:4</command> prints 2, 3, and 4. while <command "
2914 "role=\"hg-cmd\">hg log -r 4:2</command> prints 4, 3, and 2."
2915 msgstr ""
2917 #. type: Content of: <book><chapter><sect1><sect2><title>
2918 #: ../en/ch02-tour-basic.xml:346
2919 msgid "More detailed information"
2920 msgstr "更详细的信息"
2922 #. type: Content of: <book><chapter><sect1><sect2><para>
2923 #: ../en/ch02-tour-basic.xml:348
2924 msgid ""
2925 "While the summary information printed by <command role=\"hg-cmd\">hg log</"
2926 "command> is useful if you already know what you're looking for, you may need "
2927 "to see a complete description of the change, or a list of the files changed, "
2928 "if you're trying to decide whether a changeset is the one you're looking for. "
2929 "The <command role=\"hg-cmd\">hg log</command> command's <option role=\"hg-opt-"
2930 "global\">-v</option> (or <option role=\"hg-opt-global\">--verbose</option>) "
2931 "option gives you this extra detail."
2932 msgstr ""
2934 #. type: Content of: <book><chapter><sect1><sect2><para>
2935 #: ../en/ch02-tour-basic.xml:360
2936 msgid ""
2937 "If you want to see both the description and content of a change, add the "
2938 "<option role=\"hg-opt-log\">-p</option> (or <option role=\"hg-opt-log\">--"
2939 "patch</option>) option. This displays the content of a change as a "
2940 "<emphasis>unified diff</emphasis> (if you've never seen a unified diff "
2941 "before, see section <xref linkend=\"sec.mq.patch\"/> for an overview)."
2942 msgstr ""
2944 #. type: Content of: <book><chapter><sect1><title>
2945 #: ../en/ch02-tour-basic.xml:373
2946 msgid "All about command options"
2947 msgstr "命令选项"
2949 #. type: Content of: <book><chapter><sect1><para>
2950 #: ../en/ch02-tour-basic.xml:375
2951 msgid ""
2952 "Let's take a brief break from exploring Mercurial commands to discuss a "
2953 "pattern in the way that they work; you may find this useful to keep in mind "
2954 "as we continue our tour."
2955 msgstr ""
2957 #. type: Content of: <book><chapter><sect1><para>
2958 #: ../en/ch02-tour-basic.xml:379
2959 msgid ""
2960 "Mercurial has a consistent and straightforward approach to dealing with the "
2961 "options that you can pass to commands. It follows the conventions for "
2962 "options that are common to modern Linux and Unix systems."
2963 msgstr ""
2965 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2966 #: ../en/ch02-tour-basic.xml:384
2967 msgid ""
2968 "Every option has a long name. For example, as we've already seen, the "
2969 "<command role=\"hg-cmd\">hg log</command> command accepts a <option role=\"hg-"
2970 "opt-log\">--rev</option> option."
2971 msgstr ""
2973 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2974 #: ../en/ch02-tour-basic.xml:388
2975 msgid ""
2976 "Most options have short names, too. Instead of <option role=\"hg-opt-log\">--"
2977 "rev</option>, we can use <option role=\"hg-opt-log\">-r</option>. (The "
2978 "reason that some options don't have short names is that the options in "
2979 "question are rarely used.)"
2980 msgstr ""
2982 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2983 #: ../en/ch02-tour-basic.xml:393
2984 msgid ""
2985 "Long options start with two dashes (e.g. <option role=\"hg-opt-log\">--rev</"
2986 "option>), while short options start with one (e.g. <option role=\"hg-opt-log"
2987 "\">-r</option>)."
2988 msgstr ""
2990 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
2991 #: ../en/ch02-tour-basic.xml:397
2992 msgid ""
2993 "Option naming and usage is consistent across commands. For example, every "
2994 "command that lets you specify a changeset ID or revision number accepts both "
2995 "<option role=\"hg-opt-log\">-r</option> and <option role=\"hg-opt-log\">--"
2996 "rev</option> arguments."
2997 msgstr ""
2999 #. type: Content of: <book><chapter><sect1><para>
3000 #: ../en/ch02-tour-basic.xml:403
3001 msgid ""
3002 "In the examples throughout this book, I use short options instead of long. "
3003 "This just reflects my own preference, so don't read anything significant into "
3004 "it."
3005 msgstr ""
3007 #. type: Content of: <book><chapter><sect1><para>
3008 #: ../en/ch02-tour-basic.xml:407
3009 msgid ""
3010 "Most commands that print output of some kind will print more output when "
3011 "passed a <option role=\"hg-opt-global\">-v</option> (or <option role=\"hg-opt-"
3012 "global\">--verbose</option>) option, and less when passed <option role=\"hg-"
3013 "opt-global\">-q</option> (or <option role=\"hg-opt-global\">--quiet</option>)."
3014 msgstr ""
3016 #. type: Content of: <book><chapter><sect1><title>
3017 #: ../en/ch02-tour-basic.xml:415
3018 msgid "Making and reviewing changes"
3019 msgstr "创建和复审修改"
3021 #. type: Content of: <book><chapter><sect1><para>
3022 #: ../en/ch02-tour-basic.xml:417
3023 msgid ""
3024 "Now that we have a grasp of viewing history in Mercurial, let's take a look "
3025 "at making some changes and examining them."
3026 msgstr ""
3028 #. type: Content of: <book><chapter><sect1><para>
3029 #: ../en/ch02-tour-basic.xml:421
3030 msgid ""
3031 "The first thing we'll do is isolate our experiment in a repository of its "
3032 "own. We use the <command role=\"hg-cmd\">hg clone</command> command, but we "
3033 "don't need to clone a copy of the remote repository. Since we already have a "
3034 "copy of it locally, we can just clone that instead. This is much faster than "
3035 "cloning over the network, and cloning a local repository uses less disk space "
3036 "in most cases, too."
3037 msgstr ""
3039 #. type: Content of: <book><chapter><sect1><para>
3040 #: ../en/ch02-tour-basic.xml:431
3041 msgid ""
3042 "As an aside, it's often good practice to keep a <quote>pristine</quote> copy "
3043 "of a remote repository around, which you can then make temporary clones of to "
3044 "create sandboxes for each task you want to work on. This lets you work on "
3045 "multiple tasks in parallel, each isolated from the others until it's complete "
3046 "and you're ready to integrate it back. Because local clones are so cheap, "
3047 "there's almost no overhead to cloning and destroying repositories whenever "
3048 "you want."
3049 msgstr ""
3051 #. type: Content of: <book><chapter><sect1><para>
3052 #: ../en/ch02-tour-basic.xml:440
3053 msgid ""
3054 "In our <filename class=\"directory\">my-hello</filename> repository, we have "
3055 "a file <filename>hello.c</filename> that contains the classic <quote>hello, "
3056 "world</quote> program. Let's use the ancient and venerable <command>sed</"
3057 "command> command to edit this file so that it prints a second line of "
3058 "output. (I'm only using <command>sed</command> to do this because it's easy "
3059 "to write a scripted example this way. Since you're not under the same "
3060 "constraint, you probably won't want to use <command>sed</command>; simply use "
3061 "your preferred text editor to do the same thing.)"
3062 msgstr ""
3064 #. type: Content of: <book><chapter><sect1><para>
3065 #: ../en/ch02-tour-basic.xml:453
3066 msgid ""
3067 "Mercurial's <command role=\"hg-cmd\">hg status</command> command will tell us "
3068 "what Mercurial knows about the files in the repository."
3069 msgstr ""
3071 #. type: Content of: <book><chapter><sect1><para>
3072 #: ../en/ch02-tour-basic.xml:459
3073 msgid ""
3074 "The <command role=\"hg-cmd\">hg status</command> command prints no output for "
3075 "some files, but a line starting with <quote><literal>M</literal></quote> for "
3076 "<filename>hello.c</filename>. Unless you tell it to, <command role=\"hg-cmd"
3077 "\">hg status</command> will not print any output for files that have not been "
3078 "modified."
3079 msgstr ""
3081 #. type: Content of: <book><chapter><sect1><para>
3082 #: ../en/ch02-tour-basic.xml:466
3083 msgid ""
3084 "The <quote><literal>M</literal></quote> indicates that Mercurial has noticed "
3085 "that we modified <filename>hello.c</filename>. We didn't need to "
3086 "<emphasis>inform</emphasis> Mercurial that we were going to modify the file "
3087 "before we started, or that we had modified the file after we were done; it "
3088 "was able to figure this out itself."
3089 msgstr ""
3091 #. type: Content of: <book><chapter><sect1><para>
3092 #: ../en/ch02-tour-basic.xml:474
3093 msgid ""
3094 "It's a little bit helpful to know that we've modified <filename>hello.c</"
3095 "filename>, but we might prefer to know exactly <emphasis>what</emphasis> "
3096 "changes we've made to it. To do this, we use the <command role=\"hg-cmd\">hg "
3097 "diff</command> command."
3098 msgstr ""
3100 #. type: Content of: <book><chapter><sect1><title>
3101 #: ../en/ch02-tour-basic.xml:484
3102 msgid "Recording changes in a new changeset"
3103 msgstr "在新修改集中记录修改"
3105 #. type: Content of: <book><chapter><sect1><para>
3106 #: ../en/ch02-tour-basic.xml:486
3107 msgid ""
3108 "We can modify files, build and test our changes, and use <command role=\"hg-"
3109 "cmd\">hg status</command> and <command role=\"hg-cmd\">hg diff</command> to "
3110 "review our changes, until we're satisfied with what we've done and arrive at "
3111 "a natural stopping point where we want to record our work in a new changeset."
3112 msgstr ""
3114 #. type: Content of: <book><chapter><sect1><para>
3115 #: ../en/ch02-tour-basic.xml:493
3116 msgid ""
3117 "The <command role=\"hg-cmd\">hg commit</command> command lets us create a new "
3118 "changeset; we'll usually refer to this as <quote>making a commit</quote> or "
3119 "<quote>committing</quote>."
3120 msgstr ""
3122 #. type: Content of: <book><chapter><sect1><sect2><title>
3123 #: ../en/ch02-tour-basic.xml:499
3124 msgid "Setting up a username"
3125 msgstr "配置用户名称"
3127 #. type: Content of: <book><chapter><sect1><sect2><para>
3128 #: ../en/ch02-tour-basic.xml:501
3129 msgid ""
3130 "When you try to run <command role=\"hg-cmd\">hg commit</command> for the "
3131 "first time, it is not guaranteed to succeed. Mercurial records your name and "
3132 "address with each change that you commit, so that you and others will later "
3133 "be able to tell who made each change. Mercurial tries to automatically "
3134 "figure out a sensible username to commit the change with. It will attempt "
3135 "each of the following methods, in order:"
3136 msgstr ""
3138 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
3139 #: ../en/ch02-tour-basic.xml:510
3140 msgid ""
3141 "If you specify a <option role=\"hg-opt-commit\">-u</option> option to the "
3142 "<command role=\"hg-cmd\">hg commit</command> command on the command line, "
3143 "followed by a username, this is always given the highest precedence."
3144 msgstr ""
3146 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
3147 #: ../en/ch02-tour-basic.xml:515
3148 msgid ""
3149 "If you have set the <envar>HGUSER</envar> environment variable, this is "
3150 "checked next."
3151 msgstr ""
3153 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
3154 #: ../en/ch02-tour-basic.xml:518
3155 msgid ""
3156 "If you create a file in your home directory called <filename role=\"special"
3157 "\">.hgrc</filename>, with a <envar role=\"rc-item-ui\">username</envar> "
3158 "entry, that will be used next. To see what the contents of this file should "
3159 "look like, refer to section <xref linkend=\"sec.tour-basic.username\"/> below."
3160 msgstr ""
3162 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
3163 #: ../en/ch02-tour-basic.xml:525
3164 msgid ""
3165 "If you have set the <envar>EMAIL</envar> environment variable, this will be "
3166 "used next."
3167 msgstr ""
3169 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
3170 #: ../en/ch02-tour-basic.xml:528
3171 msgid ""
3172 "Mercurial will query your system to find out your local user name and host "
3173 "name, and construct a username from these components. Since this often "
3174 "results in a username that is not very useful, it will print a warning if it "
3175 "has to do this."
3176 msgstr ""
3178 #. type: Content of: <book><chapter><sect1><sect2><para>
3179 #: ../en/ch02-tour-basic.xml:535
3180 msgid ""
3181 "If all of these mechanisms fail, Mercurial will fail, printing an error "
3182 "message. In this case, it will not let you commit until you set up a "
3183 "username."
3184 msgstr ""
3186 #. type: Content of: <book><chapter><sect1><sect2><para>
3187 #: ../en/ch02-tour-basic.xml:539
3188 msgid ""
3189 "You should think of the <envar>HGUSER</envar> environment variable and the "
3190 "<option role=\"hg-opt-commit\">-u</option> option to the <command role=\"hg-"
3191 "cmd\">hg commit</command> command as ways to <emphasis>override</emphasis> "
3192 "Mercurial's default selection of username. For normal use, the simplest and "
3193 "most robust way to set a username for yourself is by creating a <filename "
3194 "role=\"special\">.hgrc</filename> file; see below for details."
3195 msgstr ""
3197 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
3198 #: ../en/ch02-tour-basic.xml:548
3199 msgid "Creating a Mercurial configuration file"
3200 msgstr "创建 Mercurial 的配置文件"
3202 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
3203 #: ../en/ch02-tour-basic.xml:550
3204 msgid ""
3205 "To set a user name, use your favourite editor to create a file called "
3206 "<filename role=\"special\">.hgrc</filename> in your home directory. "
3207 "Mercurial will use this file to look up your personalised configuration "
3208 "settings. The initial contents of your <filename role=\"special\">.hgrc</"
3209 "filename> should look like this."
3210 msgstr ""
3212 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
3213 #: ../en/ch02-tour-basic.xml:561
3214 msgid ""
3215 "The <quote><literal>[ui]</literal></quote> line begins a <emphasis>section</"
3216 "emphasis> of the config file, so you can read the <quote><literal>username "
3217 "= ...</literal></quote> line as meaning <quote>set the value of the "
3218 "<literal>username</literal> item in the <literal>ui</literal> section</"
3219 "quote>. A section continues until a new section begins, or the end of the "
3220 "file. Mercurial ignores empty lines and treats any text from "
3221 "<quote><literal>#</literal></quote> to the end of a line as a comment."
3222 msgstr ""
3224 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
3225 #: ../en/ch02-tour-basic.xml:574
3226 msgid "Choosing a user name"
3227 msgstr "选择用户名称"
3229 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
3230 #: ../en/ch02-tour-basic.xml:576
3231 msgid ""
3232 "You can use any text you like as the value of the <literal>username</literal> "
3233 "config item, since this information is for reading by other people, but for "
3234 "interpreting by Mercurial. The convention that most people follow is to use "
3235 "their name and email address, as in the example above."
3236 msgstr ""
3238 #. type: Content of: <book><chapter><sect1><sect2><sect3><note><para>
3239 #: ../en/ch02-tour-basic.xml:583
3240 msgid ""
3241 "Mercurial's built-in web server obfuscates email addresses, to make it more "
3242 "difficult for the email harvesting tools that spammers use. This reduces the "
3243 "likelihood that you'll start receiving more junk email if you publish a "
3244 "Mercurial repository on the web."
3245 msgstr ""
3247 #. type: Content of: <book><chapter><sect1><sect2><title>
3248 #: ../en/ch02-tour-basic.xml:593
3249 msgid "Writing a commit message"
3250 msgstr "写提交日志"
3252 #. type: Content of: <book><chapter><sect1><sect2><para>
3253 #: ../en/ch02-tour-basic.xml:595
3254 msgid ""
3255 "When we commit a change, Mercurial drops us into a text editor, to enter a "
3256 "message that will describe the modifications we've made in this changeset. "
3257 "This is called the <emphasis>commit message</emphasis>. It will be a record "
3258 "for readers of what we did and why, and it will be printed by <command role="
3259 "\"hg-cmd\">hg log</command> after we've finished committing."
3260 msgstr ""
3262 #. type: Content of: <book><chapter><sect1><sect2><para>
3263 #: ../en/ch02-tour-basic.xml:605
3264 msgid ""
3265 "The editor that the <command role=\"hg-cmd\">hg commit</command> command "
3266 "drops us into will contain an empty line, followed by a number of lines "
3267 "starting with <quote><literal>HG:</literal></quote>."
3268 msgstr ""
3270 #. type: Content of: <book><chapter><sect1><sect2><para>
3271 #: ../en/ch02-tour-basic.xml:612
3272 msgid ""
3273 "Mercurial ignores the lines that start with <quote><literal>HG:</literal></"
3274 "quote>; it uses them only to tell us which files it's recording changes to. "
3275 "Modifying or deleting these lines has no effect."
3276 msgstr ""
3278 #. type: Content of: <book><chapter><sect1><sect2><title>
3279 #: ../en/ch02-tour-basic.xml:618
3280 msgid "Writing a good commit message"
3281 msgstr "写好提交日志"
3283 #. type: Content of: <book><chapter><sect1><sect2><para>
3284 #: ../en/ch02-tour-basic.xml:620
3285 msgid ""
3286 "Since <command role=\"hg-cmd\">hg log</command> only prints the first line of "
3287 "a commit message by default, it's best to write a commit message whose first "
3288 "line stands alone. Here's a real example of a commit message that "
3289 "<emphasis>doesn't</emphasis> follow this guideline, and hence has a summary "
3290 "that is not readable."
3291 msgstr ""
3293 #. type: Content of: <book><chapter><sect1><sect2><para>
3294 #: ../en/ch02-tour-basic.xml:634
3295 msgid ""
3296 "As far as the remainder of the contents of the commit message are concerned, "
3297 "there are no hard-and-fast rules. Mercurial itself doesn't interpret or care "
3298 "about the contents of the commit message, though your project may have "
3299 "policies that dictate a certain kind of formatting."
3300 msgstr ""
3302 #. type: Content of: <book><chapter><sect1><sect2><para>
3303 #: ../en/ch02-tour-basic.xml:640
3304 msgid ""
3305 "My personal preference is for short, but informative, commit messages that "
3306 "tell me something that I can't figure out with a quick glance at the output "
3307 "of <command role=\"hg-cmd\">hg log --patch</command>."
3308 msgstr ""
3310 #. type: Content of: <book><chapter><sect1><sect2><title>
3311 #: ../en/ch02-tour-basic.xml:647
3312 msgid "Aborting a commit"
3313 msgstr "终止提交"
3315 #. type: Content of: <book><chapter><sect1><sect2><para>
3316 #: ../en/ch02-tour-basic.xml:649
3317 msgid ""
3318 "If you decide that you don't want to commit while in the middle of editing a "
3319 "commit message, simply exit from your editor without saving the file that "
3320 "it's editing. This will cause nothing to happen to either the repository or "
3321 "the working directory."
3322 msgstr ""
3324 #. type: Content of: <book><chapter><sect1><sect2><para>
3325 #: ../en/ch02-tour-basic.xml:654
3326 msgid ""
3327 "If we run the <command role=\"hg-cmd\">hg commit</command> command without "
3328 "any arguments, it records all of the changes we've made, as reported by "
3329 "<command role=\"hg-cmd\">hg status</command> and <command role=\"hg-cmd\">hg "
3330 "diff</command>."
3331 msgstr ""
3333 #. type: Content of: <book><chapter><sect1><sect2><title>
3334 #: ../en/ch02-tour-basic.xml:661
3335 msgid "Admiring our new handiwork"
3336 msgstr "欣赏我们的新手艺"
3338 #. type: Content of: <book><chapter><sect1><sect2><para>
3339 #: ../en/ch02-tour-basic.xml:663
3340 msgid ""
3341 "Once we've finished the commit, we can use the <command role=\"hg-cmd\">hg "
3342 "tip</command> command to display the changeset we just created. This command "
3343 "produces output that is identical to <command role=\"hg-cmd\">hg log</"
3344 "command>, but it only displays the newest revision in the repository."
3345 msgstr ""
3347 #. type: Content of: <book><chapter><sect1><sect2><para>
3348 #: ../en/ch02-tour-basic.xml:672
3349 msgid ""
3350 "We refer to the newest revision in the repository as the tip revision, or "
3351 "simply the tip."
3352 msgstr ""
3354 #. type: Content of: <book><chapter><sect1><title>
3355 #: ../en/ch02-tour-basic.xml:679
3356 msgid "Sharing changes"
3357 msgstr "共享修改"
3359 #. type: Content of: <book><chapter><sect1><para>
3360 #: ../en/ch02-tour-basic.xml:681
3361 msgid ""
3362 "We mentioned earlier that repositories in Mercurial are self-contained. This "
3363 "means that the changeset we just created exists only in our <filename class="
3364 "\"directory\">my-hello</filename> repository. Let's look at a few ways that "
3365 "we can propagate this change into other repositories."
3366 msgstr ""
3368 #. type: Content of: <book><chapter><sect1><sect2><title>
3369 #: ../en/ch02-tour-basic.xml:689
3370 msgid "Pulling changes from another repository"
3371 msgstr "从其它版本库取得修改"
3373 #. type: Content of: <book><chapter><sect1><sect2><para>
3374 #: ../en/ch02-tour-basic.xml:690
3375 msgid ""
3376 "To get started, let's clone our original <filename class=\"directory\">hello</"
3377 "filename> repository, which does not contain the change we just committed. "
3378 "We'll call our temporary repository <filename class=\"directory\">hello-pull</"
3379 "filename>."
3380 msgstr ""
3382 #. type: Content of: <book><chapter><sect1><sect2><para>
3383 #: ../en/ch02-tour-basic.xml:698
3384 msgid ""
3385 "We'll use the <command role=\"hg-cmd\">hg pull</command> command to bring "
3386 "changes from <filename class=\"directory\">my-hello</filename> into <filename "
3387 "class=\"directory\">hello-pull</filename>. However, blindly pulling unknown "
3388 "changes into a repository is a somewhat scary prospect. Mercurial provides "
3389 "the <command role=\"hg-cmd\">hg incoming</command> command to tell us what "
3390 "changes the <command role=\"hg-cmd\">hg pull</command> command "
3391 "<emphasis>would</emphasis> pull into the repository, without actually pulling "
3392 "the changes in."
3393 msgstr ""
3395 #. type: Content of: <book><chapter><sect1><sect2><para>
3396 #: ../en/ch02-tour-basic.xml:711
3397 msgid ""
3398 "(Of course, someone could cause more changesets to appear in the repository "
3399 "that we ran <command role=\"hg-cmd\">hg incoming</command> in, before we get "
3400 "a chance to <command role=\"hg-cmd\">hg pull</command> the changes, so that "
3401 "we could end up pulling changes that we didn't expect.)"
3402 msgstr ""
3404 #. type: Content of: <book><chapter><sect1><sect2><para>
3405 #: ../en/ch02-tour-basic.xml:718
3406 msgid ""
3407 "Bringing changes into a repository is a simple matter of running the <command "
3408 "role=\"hg-cmd\">hg pull</command> command, and telling it which repository to "
3409 "pull from."
3410 msgstr ""
3412 #. type: Content of: <book><chapter><sect1><sect2><para>
3413 #: ../en/ch02-tour-basic.xml:725
3414 msgid ""
3415 "As you can see from the before-and-after output of <command role=\"hg-cmd"
3416 "\">hg tip</command>, we have successfully pulled changes into our "
3417 "repository. There remains one step before we can see these changes in the "
3418 "working directory."
3419 msgstr ""
3421 #. type: Content of: <book><chapter><sect1><sect2><title>
3422 #: ../en/ch02-tour-basic.xml:733
3423 msgid "Updating the working directory"
3424 msgstr "更新工作目录"
3426 #. type: Content of: <book><chapter><sect1><sect2><para>
3427 #: ../en/ch02-tour-basic.xml:735
3428 msgid ""
3429 "We have so far glossed over the relationship between a repository and its "
3430 "working directory. The <command role=\"hg-cmd\">hg pull</command> command "
3431 "that we ran in section <xref linkend=\"sec.tour.pull\"/> brought changes into "
3432 "the repository, but if we check, there's no sign of those changes in the "
3433 "working directory. This is because <command role=\"hg-cmd\">hg pull</"
3434 "command> does not (by default) touch the working directory. Instead, we use "
3435 "the <command role=\"hg-cmd\">hg update</command> command to do this."
3436 msgstr ""
3438 #. type: Content of: <book><chapter><sect1><sect2><para>
3439 #: ../en/ch02-tour-basic.xml:747
3440 msgid ""
3441 "It might seem a bit strange that <command role=\"hg-cmd\">hg pull</command> "
3442 "doesn't update the working directory automatically. There's actually a good "
3443 "reason for this: you can use <command role=\"hg-cmd\">hg update</command> to "
3444 "update the working directory to the state it was in at <emphasis>any "
3445 "revision</emphasis> in the history of the repository. If you had the working "
3446 "directory updated to an old revision---to hunt down the origin of a bug, "
3447 "say---and ran a <command role=\"hg-cmd\">hg pull</command> which "
3448 "automatically updated the working directory to a new revision, you might not "
3449 "be terribly happy."
3450 msgstr ""
3452 #. type: Content of: <book><chapter><sect1><sect2><para>
3453 #: ../en/ch02-tour-basic.xml:758
3454 msgid ""
3455 "However, since pull-then-update is such a common thing to do, Mercurial lets "
3456 "you combine the two by passing the <option role=\"hg-opt-pull\">-u</option> "
3457 "option to <command role=\"hg-cmd\">hg pull</command>."
3458 msgstr ""
3460 #. type: Content of: <book><chapter><sect1><sect2><para>
3461 #: ../en/ch02-tour-basic.xml:763
3462 msgid ""
3463 "If you look back at the output of <command role=\"hg-cmd\">hg pull</command> "
3464 "in section <xref linkend=\"sec.tour.pull\"/> when we ran it without <option "
3465 "role=\"hg-opt-pull\">-u</option>, you can see that it printed a helpful "
3466 "reminder that we'd have to take an explicit step to update the working "
3467 "directory:"
3468 msgstr ""
3470 #. type: Content of: <book><chapter><sect1><sect2><para>
3471 #: ../en/ch02-tour-basic.xml:772
3472 msgid ""
3473 "To find out what revision the working directory is at, use the <command role="
3474 "\"hg-cmd\">hg parents</command> command."
3475 msgstr ""
3477 #. type: Content of: <book><chapter><sect1><sect2><para>
3478 #: ../en/ch02-tour-basic.xml:778
3479 msgid ""
3480 "If you look back at figure <xref endterm=\"fig.tour-basic.history.caption\" "
3481 "linkend=\"fig.tour-basic.history\"/>, you'll see arrows connecting each "
3482 "changeset. The node that the arrow leads <emphasis>from</emphasis> in each "
3483 "case is a parent, and the node that the arrow leads <emphasis>to</emphasis> "
3484 "is its child. The working directory has a parent in just the same way; this "
3485 "is the changeset that the working directory currently contains."
3486 msgstr ""
3488 #. type: Content of: <book><chapter><sect1><sect2><para>
3489 #: ../en/ch02-tour-basic.xml:788
3490 msgid ""
3491 "To update the working directory to a particular revision, give a revision "
3492 "number or changeset ID to the <command role=\"hg-cmd\">hg update</command> "
3493 "command."
3494 msgstr ""
3496 #. type: Content of: <book><chapter><sect1><sect2><para>
3497 #: ../en/ch02-tour-basic.xml:795
3498 msgid ""
3499 "If you omit an explicit revision, <command role=\"hg-cmd\">hg update</"
3500 "command> will update to the tip revision, as shown by the second call to "
3501 "<command role=\"hg-cmd\">hg update</command> in the example above."
3502 msgstr ""
3504 #. type: Content of: <book><chapter><sect1><sect2><title>
3505 #: ../en/ch02-tour-basic.xml:803
3506 msgid "Pushing changes to another repository"
3507 msgstr "发布修改到其它版本库"
3509 #. type: Content of: <book><chapter><sect1><sect2><para>
3510 #: ../en/ch02-tour-basic.xml:805
3511 msgid ""
3512 "Mercurial lets us push changes to another repository, from the repository "
3513 "we're currently visiting. As with the example of <command role=\"hg-cmd\">hg "
3514 "pull</command> above, we'll create a temporary repository to push our changes "
3515 "into."
3516 msgstr ""
3518 #. type: Content of: <book><chapter><sect1><sect2><para>
3519 #: ../en/ch02-tour-basic.xml:813
3520 msgid ""
3521 "The <command role=\"hg-cmd\">hg outgoing</command> command tells us what "
3522 "changes would be pushed into another repository."
3523 msgstr ""
3525 #. type: Content of: <book><chapter><sect1><sect2><para>
3526 #: ../en/ch02-tour-basic.xml:819
3527 msgid ""
3528 "And the <command role=\"hg-cmd\">hg push</command> command does the actual "
3529 "push."
3530 msgstr ""
3532 #. type: Content of: <book><chapter><sect1><sect2><para>
3533 #: ../en/ch02-tour-basic.xml:825
3534 msgid ""
3535 "As with <command role=\"hg-cmd\">hg pull</command>, the <command role=\"hg-cmd"
3536 "\">hg push</command> command does not update the working directory in the "
3537 "repository that it's pushing changes into. (Unlike <command role=\"hg-cmd"
3538 "\">hg pull</command>, <command role=\"hg-cmd\">hg push</command> does not "
3539 "provide a <literal>-u</literal> option that updates the other repository's "
3540 "working directory.)"
3541 msgstr ""
3543 #. type: Content of: <book><chapter><sect1><sect2><para>
3544 #: ../en/ch02-tour-basic.xml:834
3545 msgid ""
3546 "What happens if we try to pull or push changes and the receiving repository "
3547 "already has those changes? Nothing too exciting."
3548 msgstr ""
3550 #. type: Content of: <book><chapter><sect1><sect2><title>
3551 #: ../en/ch02-tour-basic.xml:841
3552 msgid "Sharing changes over a network"
3553 msgstr "通过网络共享修改"
3555 #. type: Content of: <book><chapter><sect1><sect2><para>
3556 #: ../en/ch02-tour-basic.xml:843
3557 msgid ""
3558 "The commands we have covered in the previous few sections are not limited to "
3559 "working with local repositories. Each works in exactly the same fashion over "
3560 "a network connection; simply pass in a URL instead of a local path."
3561 msgstr ""
3563 #. type: Content of: <book><chapter><sect1><sect2><para>
3564 #: ../en/ch02-tour-basic.xml:851
3565 msgid ""
3566 "In this example, we can see what changes we could push to the remote "
3567 "repository, but the repository is understandably not set up to let anonymous "
3568 "users push to it."
3569 msgstr ""
3571 #. type: Content of: <book><chapter><title>
3572 #: ../en/ch03-tour-merge.xml:5
3573 msgid "A tour of Mercurial: merging work"
3574 msgstr "Mercurial 教程: 合并工作"
3576 #. type: Content of: <book><chapter><para>
3577 #: ../en/ch03-tour-merge.xml:7
3578 msgid ""
3579 "We've now covered cloning a repository, making changes in a repository, and "
3580 "pulling or pushing changes from one repository into another. Our next step "
3581 "is <emphasis>merging</emphasis> changes from separate repositories."
3582 msgstr ""
3584 #. type: Content of: <book><chapter><sect1><title>
3585 #: ../en/ch03-tour-merge.xml:13
3586 msgid "Merging streams of work"
3587 msgstr "合并的流程"
3589 #. type: Content of: <book><chapter><sect1><para>
3590 #: ../en/ch03-tour-merge.xml:15
3591 msgid ""
3592 "Merging is a fundamental part of working with a distributed revision control "
3593 "tool."
3594 msgstr ""
3596 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
3597 #: ../en/ch03-tour-merge.xml:18
3598 msgid ""
3599 "Alice and Bob each have a personal copy of a repository for a project they're "
3600 "collaborating on. Alice fixes a bug in her repository; Bob adds a new "
3601 "feature in his. They want the shared repository to contain both the bug fix "
3602 "and the new feature."
3603 msgstr ""
3605 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
3606 #: ../en/ch03-tour-merge.xml:24
3607 msgid ""
3608 "I frequently work on several different tasks for a single project at once, "
3609 "each safely isolated in its own repository. Working this way means that I "
3610 "often need to merge one piece of my own work with another."
3611 msgstr ""
3613 #. type: Content of: <book><chapter><sect1><para>
3614 #: ../en/ch03-tour-merge.xml:30
3615 msgid ""
3616 "Because merging is such a common thing to need to do, Mercurial makes it "
3617 "easy. Let's walk through the process. We'll begin by cloning yet another "
3618 "repository (see how often they spring up?) and making a change in it."
3619 msgstr ""
3621 #. type: Content of: <book><chapter><sect1><para>
3622 #: ../en/ch03-tour-merge.xml:37
3623 msgid ""
3624 "We should now have two copies of <filename>hello.c</filename> with different "
3625 "contents. The histories of the two repositories have also diverged, as "
3626 "illustrated in figure <xref endterm=\"fig.tour-merge.sep-repos.caption\" "
3627 "linkend=\"fig.tour-merge.sep-repos\"/>."
3628 msgstr ""
3630 #. type: Content of: <book><chapter><sect1><informalfigure><mediaobject>
3631 #: ../en/ch03-tour-merge.xml:47
3632 msgid ""
3633 "<imageobject><imagedata fileref=\"images/tour-merge-sep-repos.png\"/></"
3634 "imageobject>"
3635 msgstr ""
3637 #. type: Content of: <book><chapter><sect1><informalfigure><mediaobject><caption><para>
3638 #: ../en/ch03-tour-merge.xml:49
3639 msgid ""
3640 "Divergent recent histories of the <filename class=\"directory\">my-hello</"
3641 "filename> and <filename class=\"directory\">my-new-hello</filename> "
3642 "repositories"
3643 msgstr ""
3645 #. type: Content of: <book><chapter><sect1><para>
3646 #: ../en/ch03-tour-merge.xml:57
3647 msgid ""
3648 "We already know that pulling changes from our <filename class=\"directory"
3649 "\">my-hello</filename> repository will have no effect on the working "
3650 "directory."
3651 msgstr ""
3653 #. type: Content of: <book><chapter><sect1><para>
3654 #: ../en/ch03-tour-merge.xml:63
3655 msgid ""
3656 "However, the <command role=\"hg-cmd\">hg pull</command> command says "
3657 "something about <quote>heads</quote>."
3658 msgstr ""
3660 #. type: Content of: <book><chapter><sect1><sect2><title>
3661 #: ../en/ch03-tour-merge.xml:67
3662 msgid "Head changesets"
3663 msgstr "顶点改变集"
3665 #. type: Content of: <book><chapter><sect1><sect2><para>
3666 #: ../en/ch03-tour-merge.xml:69
3667 msgid ""
3668 "A head is a change that has no descendants, or children, as they're also "
3669 "known. The tip revision is thus a head, because the newest revision in a "
3670 "repository doesn't have any children, but a repository can contain more than "
3671 "one head."
3672 msgstr ""
3674 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
3675 #: ../en/ch03-tour-merge.xml:77
3676 msgid ""
3677 "<imageobject><imagedata fileref=\"images/tour-merge-pull.png\"/></imageobject>"
3678 msgstr ""
3680 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
3681 #: ../en/ch03-tour-merge.xml:79
3682 msgid ""
3683 "Repository contents after pulling from <filename class=\"directory\">my-"
3684 "hello</filename> into <filename class=\"directory\">my-new-hello</filename>"
3685 msgstr ""
3687 #. type: Content of: <book><chapter><sect1><sect2><para>
3688 #: ../en/ch03-tour-merge.xml:85
3689 msgid ""
3690 "In figure <xref endterm=\"fig.tour-merge.pull.caption\" linkend=\"fig.tour-"
3691 "merge.pull\"/>, you can see the effect of the pull from <filename class="
3692 "\"directory\">my-hello</filename> into <filename class=\"directory\">my-new-"
3693 "hello</filename>. The history that was already present in <filename class="
3694 "\"directory\">my-new-hello</filename> is untouched, but a new revision has "
3695 "been added. By referring to figure <xref endterm=\"fig.tour-merge.sep-repos."
3696 "caption\" linkend=\"fig.tour-merge.sep-repos\"/>, we can see that the "
3697 "<emphasis>changeset ID</emphasis> remains the same in the new repository, but "
3698 "the <emphasis>revision number</emphasis> has changed. (This, incidentally, "
3699 "is a fine example of why it's not safe to use revision numbers when "
3700 "discussing changesets.) We can view the heads in a repository using the "
3701 "<command role=\"hg-cmd\">hg heads</command> command."
3702 msgstr ""
3704 #. type: Content of: <book><chapter><sect1><sect2><title>
3705 #: ../en/ch03-tour-merge.xml:106
3706 msgid "Performing the merge"
3707 msgstr "执行合并"
3709 #. type: Content of: <book><chapter><sect1><sect2><para>
3710 #: ../en/ch03-tour-merge.xml:108
3711 msgid ""
3712 "What happens if we try to use the normal <command role=\"hg-cmd\">hg update</"
3713 "command> command to update to the new tip?"
3714 msgstr ""
3716 #. type: Content of: <book><chapter><sect1><sect2><para>
3717 #: ../en/ch03-tour-merge.xml:114
3718 msgid ""
3719 "Mercurial is telling us that the <command role=\"hg-cmd\">hg update</command> "
3720 "command won't do a merge; it won't update the working directory when it "
3721 "thinks we might be wanting to do a merge, unless we force it to do so. "
3722 "Instead, we use the <command role=\"hg-cmd\">hg merge</command> command to "
3723 "merge the two heads."
3724 msgstr ""
3726 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
3727 #: ../en/ch03-tour-merge.xml:125
3728 msgid ""
3729 "<imageobject><imagedata fileref=\"images/tour-merge-merge.png\"/></"
3730 "imageobject>"
3731 msgstr ""
3733 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
3734 #: ../en/ch03-tour-merge.xml:127
3735 msgid "Working directory and repository during merge, and following commit"
3736 msgstr ""
3738 #. type: Content of: <book><chapter><sect1><sect2><para>
3739 #: ../en/ch03-tour-merge.xml:132
3740 msgid ""
3741 "This updates the working directory so that it contains changes from "
3742 "<emphasis>both</emphasis> heads, which is reflected in both the output of "
3743 "<command role=\"hg-cmd\">hg parents</command> and the contents of "
3744 "<filename>hello.c</filename>."
3745 msgstr ""
3747 #. type: Content of: <book><chapter><sect1><sect2><title>
3748 #: ../en/ch03-tour-merge.xml:142
3749 msgid "Committing the results of the merge"
3750 msgstr "提交合并结果"
3752 #. type: Content of: <book><chapter><sect1><sect2><para>
3753 #: ../en/ch03-tour-merge.xml:144
3754 msgid ""
3755 "Whenever we've done a merge, <command role=\"hg-cmd\">hg parents</command> "
3756 "will display two parents until we <command role=\"hg-cmd\">hg commit</"
3757 "command> the results of the merge."
3758 msgstr ""
3760 #. type: Content of: <book><chapter><sect1><sect2><para>
3761 #: ../en/ch03-tour-merge.xml:151
3762 msgid ""
3763 "We now have a new tip revision; notice that it has <emphasis>both</emphasis> "
3764 "of our former heads as its parents. These are the same revisions that were "
3765 "previously displayed by <command role=\"hg-cmd\">hg parents</command>."
3766 msgstr ""
3768 #. type: Content of: <book><chapter><sect1><sect2><para>
3769 #: ../en/ch03-tour-merge.xml:158
3770 msgid ""
3771 "In figure <xref endterm=\"fig.tour-merge.merge.caption\" linkend=\"fig.tour-"
3772 "merge.merge\"/>, you can see a representation of what happens to the working "
3773 "directory during the merge, and how this affects the repository when the "
3774 "commit happens. During the merge, the working directory has two parent "
3775 "changesets, and these become the parents of the new changeset."
3776 msgstr ""
3778 #. type: Content of: <book><chapter><sect1><title>
3779 #: ../en/ch03-tour-merge.xml:169
3780 msgid "Merging conflicting changes"
3781 msgstr "合并有冲突的改变"
3783 #. type: Content of: <book><chapter><sect1><para>
3784 #: ../en/ch03-tour-merge.xml:171
3785 msgid ""
3786 "Most merges are simple affairs, but sometimes you'll find yourself merging "
3787 "changes where each modifies the same portions of the same files. Unless both "
3788 "modifications are identical, this results in a <emphasis>conflict</emphasis>, "
3789 "where you have to decide how to reconcile the different changes into "
3790 "something coherent."
3791 msgstr ""
3793 #. type: Content of: <book><chapter><sect1><informalfigure><mediaobject>
3794 #: ../en/ch03-tour-merge.xml:180
3795 msgid ""
3796 "<imageobject><imagedata fileref=\"images/tour-merge-conflict.png\"/> </"
3797 "imageobject>"
3798 msgstr ""
3800 #. type: Content of: <book><chapter><sect1><informalfigure><mediaobject><caption><para>
3801 #: ../en/ch03-tour-merge.xml:183
3802 msgid "Conflicting changes to a document"
3803 msgstr ""
3805 #. type: Content of: <book><chapter><sect1><para>
3806 #: ../en/ch03-tour-merge.xml:188
3807 msgid ""
3808 "Figure <xref endterm=\"fig.tour-merge.conflict.caption\" linkend=\"fig.tour-"
3809 "merge.conflict\"/> illustrates an instance of two conflicting changes to a "
3810 "document. We started with a single version of the file; then we made some "
3811 "changes; while someone else made different changes to the same text. Our "
3812 "task in resolving the conflicting changes is to decide what the file should "
3813 "look like."
3814 msgstr ""
3816 #. type: Content of: <book><chapter><sect1><para>
3817 #: ../en/ch03-tour-merge.xml:196
3818 msgid ""
3819 "Mercurial doesn't have a built-in facility for handling conflicts. Instead, "
3820 "it runs an external program called <command>hgmerge</command>. This is a "
3821 "shell script that is bundled with Mercurial; you can change it to behave "
3822 "however you please. What it does by default is try to find one of several "
3823 "different merging tools that are likely to be installed on your system. It "
3824 "first tries a few fully automatic merging tools; if these don't succeed "
3825 "(because the resolution process requires human guidance) or aren't present, "
3826 "the script tries a few different graphical merging tools."
3827 msgstr ""
3829 #. type: Content of: <book><chapter><sect1><para>
3830 #: ../en/ch03-tour-merge.xml:207
3831 msgid ""
3832 "It's also possible to get Mercurial to run another program or script instead "
3833 "of <command>hgmerge</command>, by setting the <envar>HGMERGE</envar> "
3834 "environment variable to the name of your preferred program."
3835 msgstr ""
3837 #. type: Content of: <book><chapter><sect1><sect2><title>
3838 #: ../en/ch03-tour-merge.xml:213
3839 msgid "Using a graphical merge tool"
3840 msgstr "使用图形合并工具"
3842 #. type: Content of: <book><chapter><sect1><sect2><para>
3843 #: ../en/ch03-tour-merge.xml:215
3844 msgid ""
3845 "My preferred graphical merge tool is <command>kdiff3</command>, which I'll "
3846 "use to describe the features that are common to graphical file merging "
3847 "tools. You can see a screenshot of <command>kdiff3</command> in action in "
3848 "figure <xref endterm=\"fig.tour-merge.kdiff3.caption\" linkend=\"fig.tour-"
3849 "merge.kdiff3\"/>. The kind of merge it is performing is called a "
3850 "<emphasis>three-way merge</emphasis>, because there are three different "
3851 "versions of the file of interest to us. The tool thus splits the upper "
3852 "portion of the window into three panes:"
3853 msgstr ""
3855 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
3856 #: ../en/ch03-tour-merge.xml:226
3857 msgid ""
3858 "At the left is the <emphasis>base</emphasis> version of the file, i.e. the "
3859 "most recent version from which the two versions we're trying to merge are "
3860 "descended."
3861 msgstr ""
3863 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
3864 #: ../en/ch03-tour-merge.xml:231
3865 msgid ""
3866 "In the middle is <quote>our</quote> version of the file, with the contents "
3867 "that we modified."
3868 msgstr ""
3870 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
3871 #: ../en/ch03-tour-merge.xml:234
3872 msgid ""
3873 "On the right is <quote>their</quote> version of the file, the one that from "
3874 "the changeset that we're trying to merge with."
3875 msgstr ""
3877 #. type: Content of: <book><chapter><sect1><sect2><para>
3878 #: ../en/ch03-tour-merge.xml:238
3879 msgid ""
3880 "In the pane below these is the current <emphasis>result</emphasis> of the "
3881 "merge. Our task is to replace all of the red text, which indicates unresolved "
3882 "conflicts, with some sensible merger of the <quote>ours</quote> and "
3883 "<quote>theirs</quote> versions of the file."
3884 msgstr ""
3886 #. type: Content of: <book><chapter><sect1><sect2><para>
3887 #: ../en/ch03-tour-merge.xml:245
3888 msgid ""
3889 "All four of these panes are <emphasis>locked together</emphasis>; if we "
3890 "scroll vertically or horizontally in any of them, the others are updated to "
3891 "display the corresponding sections of their respective files."
3892 msgstr ""
3894 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
3895 #: ../en/ch03-tour-merge.xml:252
3896 msgid ""
3897 "<imageobject><imagedata width=\"100%\" fileref=\"images/kdiff3.png\"/> </"
3898 "imageobject>"
3899 msgstr ""
3901 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
3902 #: ../en/ch03-tour-merge.xml:255
3903 msgid "Using <command>kdiff3</command> to merge versions of a file"
3904 msgstr ""
3906 #. type: Content of: <book><chapter><sect1><sect2><para>
3907 #: ../en/ch03-tour-merge.xml:261
3908 msgid ""
3909 "For each conflicting portion of the file, we can choose to resolve the "
3910 "conflict using some combination of text from the base version, ours, or "
3911 "theirs. We can also manually edit the merged file at any time, in case we "
3912 "need to make further modifications."
3913 msgstr ""
3915 #. type: Content of: <book><chapter><sect1><sect2><para>
3916 #: ../en/ch03-tour-merge.xml:267
3917 msgid ""
3918 "There are <emphasis>many</emphasis> file merging tools available, too many to "
3919 "cover here. They vary in which platforms they are available for, and in "
3920 "their particular strengths and weaknesses. Most are tuned for merging files "
3921 "containing plain text, while a few are aimed at specialised file formats "
3922 "(generally XML)."
3923 msgstr ""
3925 #. type: Content of: <book><chapter><sect1><sect2><title>
3926 #: ../en/ch03-tour-merge.xml:276
3927 msgid "A worked example"
3928 msgstr "合并实例"
3930 #. type: Content of: <book><chapter><sect1><sect2><para>
3931 #: ../en/ch03-tour-merge.xml:278
3932 msgid ""
3933 "In this example, we will reproduce the file modification history of figure "
3934 "<xref endterm=\"fig.tour-merge.conflict.caption\" linkend=\"fig.tour-merge."
3935 "conflict\"/> above. Let's begin by creating a repository with a base version "
3936 "of our document."
3937 msgstr ""
3939 #. type: Content of: <book><chapter><sect1><sect2><para>
3940 #: ../en/ch03-tour-merge.xml:286
3941 msgid "We'll clone the repository and make a change to the file."
3942 msgstr ""
3944 #. type: Content of: <book><chapter><sect1><sect2><para>
3945 #: ../en/ch03-tour-merge.xml:291
3946 msgid ""
3947 "And another clone, to simulate someone else making a change to the file. "
3948 "(This hints at the idea that it's not all that unusual to merge with yourself "
3949 "when you isolate tasks in separate repositories, and indeed to find and "
3950 "resolve conflicts while doing so.)"
3951 msgstr ""
3953 #. type: Content of: <book><chapter><sect1><sect2><para>
3954 #: ../en/ch03-tour-merge.xml:299
3955 msgid ""
3956 "Having created two different versions of the file, we'll set up an "
3957 "environment suitable for running our merge."
3958 msgstr ""
3960 #. type: Content of: <book><chapter><sect1><sect2><para>
3961 #: ../en/ch03-tour-merge.xml:305
3962 msgid ""
3963 "In this example, I won't use Mercurial's normal <command>hgmerge</command> "
3964 "program to do the merge, because it would drop my nice automated example-"
3965 "running tool into a graphical user interface. Instead, I'll set "
3966 "<envar>HGMERGE</envar> to tell Mercurial to use the non-interactive "
3967 "<command>merge</command> command. This is bundled with many Unix-like "
3968 "systems. If you're following this example on your computer, don't bother "
3969 "setting <envar>HGMERGE</envar>."
3970 msgstr ""
3972 #. type: Content of: <book><chapter><sect1><sect2><para>
3973 #: ../en/ch03-tour-merge.xml:315
3974 msgid "<emphasis role=\"bold\">XXX FIX THIS EXAMPLE.</emphasis>"
3975 msgstr ""
3977 #. type: Content of: <book><chapter><sect1><sect2><para>
3978 #: ../en/ch03-tour-merge.xml:320
3979 msgid ""
3980 "Because <command>merge</command> can't resolve the conflicting changes, it "
3981 "leaves <emphasis>merge markers</emphasis> inside the file that has conflicts, "
3982 "indicating which lines have conflicts, and whether they came from our version "
3983 "of the file or theirs."
3984 msgstr ""
3986 #. type: Content of: <book><chapter><sect1><sect2><para>
3987 #: ../en/ch03-tour-merge.xml:326
3988 msgid ""
3989 "Mercurial can tell from the way <command>merge</command> exits that it wasn't "
3990 "able to merge successfully, so it tells us what commands we'll need to run if "
3991 "we want to redo the merging operation. This could be useful if, for example, "
3992 "we were running a graphical merge tool and quit because we were confused or "
3993 "realised we had made a mistake."
3994 msgstr ""
3996 #. type: Content of: <book><chapter><sect1><sect2><para>
3997 #: ../en/ch03-tour-merge.xml:333
3998 msgid ""
3999 "If automatic or manual merges fail, there's nothing to prevent us from "
4000 "<quote>fixing up</quote> the affected files ourselves, and committing the "
4001 "results of our merge:"
4002 msgstr ""
4004 #. type: Content of: <book><chapter><sect1><title>
4005 #: ../en/ch03-tour-merge.xml:342
4006 msgid "Simplifying the pull-merge-commit sequence"
4007 msgstr "简化拉-合并-提交程序"
4009 #. type: Content of: <book><chapter><sect1><para>
4010 #: ../en/ch03-tour-merge.xml:344
4011 msgid ""
4012 "The process of merging changes as outlined above is straightforward, but "
4013 "requires running three commands in sequence."
4014 msgstr ""
4016 #. type: Content of: <book><chapter><sect1><para>
4017 #: ../en/ch03-tour-merge.xml:350
4018 msgid ""
4019 "In the case of the final commit, you also need to enter a commit message, "
4020 "which is almost always going to be a piece of uninteresting "
4021 "<quote>boilerplate</quote> text."
4022 msgstr ""
4024 #. type: Content of: <book><chapter><sect1><para>
4025 #: ../en/ch03-tour-merge.xml:354
4026 msgid ""
4027 "It would be nice to reduce the number of steps needed, if this were "
4028 "possible. Indeed, Mercurial is distributed with an extension called <literal "
4029 "role=\"hg-ext\">fetch</literal> that does just this."
4030 msgstr ""
4032 #. type: Content of: <book><chapter><sect1><para>
4033 #: ../en/ch03-tour-merge.xml:359
4034 msgid ""
4035 "Mercurial provides a flexible extension mechanism that lets people extend its "
4036 "functionality, while keeping the core of Mercurial small and easy to deal "
4037 "with. Some extensions add new commands that you can use from the command "
4038 "line, while others work <quote>behind the scenes,</quote> for example adding "
4039 "capabilities to the server."
4040 msgstr ""
4042 #. type: Content of: <book><chapter><sect1><para>
4043 #: ../en/ch03-tour-merge.xml:366
4044 msgid ""
4045 "The <literal role=\"hg-ext\">fetch</literal> extension adds a new command "
4046 "called, not surprisingly, <command role=\"hg-cmd\">hg fetch</command>. This "
4047 "extension acts as a combination of <command role=\"hg-cmd\">hg pull</"
4048 "command>, <command role=\"hg-cmd\">hg update</command> and <command role=\"hg-"
4049 "cmd\">hg merge</command>. It begins by pulling changes from another "
4050 "repository into the current repository. If it finds that the changes added a "
4051 "new head to the repository, it begins a merge, then commits the result of the "
4052 "merge with an automatically-generated commit message. If no new heads were "
4053 "added, it updates the working directory to the new tip changeset."
4054 msgstr ""
4056 #. type: Content of: <book><chapter><sect1><para>
4057 #: ../en/ch03-tour-merge.xml:379
4058 msgid ""
4059 "Enabling the <literal role=\"hg-ext\">fetch</literal> extension is easy. "
4060 "Edit your <filename role=\"special\">.hgrc</filename>, and either go to the "
4061 "<literal role=\"rc-extensions\">extensions</literal> section or create an "
4062 "<literal role=\"rc-extensions\">extensions</literal> section. Then add a line "
4063 "that simply reads <quote><literal>fetch </literal></quote>."
4064 msgstr ""
4066 #. type: Content of: <book><chapter><sect1><para>
4067 #: ../en/ch03-tour-merge.xml:389
4068 msgid ""
4069 "(Normally, on the right-hand side of the <quote><literal>=</literal></quote> "
4070 "would appear the location of the extension, but since the <literal role=\"hg-"
4071 "ext\">fetch</literal> extension is in the standard distribution, Mercurial "
4072 "knows where to search for it.)"
4073 msgstr ""
4075 #. type: Content of: <book><chapter><title>
4076 #: ../en/ch04-concepts.xml:5
4077 msgid "Behind the scenes"
4078 msgstr "Mercurial 内幕"
4080 #. type: Content of: <book><chapter><para>
4081 #: ../en/ch04-concepts.xml:7
4082 msgid ""
4083 "Unlike many revision control systems, the concepts upon which Mercurial is "
4084 "built are simple enough that it's easy to understand how the software really "
4085 "works. Knowing this certainly isn't necessary, but I find it useful to have "
4086 "a <quote>mental model</quote> of what's going on."
4087 msgstr ""
4089 #. type: Content of: <book><chapter><para>
4090 #: ../en/ch04-concepts.xml:13
4091 msgid ""
4092 "This understanding gives me confidence that Mercurial has been carefully "
4093 "designed to be both <emphasis>safe</emphasis> and <emphasis>efficient</"
4094 "emphasis>. And just as importantly, if it's easy for me to retain a good "
4095 "idea of what the software is doing when I perform a revision control task, "
4096 "I'm less likely to be surprised by its behaviour."
4097 msgstr ""
4099 #. type: Content of: <book><chapter><para>
4100 #: ../en/ch04-concepts.xml:20
4101 msgid ""
4102 "In this chapter, we'll initially cover the core concepts behind Mercurial's "
4103 "design, then continue to discuss some of the interesting details of its "
4104 "implementation."
4105 msgstr ""
4107 #. type: Content of: <book><chapter><sect1><title>
4108 #: ../en/ch04-concepts.xml:25
4109 msgid "Mercurial's historical record"
4110 msgstr "Mercurial 的历史记录"
4112 #. type: Content of: <book><chapter><sect1><sect2><title>
4113 #: ../en/ch04-concepts.xml:28
4114 msgid "Tracking the history of a single file"
4115 msgstr "跟踪单一文件的历史"
4117 #. type: Content of: <book><chapter><sect1><sect2><para>
4118 #: ../en/ch04-concepts.xml:30
4119 msgid ""
4120 "When Mercurial tracks modifications to a file, it stores the history of that "
4121 "file in a metadata object called a <emphasis>filelog</emphasis>. Each entry "
4122 "in the filelog contains enough information to reconstruct one revision of the "
4123 "file that is being tracked. Filelogs are stored as files in the <filename "
4124 "role=\"special\" class=\"directory\">.hg/store/data</filename> directory. A "
4125 "filelog contains two kinds of information: revision data, and an index to "
4126 "help Mercurial to find a revision efficiently."
4127 msgstr ""
4129 #. type: Content of: <book><chapter><sect1><sect2><para>
4130 #: ../en/ch04-concepts.xml:41
4131 msgid ""
4132 "A file that is large, or has a lot of history, has its filelog stored in "
4133 "separate data (<quote><literal>.d</literal></quote> suffix) and index "
4134 "(<quote><literal>.i</literal></quote> suffix) files. For small files without "
4135 "much history, the revision data and index are combined in a single "
4136 "<quote><literal>.i</literal></quote> file. The correspondence between a file "
4137 "in the working directory and the filelog that tracks its history in the "
4138 "repository is illustrated in figure <xref endterm=\"fig.concepts.filelog."
4139 "caption\" linkend=\"fig.concepts.filelog\"/>."
4140 msgstr ""
4142 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
4143 #: ../en/ch04-concepts.xml:55
4144 msgid "<imageobject><imagedata fileref=\"images/filelog.png\"/></imageobject>"
4145 msgstr ""
4147 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
4148 #: ../en/ch04-concepts.xml:57
4149 msgid ""
4150 "Relationships between files in working directory and filelogs in repository"
4151 msgstr ""
4153 #. type: Content of: <book><chapter><sect1><sect2><title>
4154 #: ../en/ch04-concepts.xml:65
4155 msgid "Managing tracked files"
4156 msgstr "管理跟踪的文件"
4158 #. type: Content of: <book><chapter><sect1><sect2><para>
4159 #: ../en/ch04-concepts.xml:67
4160 msgid ""
4161 "Mercurial uses a structure called a <emphasis>manifest</emphasis> to collect "
4162 "together information about the files that it tracks. Each entry in the "
4163 "manifest contains information about the files present in a single changeset. "
4164 "An entry records which files are present in the changeset, the revision of "
4165 "each file, and a few other pieces of file metadata."
4166 msgstr ""
4168 #. type: Content of: <book><chapter><sect1><sect2><title>
4169 #: ../en/ch04-concepts.xml:77
4170 msgid "Recording changeset information"
4171 msgstr "记录修改集信息"
4173 #. type: Content of: <book><chapter><sect1><sect2><para>
4174 #: ../en/ch04-concepts.xml:79
4175 msgid ""
4176 "The <emphasis>changelog</emphasis> contains information about each "
4177 "changeset. Each revision records who committed a change, the changeset "
4178 "comment, other pieces of changeset-related information, and the revision of "
4179 "the manifest to use."
4180 msgstr ""
4182 #. type: Content of: <book><chapter><sect1><sect2><title>
4183 #: ../en/ch04-concepts.xml:87
4184 msgid "Relationships between revisions"
4185 msgstr "版本之间的关系"
4187 #. type: Content of: <book><chapter><sect1><sect2><para>
4188 #: ../en/ch04-concepts.xml:89
4189 msgid ""
4190 "Within a changelog, a manifest, or a filelog, each revision stores a pointer "
4191 "to its immediate parent (or to its two parents, if it's a merge revision). "
4192 "As I mentioned above, there are also relationships between revisions "
4193 "<emphasis>across</emphasis> these structures, and they are hierarchical in "
4194 "nature."
4195 msgstr ""
4197 #. type: Content of: <book><chapter><sect1><sect2><para>
4198 #: ../en/ch04-concepts.xml:96
4199 msgid ""
4200 "For every changeset in a repository, there is exactly one revision stored in "
4201 "the changelog. Each revision of the changelog contains a pointer to a single "
4202 "revision of the manifest. A revision of the manifest stores a pointer to a "
4203 "single revision of each filelog tracked when that changeset was created. "
4204 "These relationships are illustrated in figure <xref endterm=\"fig.concepts."
4205 "metadata.caption\" linkend=\"fig.concepts.metadata\"/>."
4206 msgstr ""
4208 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
4209 #: ../en/ch04-concepts.xml:107
4210 msgid "<imageobject><imagedata fileref=\"images/metadata.png\"/></imageobject>"
4211 msgstr ""
4213 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
4214 #: ../en/ch04-concepts.xml:109
4215 msgid "Metadata relationships"
4216 msgstr ""
4218 #. type: Content of: <book><chapter><sect1><sect2><para>
4219 #: ../en/ch04-concepts.xml:114
4220 msgid ""
4221 "As the illustration shows, there is <emphasis>not</emphasis> a <quote>one to "
4222 "one</quote> relationship between revisions in the changelog, manifest, or "
4223 "filelog. If the manifest hasn't changed between two changesets, the changelog "
4224 "entries for those changesets will point to the same revision of the "
4225 "manifest. If a file that Mercurial tracks hasn't changed between two "
4226 "changesets, the entry for that file in the two revisions of the manifest will "
4227 "point to the same revision of its filelog."
4228 msgstr ""
4230 #. type: Content of: <book><chapter><sect1><title>
4231 #: ../en/ch04-concepts.xml:127
4232 msgid "Safe, efficient storage"
4233 msgstr "安全，高效的存储"
4235 #. type: Content of: <book><chapter><sect1><para>
4236 #: ../en/ch04-concepts.xml:129
4237 msgid ""
4238 "The underpinnings of changelogs, manifests, and filelogs are provided by a "
4239 "single structure called the <emphasis>revlog</emphasis>."
4240 msgstr ""
4242 #. type: Content of: <book><chapter><sect1><sect2><title>
4243 #: ../en/ch04-concepts.xml:134
4244 msgid "Efficient storage"
4245 msgstr "高效存储"
4247 #. type: Content of: <book><chapter><sect1><sect2><para>
4248 #: ../en/ch04-concepts.xml:136
4249 msgid ""
4250 "The revlog provides efficient storage of revisions using a <emphasis>delta</"
4251 "emphasis> mechanism. Instead of storing a complete copy of a file for each "
4252 "revision, it stores the changes needed to transform an older revision into "
4253 "the new revision. For many kinds of file data, these deltas are typically a "
4254 "fraction of a percent of the size of a full copy of a file."
4255 msgstr ""
4257 #. type: Content of: <book><chapter><sect1><sect2><para>
4258 #: ../en/ch04-concepts.xml:144
4259 msgid ""
4260 "Some obsolete revision control systems can only work with deltas of text "
4261 "files. They must either store binary files as complete snapshots or encoded "
4262 "into a text representation, both of which are wasteful approaches. Mercurial "
4263 "can efficiently handle deltas of files with arbitrary binary contents; it "
4264 "doesn't need to treat text as special."
4265 msgstr ""
4267 #. type: Content of: <book><chapter><sect1><sect2><title>
4268 #: ../en/ch04-concepts.xml:153
4269 msgid "Safe operation"
4270 msgstr "安全操作"
4272 #. type: Content of: <book><chapter><sect1><sect2><para>
4273 #: ../en/ch04-concepts.xml:155
4274 msgid ""
4275 "Mercurial only ever <emphasis>appends</emphasis> data to the end of a revlog "
4276 "file. It never modifies a section of a file after it has written it. This is "
4277 "both more robust and efficient than schemes that need to modify or rewrite "
4278 "data."
4279 msgstr ""
4281 #. type: Content of: <book><chapter><sect1><sect2><para>
4282 #: ../en/ch04-concepts.xml:161
4283 msgid ""
4284 "In addition, Mercurial treats every write as part of a <emphasis>transaction</"
4285 "emphasis> that can span a number of files. A transaction is "
4286 "<emphasis>atomic</emphasis>: either the entire transaction succeeds and its "
4287 "effects are all visible to readers in one go, or the whole thing is undone. "
4288 "This guarantee of atomicity means that if you're running two copies of "
4289 "Mercurial, where one is reading data and one is writing it, the reader will "
4290 "never see a partially written result that might confuse it."
4291 msgstr ""
4293 #. type: Content of: <book><chapter><sect1><sect2><para>
4294 #: ../en/ch04-concepts.xml:171
4295 msgid ""
4296 "The fact that Mercurial only appends to files makes it easier to provide this "
4297 "transactional guarantee. The easier it is to do stuff like this, the more "
4298 "confident you should be that it's done correctly."
4299 msgstr ""
4301 #. type: Content of: <book><chapter><sect1><sect2><title>
4302 #: ../en/ch04-concepts.xml:178
4303 msgid "Fast retrieval"
4304 msgstr "快速检索"
4306 #. type: Content of: <book><chapter><sect1><sect2><para>
4307 #: ../en/ch04-concepts.xml:180
4308 msgid ""
4309 "Mercurial cleverly avoids a pitfall common to all earlier revision control "
4310 "systems: the problem of <emphasis>inefficient retrieval</emphasis>. Most "
4311 "revision control systems store the contents of a revision as an incremental "
4312 "series of modifications against a <quote>snapshot</quote>. To reconstruct a "
4313 "specific revision, you must first read the snapshot, and then every one of "
4314 "the revisions between the snapshot and your target revision. The more "
4315 "history that a file accumulates, the more revisions you must read, hence the "
4316 "longer it takes to reconstruct a particular revision."
4317 msgstr ""
4319 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
4320 #: ../en/ch04-concepts.xml:193
4321 msgid "<imageobject><imagedata fileref=\"images/snapshot.png\"/></imageobject>"
4322 msgstr ""
4324 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
4325 #: ../en/ch04-concepts.xml:195
4326 msgid "Snapshot of a revlog, with incremental deltas"
4327 msgstr ""
4329 #. type: Content of: <book><chapter><sect1><sect2><para>
4330 #: ../en/ch04-concepts.xml:200
4331 msgid ""
4332 "The innovation that Mercurial applies to this problem is simple but "
4333 "effective. Once the cumulative amount of delta information stored since the "
4334 "last snapshot exceeds a fixed threshold, it stores a new snapshot "
4335 "(compressed, of course), instead of another delta. This makes it possible to "
4336 "reconstruct <emphasis>any</emphasis> revision of a file quickly. This "
4337 "approach works so well that it has since been copied by several other "
4338 "revision control systems."
4339 msgstr ""
4341 #. type: Content of: <book><chapter><sect1><sect2><para>
4342 #: ../en/ch04-concepts.xml:209
4343 msgid ""
4344 "Figure <xref endterm=\"fig.concepts.snapshot.caption\" linkend=\"fig.concepts."
4345 "snapshot\"/> illustrates the idea. In an entry in a revlog's index file, "
4346 "Mercurial stores the range of entries from the data file that it must read to "
4347 "reconstruct a particular revision."
4348 msgstr ""
4350 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
4351 #: ../en/ch04-concepts.xml:216
4352 msgid "Aside: the influence of video compression"
4353 msgstr ""
4355 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
4356 #: ../en/ch04-concepts.xml:218
4357 msgid ""
4358 "If you're familiar with video compression or have ever watched a TV feed "
4359 "through a digital cable or satellite service, you may know that most video "
4360 "compression schemes store each frame of video as a delta against its "
4361 "predecessor frame. In addition, these schemes use <quote>lossy</quote> "
4362 "compression techniques to increase the compression ratio, so visual errors "
4363 "accumulate over the course of a number of inter-frame deltas."
4364 msgstr ""
4366 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
4367 #: ../en/ch04-concepts.xml:227
4368 msgid ""
4369 "Because it's possible for a video stream to <quote>drop out</quote> "
4370 "occasionally due to signal glitches, and to limit the accumulation of "
4371 "artefacts introduced by the lossy compression process, video encoders "
4372 "periodically insert a complete frame (called a <quote>key frame</quote>) into "
4373 "the video stream; the next delta is generated against that frame. This means "
4374 "that if the video signal gets interrupted, it will resume once the next key "
4375 "frame is received. Also, the accumulation of encoding errors restarts anew "
4376 "with each key frame."
4377 msgstr ""
4379 #. type: Content of: <book><chapter><sect1><sect2><title>
4380 #: ../en/ch04-concepts.xml:241
4381 msgid "Identification and strong integrity"
4382 msgstr "鉴别和强完整性"
4384 #. type: Content of: <book><chapter><sect1><sect2><para>
4385 #: ../en/ch04-concepts.xml:243
4386 msgid ""
4387 "Along with delta or snapshot information, a revlog entry contains a "
4388 "cryptographic hash of the data that it represents. This makes it difficult "
4389 "to forge the contents of a revision, and easy to detect accidental corruption."
4390 msgstr ""
4392 #. type: Content of: <book><chapter><sect1><sect2><para>
4393 #: ../en/ch04-concepts.xml:248
4394 msgid ""
4395 "Hashes provide more than a mere check against corruption; they are used as "
4396 "the identifiers for revisions. The changeset identification hashes that you "
4397 "see as an end user are from revisions of the changelog. Although filelogs "
4398 "and the manifest also use hashes, Mercurial only uses these behind the scenes."
4399 msgstr ""
4401 #. type: Content of: <book><chapter><sect1><sect2><para>
4402 #: ../en/ch04-concepts.xml:255
4403 msgid ""
4404 "Mercurial verifies that hashes are correct when it retrieves file revisions "
4405 "and when it pulls changes from another repository. If it encounters an "
4406 "integrity problem, it will complain and stop whatever it's doing."
4407 msgstr ""
4409 #. type: Content of: <book><chapter><sect1><sect2><para>
4410 #: ../en/ch04-concepts.xml:260
4411 msgid ""
4412 "In addition to the effect it has on retrieval efficiency, Mercurial's use of "
4413 "periodic snapshots makes it more robust against partial data corruption. If "
4414 "a revlog becomes partly corrupted due to a hardware error or system bug, it's "
4415 "often possible to reconstruct some or most revisions from the uncorrupted "
4416 "sections of the revlog, both before and after the corrupted section. This "
4417 "would not be possible with a delta-only storage model."
4418 msgstr ""
4420 #. type: Content of: <book><chapter><sect1><title>
4421 #: ../en/ch04-concepts.xml:272
4422 msgid "Revision history, branching, and merging"
4423 msgstr "修订历史，分支与合并"
4425 #. type: Content of: <book><chapter><sect1><para>
4426 #: ../en/ch04-concepts.xml:274
4427 msgid ""
4428 "Every entry in a Mercurial revlog knows the identity of its immediate "
4429 "ancestor revision, usually referred to as its <emphasis>parent</emphasis>. "
4430 "In fact, a revision contains room for not one parent, but two. Mercurial "
4431 "uses a special hash, called the <quote>null ID</quote>, to represent the idea "
4432 "<quote>there is no parent here</quote>. This hash is simply a string of "
4433 "zeroes."
4434 msgstr ""
4436 #. type: Content of: <book><chapter><sect1><para>
4437 #: ../en/ch04-concepts.xml:282
4438 msgid ""
4439 "In figure <xref endterm=\"fig.concepts.revlog.caption\" linkend=\"fig."
4440 "concepts.revlog\"/>, you can see an example of the conceptual structure of a "
4441 "revlog. Filelogs, manifests, and changelogs all have this same structure; "
4442 "they differ only in the kind of data stored in each delta or snapshot."
4443 msgstr ""
4445 #. type: Content of: <book><chapter><sect1><para>
4446 #: ../en/ch04-concepts.xml:289
4447 msgid ""
4448 "The first revision in a revlog (at the bottom of the image) has the null ID "
4449 "in both of its parent slots. For a <quote>normal</quote> revision, its first "
4450 "parent slot contains the ID of its parent revision, and its second contains "
4451 "the null ID, indicating that the revision has only one real parent. Any two "
4452 "revisions that have the same parent ID are branches. A revision that "
4453 "represents a merge between branches has two normal revision IDs in its parent "
4454 "slots."
4455 msgstr ""
4457 #. type: Content of: <book><chapter><sect1><informalfigure><mediaobject>
4458 #: ../en/ch04-concepts.xml:300
4459 msgid "<imageobject><imagedata fileref=\"images/revlog.png\"/></imageobject>"
4460 msgstr ""
4462 #. type: Content of: <book><chapter><sect1><informalfigure><mediaobject><caption><para>
4463 #: ../en/ch04-concepts.xml:302
4464 msgid "Revision in revlog"
4465 msgstr ""
4467 #. type: Content of: <book><chapter><sect1><title>
4468 #: ../en/ch04-concepts.xml:309
4469 msgid "The working directory"
4470 msgstr "工作目录"
4472 #. type: Content of: <book><chapter><sect1><para>
4473 #: ../en/ch04-concepts.xml:311
4474 msgid ""
4475 "In the working directory, Mercurial stores a snapshot of the files from the "
4476 "repository as of a particular changeset."
4477 msgstr ""
4479 #. type: Content of: <book><chapter><sect1><para>
4480 #: ../en/ch04-concepts.xml:314
4481 msgid ""
4482 "The working directory <quote>knows</quote> which changeset it contains. When "
4483 "you update the working directory to contain a particular changeset, Mercurial "
4484 "looks up the appropriate revision of the manifest to find out which files it "
4485 "was tracking at the time that changeset was committed, and which revision of "
4486 "each file was then current. It then recreates a copy of each of those files, "
4487 "with the same contents it had when the changeset was committed."
4488 msgstr ""
4490 #. type: Content of: <book><chapter><sect1><para>
4491 #: ../en/ch04-concepts.xml:323
4492 msgid ""
4493 "The <emphasis>dirstate</emphasis> contains Mercurial's knowledge of the "
4494 "working directory. This details which changeset the working directory is "
4495 "updated to, and all of the files that Mercurial is tracking in the working "
4496 "directory."
4497 msgstr ""
4499 #. type: Content of: <book><chapter><sect1><para>
4500 #: ../en/ch04-concepts.xml:329
4501 msgid ""
4502 "Just as a revision of a revlog has room for two parents, so that it can "
4503 "represent either a normal revision (with one parent) or a merge of two "
4504 "earlier revisions, the dirstate has slots for two parents. When you use the "
4505 "<command role=\"hg-cmd\">hg update</command> command, the changeset that you "
4506 "update to is stored in the <quote>first parent</quote> slot, and the null ID "
4507 "in the second. When you <command role=\"hg-cmd\">hg merge</command> with "
4508 "another changeset, the first parent remains unchanged, and the second parent "
4509 "is filled in with the changeset you're merging with. The <command role=\"hg-"
4510 "cmd\">hg parents</command> command tells you what the parents of the dirstate "
4511 "are."
4512 msgstr ""
4514 #. type: Content of: <book><chapter><sect1><sect2><title>
4515 #: ../en/ch04-concepts.xml:343
4516 msgid "What happens when you commit"
4517 msgstr "当你提交时发生的事情"
4519 #. type: Content of: <book><chapter><sect1><sect2><para>
4520 #: ../en/ch04-concepts.xml:345
4521 msgid ""
4522 "The dirstate stores parent information for more than just book-keeping "
4523 "purposes. Mercurial uses the parents of the dirstate as <emphasis>the "
4524 "parents of a new changeset</emphasis> when you perform a commit."
4525 msgstr ""
4527 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
4528 #: ../en/ch04-concepts.xml:352
4529 msgid "<imageobject><imagedata fileref=\"images/wdir.png\"/></imageobject>"
4530 msgstr ""
4532 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
4533 #: ../en/ch04-concepts.xml:354
4534 msgid "The working directory can have two parents"
4535 msgstr ""
4537 #. type: Content of: <book><chapter><sect1><sect2><para>
4538 #: ../en/ch04-concepts.xml:359
4539 msgid ""
4540 "Figure <xref endterm=\"fig.concepts.wdir.caption\" linkend=\"fig.concepts.wdir"
4541 "\"/> shows the normal state of the working directory, where it has a single "
4542 "changeset as parent. That changeset is the <emphasis>tip</emphasis>, the "
4543 "newest changeset in the repository that has no children."
4544 msgstr ""
4546 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
4547 #: ../en/ch04-concepts.xml:368
4548 msgid ""
4549 "<imageobject><imagedata fileref=\"images/wdir-after-commit.png\"/> </"
4550 "imageobject>"
4551 msgstr ""
4553 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
4554 #: ../en/ch04-concepts.xml:371
4555 msgid "The working directory gains new parents after a commit"
4556 msgstr ""
4558 #. type: Content of: <book><chapter><sect1><sect2><para>
4559 #: ../en/ch04-concepts.xml:376
4560 msgid ""
4561 "It's useful to think of the working directory as <quote>the changeset I'm "
4562 "about to commit</quote>. Any files that you tell Mercurial that you've "
4563 "added, removed, renamed, or copied will be reflected in that changeset, as "
4564 "will modifications to any files that Mercurial is already tracking; the new "
4565 "changeset will have the parents of the working directory as its parents."
4566 msgstr ""
4568 #. type: Content of: <book><chapter><sect1><sect2><para>
4569 #: ../en/ch04-concepts.xml:384
4570 msgid ""
4571 "After a commit, Mercurial will update the parents of the working directory, "
4572 "so that the first parent is the ID of the new changeset, and the second is "
4573 "the null ID. This is shown in figure <xref endterm=\"fig.concepts.wdir-after-"
4574 "commit.caption\" linkend=\"fig.concepts.wdir-after-commit\"/>. Mercurial "
4575 "doesn't touch any of the files in the working directory when you commit; it "
4576 "just modifies the dirstate to note its new parents."
4577 msgstr ""
4579 #. type: Content of: <book><chapter><sect1><sect2><title>
4580 #: ../en/ch04-concepts.xml:396
4581 msgid "Creating a new head"
4582 msgstr "创建新顶点"
4584 #. type: Content of: <book><chapter><sect1><sect2><para>
4585 #: ../en/ch04-concepts.xml:398
4586 msgid ""
4587 "It's perfectly normal to update the working directory to a changeset other "
4588 "than the current tip. For example, you might want to know what your project "
4589 "looked like last Tuesday, or you could be looking through changesets to see "
4590 "which one introduced a bug. In cases like this, the natural thing to do is "
4591 "update the working directory to the changeset you're interested in, and then "
4592 "examine the files in the working directory directly to see their contents as "
4593 "they were when you committed that changeset. The effect of this is shown in "
4594 "figure <xref endterm=\"fig.concepts.wdir-pre-branch.caption\" linkend=\"fig."
4595 "concepts.wdir-pre-branch\"/>."
4596 msgstr ""
4598 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
4599 #: ../en/ch04-concepts.xml:412
4600 msgid ""
4601 "<imageobject><imagedata fileref=\"images/wdir-pre-branch.png\"/> </"
4602 "imageobject>"
4603 msgstr ""
4605 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
4606 #: ../en/ch04-concepts.xml:415
4607 msgid "The working directory, updated to an older changeset"
4608 msgstr ""
4610 #. type: Content of: <book><chapter><sect1><sect2><para>
4611 #: ../en/ch04-concepts.xml:420
4612 msgid ""
4613 "Having updated the working directory to an older changeset, what happens if "
4614 "you make some changes, and then commit? Mercurial behaves in the same way as "
4615 "I outlined above. The parents of the working directory become the parents of "
4616 "the new changeset. This new changeset has no children, so it becomes the new "
4617 "tip. And the repository now contains two changesets that have no children; "
4618 "we call these <emphasis>heads</emphasis>. You can see the structure that "
4619 "this creates in figure <xref endterm=\"fig.concepts.wdir-branch.caption\" "
4620 "linkend=\"fig.concepts.wdir-branch\"/>."
4621 msgstr ""
4623 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
4624 #: ../en/ch04-concepts.xml:434
4625 msgid ""
4626 "<imageobject><imagedata fileref=\"images/wdir-branch.png\"/> </imageobject>"
4627 msgstr ""
4629 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
4630 #: ../en/ch04-concepts.xml:437
4631 msgid "After a commit made while synced to an older changeset"
4632 msgstr ""
4634 #. type: Content of: <book><chapter><sect1><sect2><note><para>
4635 #: ../en/ch04-concepts.xml:443
4636 msgid ""
4637 "If you're new to Mercurial, you should keep in mind a common <quote>error</"
4638 "quote>, which is to use the <command role=\"hg-cmd\">hg pull</command> "
4639 "command without any options. By default, the <command role=\"hg-cmd\">hg "
4640 "pull</command> command <emphasis>does not</emphasis> update the working "
4641 "directory, so you'll bring new changesets into your repository, but the "
4642 "working directory will stay synced at the same changeset as before the pull. "
4643 "If you make some changes and commit afterwards, you'll thus create a new "
4644 "head, because your working directory isn't synced to whatever the current tip "
4645 "is."
4646 msgstr ""
4648 #. type: Content of: <book><chapter><sect1><sect2><note><para>
4649 #: ../en/ch04-concepts.xml:455
4650 msgid ""
4651 "I put the word <quote>error</quote> in quotes because all that you need to do "
4652 "to rectify this situation is <command role=\"hg-cmd\">hg merge</command>, "
4653 "then <command role=\"hg-cmd\">hg commit</command>. In other words, this "
4654 "almost never has negative consequences; it just surprises people. I'll "
4655 "discuss other ways to avoid this behaviour, and why Mercurial behaves in this "
4656 "initially surprising way, later on."
4657 msgstr ""
4659 #. type: Content of: <book><chapter><sect1><sect2><title>
4660 #: ../en/ch04-concepts.xml:467
4661 msgid "Merging heads"
4662 msgstr "合并顶点"
4664 #. type: Content of: <book><chapter><sect1><sect2><para>
4665 #: ../en/ch04-concepts.xml:469
4666 msgid ""
4667 "When you run the <command role=\"hg-cmd\">hg merge</command> command, "
4668 "Mercurial leaves the first parent of the working directory unchanged, and "
4669 "sets the second parent to the changeset you're merging with, as shown in "
4670 "figure <xref endterm=\"fig.concepts.wdir-merge.caption\" linkend=\"fig."
4671 "concepts.wdir-merge\"/>."
4672 msgstr ""
4674 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
4675 #: ../en/ch04-concepts.xml:478
4676 msgid ""
4677 "<imageobject><imagedata fileref=\"images/wdir-merge.png\"/> </imageobject>"
4678 msgstr ""
4680 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
4681 #: ../en/ch04-concepts.xml:481
4682 msgid "Merging two heads"
4683 msgstr ""
4685 #. type: Content of: <book><chapter><sect1><sect2><para>
4686 #: ../en/ch04-concepts.xml:486
4687 msgid ""
4688 "Mercurial also has to modify the working directory, to merge the files "
4689 "managed in the two changesets. Simplified a little, the merging process goes "
4690 "like this, for every file in the manifests of both changesets."
4691 msgstr ""
4693 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
4694 #: ../en/ch04-concepts.xml:491
4695 msgid "If neither changeset has modified a file, do nothing with that file."
4696 msgstr ""
4698 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
4699 #: ../en/ch04-concepts.xml:494
4700 msgid ""
4701 "If one changeset has modified a file, and the other hasn't, create the "
4702 "modified copy of the file in the working directory."
4703 msgstr ""
4705 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
4706 #: ../en/ch04-concepts.xml:498
4707 msgid ""
4708 "If one changeset has removed a file, and the other hasn't (or has also "
4709 "deleted it), delete the file from the working directory."
4710 msgstr ""
4712 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
4713 #: ../en/ch04-concepts.xml:502
4714 msgid ""
4715 "If one changeset has removed a file, but the other has modified the file, ask "
4716 "the user what to do: keep the modified file, or remove it?"
4717 msgstr ""
4719 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
4720 #: ../en/ch04-concepts.xml:506
4721 msgid ""
4722 "If both changesets have modified a file, invoke an external merge program to "
4723 "choose the new contents for the merged file. This may require input from the "
4724 "user."
4725 msgstr ""
4727 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
4728 #: ../en/ch04-concepts.xml:511
4729 msgid ""
4730 "If one changeset has modified a file, and the other has renamed or copied the "
4731 "file, make sure that the changes follow the new name of the file."
4732 msgstr ""
4734 #. type: Content of: <book><chapter><sect1><sect2><para>
4735 #: ../en/ch04-concepts.xml:515
4736 msgid ""
4737 "There are more details&emdash;merging has plenty of corner cases&emdash;but "
4738 "these are the most common choices that are involved in a merge. As you can "
4739 "see, most cases are completely automatic, and indeed most merges finish "
4740 "automatically, without requiring your input to resolve any conflicts."
4741 msgstr ""
4743 #. type: Content of: <book><chapter><sect1><sect2><para>
4744 #: ../en/ch04-concepts.xml:522
4745 msgid ""
4746 "When you're thinking about what happens when you commit after a merge, once "
4747 "again the working directory is <quote>the changeset I'm about to commit</"
4748 "quote>. After the <command role=\"hg-cmd\">hg merge</command> command "
4749 "completes, the working directory has two parents; these will become the "
4750 "parents of the new changeset."
4751 msgstr ""
4753 #. type: Content of: <book><chapter><sect1><sect2><para>
4754 #: ../en/ch04-concepts.xml:529
4755 msgid ""
4756 "Mercurial lets you perform multiple merges, but you must commit the results "
4757 "of each individual merge as you go. This is necessary because Mercurial only "
4758 "tracks two parents for both revisions and the working directory. While it "
4759 "would be technically possible to merge multiple changesets at once, the "
4760 "prospect of user confusion and making a terrible mess of a merge immediately "
4761 "becomes overwhelming."
4762 msgstr ""
4764 #. type: Content of: <book><chapter><sect1><title>
4765 #: ../en/ch04-concepts.xml:540
4766 msgid "Other interesting design features"
4767 msgstr "其它有趣的设计特性"
4769 #. type: Content of: <book><chapter><sect1><para>
4770 #: ../en/ch04-concepts.xml:542
4771 msgid ""
4772 "In the sections above, I've tried to highlight some of the most important "
4773 "aspects of Mercurial's design, to illustrate that it pays careful attention "
4774 "to reliability and performance. However, the attention to detail doesn't "
4775 "stop there. There are a number of other aspects of Mercurial's construction "
4776 "that I personally find interesting. I'll detail a few of them here, separate "
4777 "from the <quote>big ticket</quote> items above, so that if you're interested, "
4778 "you can gain a better idea of the amount of thinking that goes into a well-"
4779 "designed system."
4780 msgstr ""
4782 #. type: Content of: <book><chapter><sect1><sect2><title>
4783 #: ../en/ch04-concepts.xml:553
4784 msgid "Clever compression"
4785 msgstr "智能压缩"
4787 #. type: Content of: <book><chapter><sect1><sect2><para>
4788 #: ../en/ch04-concepts.xml:555
4789 msgid ""
4790 "When appropriate, Mercurial will store both snapshots and deltas in "
4791 "compressed form. It does this by always <emphasis>trying to</emphasis> "
4792 "compress a snapshot or delta, but only storing the compressed version if it's "
4793 "smaller than the uncompressed version."
4794 msgstr ""
4796 #. type: Content of: <book><chapter><sect1><sect2><para>
4797 #: ../en/ch04-concepts.xml:561
4798 msgid ""
4799 "This means that Mercurial does <quote>the right thing</quote> when storing a "
4800 "file whose native form is compressed, such as a <literal>zip</literal> "
4801 "archive or a JPEG image. When these types of files are compressed a second "
4802 "time, the resulting file is usually bigger than the once-compressed form, and "
4803 "so Mercurial will store the plain <literal>zip</literal> or JPEG."
4804 msgstr ""
4806 #. type: Content of: <book><chapter><sect1><sect2><para>
4807 #: ../en/ch04-concepts.xml:569
4808 msgid ""
4809 "Deltas between revisions of a compressed file are usually larger than "
4810 "snapshots of the file, and Mercurial again does <quote>the right thing</"
4811 "quote> in these cases. It finds that such a delta exceeds the threshold at "
4812 "which it should store a complete snapshot of the file, so it stores the "
4813 "snapshot, again saving space compared to a naive delta-only approach."
4814 msgstr ""
4816 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
4817 #: ../en/ch04-concepts.xml:578
4818 msgid "Network recompression"
4819 msgstr "网络重新压缩"
4821 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
4822 #: ../en/ch04-concepts.xml:580
4823 msgid ""
4824 "When storing revisions on disk, Mercurial uses the <quote>deflate</quote> "
4825 "compression algorithm (the same one used by the popular <literal>zip</"
4826 "literal> archive format), which balances good speed with a respectable "
4827 "compression ratio. However, when transmitting revision data over a network "
4828 "connection, Mercurial uncompresses the compressed revision data."
4829 msgstr ""
4831 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
4832 #: ../en/ch04-concepts.xml:588
4833 msgid ""
4834 "If the connection is over HTTP, Mercurial recompresses the entire stream of "
4835 "data using a compression algorithm that gives a better compression ratio (the "
4836 "Burrows-Wheeler algorithm from the widely used <literal>bzip2</literal> "
4837 "compression package). This combination of algorithm and compression of the "
4838 "entire stream (instead of a revision at a time) substantially reduces the "
4839 "number of bytes to be transferred, yielding better network performance over "
4840 "almost all kinds of network."
4841 msgstr ""
4843 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
4844 #: ../en/ch04-concepts.xml:598
4845 msgid ""
4846 "(If the connection is over <command>ssh</command>, Mercurial "
4847 "<emphasis>doesn't</emphasis> recompress the stream, because <command>ssh</"
4848 "command> can already do this itself.)"
4849 msgstr ""
4851 #. type: Content of: <book><chapter><sect1><sect2><title>
4852 #: ../en/ch04-concepts.xml:606
4853 msgid "Read/write ordering and atomicity"
4854 msgstr "读写顺序与原子性"
4856 #. type: Content of: <book><chapter><sect1><sect2><para>
4857 #: ../en/ch04-concepts.xml:608
4858 msgid ""
4859 "Appending to files isn't the whole story when it comes to guaranteeing that a "
4860 "reader won't see a partial write. If you recall figure <xref endterm=\"fig."
4861 "concepts.metadata.caption\" linkend=\"fig.concepts.metadata\"/>, revisions in "
4862 "the changelog point to revisions in the manifest, and revisions in the "
4863 "manifest point to revisions in filelogs. This hierarchy is deliberate."
4864 msgstr ""
4866 #. type: Content of: <book><chapter><sect1><sect2><para>
4867 #: ../en/ch04-concepts.xml:616
4868 msgid ""
4869 "A writer starts a transaction by writing filelog and manifest data, and "
4870 "doesn't write any changelog data until those are finished. A reader starts "
4871 "by reading changelog data, then manifest data, followed by filelog data."
4872 msgstr ""
4874 #. type: Content of: <book><chapter><sect1><sect2><para>
4875 #: ../en/ch04-concepts.xml:621
4876 msgid ""
4877 "Since the writer has always finished writing filelog and manifest data before "
4878 "it writes to the changelog, a reader will never read a pointer to a partially "
4879 "written manifest revision from the changelog, and it will never read a "
4880 "pointer to a partially written filelog revision from the manifest."
4881 msgstr ""
4883 #. type: Content of: <book><chapter><sect1><sect2><title>
4884 #: ../en/ch04-concepts.xml:629
4885 msgid "Concurrent access"
4886 msgstr "并发访问"
4888 #. type: Content of: <book><chapter><sect1><sect2><para>
4889 #: ../en/ch04-concepts.xml:631
4890 msgid ""
4891 "The read/write ordering and atomicity guarantees mean that Mercurial never "
4892 "needs to <emphasis>lock</emphasis> a repository when it's reading data, even "
4893 "if the repository is being written to while the read is occurring. This has a "
4894 "big effect on scalability; you can have an arbitrary number of Mercurial "
4895 "processes safely reading data from a repository safely all at once, no matter "
4896 "whether it's being written to or not."
4897 msgstr ""
4899 #. type: Content of: <book><chapter><sect1><sect2><para>
4900 #: ../en/ch04-concepts.xml:640
4901 msgid ""
4902 "The lockless nature of reading means that if you're sharing a repository on a "
4903 "multi-user system, you don't need to grant other local users permission to "
4904 "<emphasis>write</emphasis> to your repository in order for them to be able to "
4905 "clone it or pull changes from it; they only need <emphasis>read</emphasis> "
4906 "permission. (This is <emphasis>not</emphasis> a common feature among "
4907 "revision control systems, so don't take it for granted! Most require readers "
4908 "to be able to lock a repository to access it safely, and this requires write "
4909 "permission on at least one directory, which of course makes for all kinds of "
4910 "nasty and annoying security and administrative problems.)"
4911 msgstr ""
4913 #. type: Content of: <book><chapter><sect1><sect2><para>
4914 #: ../en/ch04-concepts.xml:653
4915 msgid ""
4916 "Mercurial uses locks to ensure that only one process can write to a "
4917 "repository at a time (the locking mechanism is safe even over filesystems "
4918 "that are notoriously hostile to locking, such as NFS). If a repository is "
4919 "locked, a writer will wait for a while to retry if the repository becomes "
4920 "unlocked, but if the repository remains locked for too long, the process "
4921 "attempting to write will time out after a while. This means that your daily "
4922 "automated scripts won't get stuck forever and pile up if a system crashes "
4923 "unnoticed, for example. (Yes, the timeout is configurable, from zero to "
4924 "infinity.)"
4925 msgstr ""
4927 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
4928 #: ../en/ch04-concepts.xml:665
4929 msgid "Safe dirstate access"
4930 msgstr "安全的目录状态访问"
4932 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
4933 #: ../en/ch04-concepts.xml:667
4934 msgid ""
4935 "As with revision data, Mercurial doesn't take a lock to read the dirstate "
4936 "file; it does acquire a lock to write it. To avoid the possibility of "
4937 "reading a partially written copy of the dirstate file, Mercurial writes to a "
4938 "file with a unique name in the same directory as the dirstate file, then "
4939 "renames the temporary file atomically to <filename>dirstate</filename>. The "
4940 "file named <filename>dirstate</filename> is thus guaranteed to be complete, "
4941 "not partially written."
4942 msgstr ""
4944 #. type: Content of: <book><chapter><sect1><sect2><title>
4945 #: ../en/ch04-concepts.xml:680
4946 msgid "Avoiding seeks"
4947 msgstr "避免查找"
4949 #. type: Content of: <book><chapter><sect1><sect2><para>
4950 #: ../en/ch04-concepts.xml:682
4951 msgid ""
4952 "Critical to Mercurial's performance is the avoidance of seeks of the disk "
4953 "head, since any seek is far more expensive than even a comparatively large "
4954 "read operation."
4955 msgstr ""
4957 #. type: Content of: <book><chapter><sect1><sect2><para>
4958 #: ../en/ch04-concepts.xml:686
4959 msgid ""
4960 "This is why, for example, the dirstate is stored in a single file. If there "
4961 "were a dirstate file per directory that Mercurial tracked, the disk would "
4962 "seek once per directory. Instead, Mercurial reads the entire single dirstate "
4963 "file in one step."
4964 msgstr ""
4966 #. type: Content of: <book><chapter><sect1><sect2><para>
4967 #: ../en/ch04-concepts.xml:692
4968 msgid ""
4969 "Mercurial also uses a <quote>copy on write</quote> scheme when cloning a "
4970 "repository on local storage. Instead of copying every revlog file from the "
4971 "old repository into the new repository, it makes a <quote>hard link</quote>, "
4972 "which is a shorthand way to say <quote>these two names point to the same "
4973 "file</quote>. When Mercurial is about to write to one of a revlog's files, "
4974 "it checks to see if the number of names pointing at the file is greater than "
4975 "one. If it is, more than one repository is using the file, so Mercurial "
4976 "makes a new copy of the file that is private to this repository."
4977 msgstr ""
4979 #. type: Content of: <book><chapter><sect1><sect2><para>
4980 #: ../en/ch04-concepts.xml:703
4981 msgid ""
4982 "A few revision control developers have pointed out that this idea of making a "
4983 "complete private copy of a file is not very efficient in its use of storage. "
4984 "While this is true, storage is cheap, and this method gives the highest "
4985 "performance while deferring most book-keeping to the operating system. An "
4986 "alternative scheme would most likely reduce performance and increase the "
4987 "complexity of the software, each of which is much more important to the "
4988 "<quote>feel</quote> of day-to-day use."
4989 msgstr ""
4991 #. type: Content of: <book><chapter><sect1><sect2><title>
4992 #: ../en/ch04-concepts.xml:715
4993 msgid "Other contents of the dirstate"
4994 msgstr "目录状态的其它内容"
4996 #. type: Content of: <book><chapter><sect1><sect2><para>
4997 #: ../en/ch04-concepts.xml:717
4998 msgid ""
4999 "Because Mercurial doesn't force you to tell it when you're modifying a file, "
5000 "it uses the dirstate to store some extra information so it can determine "
5001 "efficiently whether you have modified a file. For each file in the working "
5002 "directory, it stores the time that it last modified the file itself, and the "
5003 "size of the file at that time."
5004 msgstr ""
5006 #. type: Content of: <book><chapter><sect1><sect2><para>
5007 #: ../en/ch04-concepts.xml:724
5008 msgid ""
5009 "When you explicitly <command role=\"hg-cmd\">hg add</command>, <command role="
5010 "\"hg-cmd\">hg remove</command>, <command role=\"hg-cmd\">hg rename</command> "
5011 "or <command role=\"hg-cmd\">hg copy</command> files, Mercurial updates the "
5012 "dirstate so that it knows what to do with those files when you commit."
5013 msgstr ""
5015 #. type: Content of: <book><chapter><sect1><sect2><para>
5016 #: ../en/ch04-concepts.xml:731
5017 msgid ""
5018 "When Mercurial is checking the states of files in the working directory, it "
5019 "first checks a file's modification time. If that has not changed, the file "
5020 "must not have been modified. If the file's size has changed, the file must "
5021 "have been modified. If the modification time has changed, but the size has "
5022 "not, only then does Mercurial need to read the actual contents of the file to "
5023 "see if they've changed. Storing these few extra pieces of information "
5024 "dramatically reduces the amount of data that Mercurial needs to read, which "
5025 "yields large performance improvements compared to other revision control "
5026 "systems."
5027 msgstr ""
5029 #. type: Content of: <book><chapter><title>
5030 #: ../en/ch05-daily.xml:5
5031 msgid "Mercurial in daily use"
5032 msgstr "Mercurial 的日常使用"
5034 #. type: Content of: <book><chapter><sect1><title>
5035 #: ../en/ch05-daily.xml:8
5036 msgid "Telling Mercurial which files to track"
5037 msgstr "告诉 Mercurial 要跟踪哪些文件"
5039 #. type: Content of: <book><chapter><sect1><para>
5040 #: ../en/ch05-daily.xml:10
5041 msgid ""
5042 "Mercurial does not work with files in your repository unless you tell it to "
5043 "manage them. The <command role=\"hg-cmd\">hg status</command> command will "
5044 "tell you which files Mercurial doesn't know about; it uses a <quote><literal>?"
5045 "</literal></quote> to display such files."
5046 msgstr ""
5048 #
5049 #. type: Content of: <book><chapter><sect1><para>
5050 #: ../en/ch05-daily.xml:17
5051 msgid ""
5052 "To tell Mercurial to track a file, use the <command role=\"hg-cmd\">hg add</"
5053 "command> command. Once you have added a file, the entry in the output of "
5054 "<command role=\"hg-cmd\">hg status</command> for that file changes from "
5055 "<quote><literal>?</literal></quote> to <quote><literal>A</literal></quote>."
5056 msgstr ""
5058 #. type: Content of: <book><chapter><sect1><para>
5059 #: ../en/ch05-daily.xml:26
5060 msgid ""
5061 "After you run a <command role=\"hg-cmd\">hg commit</command>, the files that "
5062 "you added before the commit will no longer be listed in the output of "
5063 "<command role=\"hg-cmd\">hg status</command>. The reason for this is that "
5064 "<command role=\"hg-cmd\">hg status</command> only tells you about "
5065 "<quote>interesting</quote> files&emdash;those that you have modified or told "
5066 "Mercurial to do something with&emdash;by default. If you have a repository "
5067 "that contains thousands of files, you will rarely want to know about files "
5068 "that Mercurial is tracking, but that have not changed. (You can still get "
5069 "this information; we'll return to this later.)"
5070 msgstr ""
5072 #. type: Content of: <book><chapter><sect1><para>
5073 #: ../en/ch05-daily.xml:38
5074 msgid ""
5075 "Once you add a file, Mercurial doesn't do anything with it immediately. "
5076 "Instead, it will take a snapshot of the file's state the next time you "
5077 "perform a commit. It will then continue to track the changes you make to the "
5078 "file every time you commit, until you remove the file."
5079 msgstr ""
5081 #. type: Content of: <book><chapter><sect1><sect2><title>
5082 #: ../en/ch05-daily.xml:45
5083 msgid "Explicit versus implicit file naming"
5084 msgstr "明确与隐含文件命名"
5086 #. type: Content of: <book><chapter><sect1><sect2><para>
5087 #: ../en/ch05-daily.xml:47
5088 msgid ""
5089 "A useful behaviour that Mercurial has is that if you pass the name of a "
5090 "directory to a command, every Mercurial command will treat this as <quote>I "
5091 "want to operate on every file in this directory and its subdirectories</"
5092 "quote>."
5093 msgstr ""
5095 #. type: Content of: <book><chapter><sect1><sect2><para>
5096 #: ../en/ch05-daily.xml:54
5097 msgid ""
5098 "Notice in this example that Mercurial printed the names of the files it "
5099 "added, whereas it didn't do so when we added the file named <filename>a</"
5100 "filename> in the earlier example."
5101 msgstr ""
5103 #. type: Content of: <book><chapter><sect1><sect2><para>
5104 #: ../en/ch05-daily.xml:59
5105 msgid ""
5106 "What's going on is that in the former case, we explicitly named the file to "
5107 "add on the command line, so the assumption that Mercurial makes in such cases "
5108 "is that you know what you were doing, and it doesn't print any output."
5109 msgstr ""
5111 #. type: Content of: <book><chapter><sect1><sect2><para>
5112 #: ../en/ch05-daily.xml:64
5113 msgid ""
5114 "However, when we <emphasis>imply</emphasis> the names of files by giving the "
5115 "name of a directory, Mercurial takes the extra step of printing the name of "
5116 "each file that it does something with. This makes it more clear what is "
5117 "happening, and reduces the likelihood of a silent and nasty surprise. This "
5118 "behaviour is common to most Mercurial commands."
5119 msgstr ""
5121 #. type: Content of: <book><chapter><sect1><sect2><title>
5122 #: ../en/ch05-daily.xml:73
5123 msgid "Aside: Mercurial tracks files, not directories"
5124 msgstr "旁白: Mercurial 只跟踪文件，不跟踪目录"
5126 #. type: Content of: <book><chapter><sect1><sect2><para>
5127 #: ../en/ch05-daily.xml:75
5128 msgid ""
5129 "Mercurial does not track directory information. Instead, it tracks the path "
5130 "to a file. Before creating a file, it first creates any missing directory "
5131 "components of the path. After it deletes a file, it then deletes any empty "
5132 "directories that were in the deleted file's path. This sounds like a trivial "
5133 "distinction, but it has one minor practical consequence: it is not possible "
5134 "to represent a completely empty directory in Mercurial."
5135 msgstr ""
5137 #. type: Content of: <book><chapter><sect1><sect2><para>
5138 #: ../en/ch05-daily.xml:84
5139 msgid ""
5140 "Empty directories are rarely useful, and there are unintrusive workarounds "
5141 "that you can use to achieve an appropriate effect. The developers of "
5142 "Mercurial thus felt that the complexity that would be required to manage "
5143 "empty directories was not worth the limited benefit this feature would bring."
5144 msgstr ""
5146 #. type: Content of: <book><chapter><sect1><sect2><para>
5147 #: ../en/ch05-daily.xml:91
5148 msgid ""
5149 "If you need an empty directory in your repository, there are a few ways to "
5150 "achieve this. One is to create a directory, then <command role=\"hg-cmd\">hg "
5151 "add</command> a <quote>hidden</quote> file to that directory. On Unix-like "
5152 "systems, any file name that begins with a period (<quote><literal>.</"
5153 "literal></quote>) is treated as hidden by most commands and GUI tools. This "
5154 "approach is illustrated below."
5155 msgstr ""
5157 #. type: Content of: <book><chapter><sect1><sect2><para>
5158 #: ../en/ch05-daily.xml:102
5159 msgid ""
5160 "Another way to tackle a need for an empty directory is to simply create one "
5161 "in your automated build scripts before they will need it."
5162 msgstr ""
5164 #. type: Content of: <book><chapter><sect1><title>
5165 #: ../en/ch05-daily.xml:109
5166 msgid "How to stop tracking a file"
5167 msgstr "如何停止跟踪文件"
5169 #
5170 #. type: Content of: <book><chapter><sect1><para>
5171 #: ../en/ch05-daily.xml:111
5172 msgid ""
5173 "Once you decide that a file no longer belongs in your repository, use the "
5174 "<command role=\"hg-cmd\">hg remove</command> command; this deletes the file, "
5175 "and tells Mercurial to stop tracking it. A removed file is represented in "
5176 "the output of <command role=\"hg-cmd\">hg status</command> with a "
5177 "<quote><literal>R</literal></quote>."
5178 msgstr ""
5180 #. type: Content of: <book><chapter><sect1><para>
5181 #: ../en/ch05-daily.xml:120
5182 msgid ""
5183 "After you <command role=\"hg-cmd\">hg remove</command> a file, Mercurial will "
5184 "no longer track changes to that file, even if you recreate a file with the "
5185 "same name in your working directory. If you do recreate a file with the same "
5186 "name and want Mercurial to track the new file, simply <command role=\"hg-cmd"
5187 "\">hg add</command> it. Mercurial will know that the newly added file is not "
5188 "related to the old file of the same name."
5189 msgstr ""
5191 #. type: Content of: <book><chapter><sect1><sect2><title>
5192 #: ../en/ch05-daily.xml:129
5193 msgid "Removing a file does not affect its history"
5194 msgstr "删除文件不影响历史"
5196 #. type: Content of: <book><chapter><sect1><sect2><para>
5197 #: ../en/ch05-daily.xml:131
5198 msgid "It is important to understand that removing a file has only two effects."
5199 msgstr ""
5201 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
5202 #: ../en/ch05-daily.xml:134
5203 msgid "It removes the current version of the file from the working directory."
5204 msgstr ""
5206 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
5207 #: ../en/ch05-daily.xml:137
5208 msgid ""
5209 "It stops Mercurial from tracking changes to the file, from the time of the "
5210 "next commit."
5211 msgstr ""
5213 #. type: Content of: <book><chapter><sect1><sect2><para>
5214 #: ../en/ch05-daily.xml:140
5215 msgid ""
5216 "Removing a file <emphasis>does not</emphasis> in any way alter the "
5217 "<emphasis>history</emphasis> of the file."
5218 msgstr ""
5220 #. type: Content of: <book><chapter><sect1><sect2><para>
5221 #: ../en/ch05-daily.xml:143
5222 msgid ""
5223 "If you update the working directory to a changeset in which a file that you "
5224 "have removed was still tracked, it will reappear in the working directory, "
5225 "with the contents it had when you committed that changeset. If you then "
5226 "update the working directory to a later changeset, in which the file had been "
5227 "removed, Mercurial will once again remove the file from the working directory."
5228 msgstr ""
5230 #. type: Content of: <book><chapter><sect1><sect2><title>
5231 #: ../en/ch05-daily.xml:153
5232 msgid "Missing files"
5233 msgstr "丢失的文件"
5235 #. type: Content of: <book><chapter><sect1><sect2><para>
5236 #: ../en/ch05-daily.xml:155
5237 msgid ""
5238 "Mercurial considers a file that you have deleted, but not used <command role="
5239 "\"hg-cmd\">hg remove</command> to delete, to be <emphasis>missing</"
5240 "emphasis>. A missing file is represented with <quote><literal>!</literal></"
5241 "quote> in the output of <command role=\"hg-cmd\">hg status</command>. "
5242 "Mercurial commands will not generally do anything with missing files."
5243 msgstr ""
5245 #. type: Content of: <book><chapter><sect1><sect2><para>
5246 #: ../en/ch05-daily.xml:165
5247 msgid ""
5248 "If your repository contains a file that <command role=\"hg-cmd\">hg status</"
5249 "command> reports as missing, and you want the file to stay gone, you can run "
5250 "<command role=\"hg-cmd\">hg remove <option role=\"hg-opt-remove\">--after</"
5251 "option></command> at any time later on, to tell Mercurial that you really did "
5252 "mean to remove the file."
5253 msgstr ""
5255 #. type: Content of: <book><chapter><sect1><sect2><para>
5256 #: ../en/ch05-daily.xml:175
5257 msgid ""
5258 "On the other hand, if you deleted the missing file by accident, give <command "
5259 "role=\"hg-cmd\">hg revert</command> the name of the file to recover. It will "
5260 "reappear, in unmodified form."
5261 msgstr ""
5263 #. type: Content of: <book><chapter><sect1><sect2><title>
5264 #: ../en/ch05-daily.xml:184
5265 msgid "Aside: why tell Mercurial explicitly to remove a file?"
5266 msgstr "旁白: 为什么要明确告诉 Mercurial 删除文件?"
5268 #. type: Content of: <book><chapter><sect1><sect2><para>
5269 #: ../en/ch05-daily.xml:187
5270 msgid ""
5271 "You might wonder why Mercurial requires you to explicitly tell it that you "
5272 "are deleting a file. Early during the development of Mercurial, it let you "
5273 "delete a file however you pleased; Mercurial would notice the absence of the "
5274 "file automatically when you next ran a <command role=\"hg-cmd\">hg commit</"
5275 "command>, and stop tracking the file. In practice, this made it too easy to "
5276 "accidentally remove a file without noticing."
5277 msgstr ""
5279 #. type: Content of: <book><chapter><sect1><sect2><title>
5280 #: ../en/ch05-daily.xml:198
5281 msgid "Useful shorthand&emdash;adding and removing files in one step"
5282 msgstr "有用的速记&emdash;一个步骤添加和删除文件"
5284 #. type: Content of: <book><chapter><sect1><sect2><para>
5285 #: ../en/ch05-daily.xml:201
5286 msgid ""
5287 "Mercurial offers a combination command, <command role=\"hg-cmd\">hg "
5288 "addremove</command>, that adds untracked files and marks missing files as "
5289 "removed."
5290 msgstr ""
5292 #. type: Content of: <book><chapter><sect1><sect2><para>
5293 #: ../en/ch05-daily.xml:207
5294 msgid ""
5295 "The <command role=\"hg-cmd\">hg commit</command> command also provides a "
5296 "<option role=\"hg-opt-commit\">-A</option> option that performs this same add-"
5297 "and-remove, immediately followed by a commit."
5298 msgstr ""
5300 #. type: Content of: <book><chapter><sect1><title>
5301 #: ../en/ch05-daily.xml:217
5302 msgid "Copying files"
5303 msgstr "复制文件"
5305 #. type: Content of: <book><chapter><sect1><para>
5306 #: ../en/ch05-daily.xml:219
5307 msgid ""
5308 "Mercurial provides a <command role=\"hg-cmd\">hg copy</command> command that "
5309 "lets you make a new copy of a file. When you copy a file using this command, "
5310 "Mercurial makes a record of the fact that the new file is a copy of the "
5311 "original file. It treats these copied files specially when you merge your "
5312 "work with someone else's."
5313 msgstr ""
5315 #. type: Content of: <book><chapter><sect1><sect2><title>
5316 #: ../en/ch05-daily.xml:227
5317 msgid "The results of copying during a merge"
5318 msgstr "合并期间的复制结果"
5320 #. type: Content of: <book><chapter><sect1><sect2><para>
5321 #: ../en/ch05-daily.xml:229
5322 msgid ""
5323 "What happens during a merge is that changes <quote>follow</quote> a copy. To "
5324 "best illustrate what this means, let's create an example. We'll start with "
5325 "the usual tiny repository that contains a single file."
5326 msgstr ""
5328 #. type: Content of: <book><chapter><sect1><sect2><para>
5329 #: ../en/ch05-daily.xml:236
5330 msgid ""
5331 "We need to do some work in parallel, so that we'll have something to merge. "
5332 "So let's clone our repository."
5333 msgstr ""
5335 #. type: Content of: <book><chapter><sect1><sect2><para>
5336 #: ../en/ch05-daily.xml:242
5337 msgid ""
5338 "Back in our initial repository, let's use the <command role=\"hg-cmd\">hg "
5339 "copy</command> command to make a copy of the first file we created."
5340 msgstr ""
5342 #. type: Content of: <book><chapter><sect1><sect2><para>
5343 #: ../en/ch05-daily.xml:248
5344 msgid ""
5345 "If we look at the output of the <command role=\"hg-cmd\">hg status</command> "
5346 "command afterwards, the copied file looks just like a normal added file."
5347 msgstr ""
5349 #. type: Content of: <book><chapter><sect1><sect2><para>
5350 #: ../en/ch05-daily.xml:254
5351 msgid ""
5352 "But if we pass the <option role=\"hg-opt-status\">-C</option> option to "
5353 "<command role=\"hg-cmd\">hg status</command>, it prints another line of "
5354 "output: this is the file that our newly-added file was copied <emphasis>from</"
5355 "emphasis>."
5356 msgstr ""
5358 #. type: Content of: <book><chapter><sect1><sect2><para>
5359 #: ../en/ch05-daily.xml:262
5360 msgid ""
5361 "Now, back in the repository we cloned, let's make a change in parallel. "
5362 "We'll add a line of content to the original file that we created."
5363 msgstr ""
5365 #. type: Content of: <book><chapter><sect1><sect2><para>
5366 #: ../en/ch05-daily.xml:268
5367 msgid ""
5368 "Now we have a modified <filename>file</filename> in this repository. When we "
5369 "pull the changes from the first repository, and merge the two heads, "
5370 "Mercurial will propagate the changes that we made locally to <filename>file</"
5371 "filename> into its copy, <filename>new-file</filename>."
5372 msgstr ""
5374 #. type: Content of: <book><chapter><sect1><sect2><title>
5375 #: ../en/ch05-daily.xml:278
5376 msgid "Why should changes follow copies?"
5377 msgstr "为什么复制后需要后续修改?"
5379 #. type: Content of: <book><chapter><sect1><sect2><para>
5380 #: ../en/ch05-daily.xml:280
5381 msgid ""
5382 "This behaviour, of changes to a file propagating out to copies of the file, "
5383 "might seem esoteric, but in most cases it's highly desirable."
5384 msgstr ""
5386 #. type: Content of: <book><chapter><sect1><sect2><para>
5387 #: ../en/ch05-daily.xml:284
5388 msgid ""
5389 "First of all, remember that this propagation <emphasis>only</emphasis> "
5390 "happens when you merge. So if you <command role=\"hg-cmd\">hg copy</command> "
5391 "a file, and subsequently modify the original file during the normal course of "
5392 "your work, nothing will happen."
5393 msgstr ""
5395 #. type: Content of: <book><chapter><sect1><sect2><para>
5396 #: ../en/ch05-daily.xml:290
5397 msgid ""
5398 "The second thing to know is that modifications will only propagate across a "
5399 "copy as long as the repository that you're pulling changes from "
5400 "<emphasis>doesn't know</emphasis> about the copy."
5401 msgstr ""
5403 #. type: Content of: <book><chapter><sect1><sect2><para>
5404 #: ../en/ch05-daily.xml:295
5405 msgid ""
5406 "The reason that Mercurial does this is as follows. Let's say I make an "
5407 "important bug fix in a source file, and commit my changes. Meanwhile, you've "
5408 "decided to <command role=\"hg-cmd\">hg copy</command> the file in your "
5409 "repository, without knowing about the bug or having seen the fix, and you "
5410 "have started hacking on your copy of the file."
5411 msgstr ""
5413 #. type: Content of: <book><chapter><sect1><sect2><para>
5414 #: ../en/ch05-daily.xml:302
5415 msgid ""
5416 "If you pulled and merged my changes, and Mercurial <emphasis>didn't</"
5417 "emphasis> propagate changes across copies, your source file would now contain "
5418 "the bug, and unless you remembered to propagate the bug fix by hand, the bug "
5419 "would <emphasis>remain</emphasis> in your copy of the file."
5420 msgstr ""
5422 #. type: Content of: <book><chapter><sect1><sect2><para>
5423 #: ../en/ch05-daily.xml:308
5424 msgid ""
5425 "By automatically propagating the change that fixed the bug from the original "
5426 "file to the copy, Mercurial prevents this class of problem. To my knowledge, "
5427 "Mercurial is the <emphasis>only</emphasis> revision control system that "
5428 "propagates changes across copies like this."
5429 msgstr ""
5431 #. type: Content of: <book><chapter><sect1><sect2><para>
5432 #: ../en/ch05-daily.xml:314
5433 msgid ""
5434 "Once your change history has a record that the copy and subsequent merge "
5435 "occurred, there's usually no further need to propagate changes from the "
5436 "original file to the copied file, and that's why Mercurial only propagates "
5437 "changes across copies until this point, and no further."
5438 msgstr ""
5440 #. type: Content of: <book><chapter><sect1><sect2><title>
5441 #: ../en/ch05-daily.xml:322
5442 msgid "How to make changes <emphasis>not</emphasis> follow a copy"
5443 msgstr "如何让复制后<emphasis>不</emphasis>修改?"
5445 #. type: Content of: <book><chapter><sect1><sect2><para>
5446 #: ../en/ch05-daily.xml:325
5447 msgid ""
5448 "If, for some reason, you decide that this business of automatically "
5449 "propagating changes across copies is not for you, simply use your system's "
5450 "normal file copy command (on Unix-like systems, that's <command>cp</command>) "
5451 "to make a copy of a file, then <command role=\"hg-cmd\">hg add</command> the "
5452 "new copy by hand. Before you do so, though, please do reread section <xref "
5453 "linkend=\"sec.daily.why-copy\"/>, and make an informed decision that this "
5454 "behaviour is not appropriate to your specific case."
5455 msgstr ""
5457 #. type: Content of: <book><chapter><sect1><sect2><title>
5458 #: ../en/ch05-daily.xml:338
5459 msgid "Behaviour of the <command role=\"hg-cmd\">hg copy</command> command"
5460 msgstr "命令 <command role=\"hg-cmd\">hg copy</command> 的特性"
5462 #. type: Content of: <book><chapter><sect1><sect2><para>
5463 #: ../en/ch05-daily.xml:341
5464 msgid ""
5465 "When you use the <command role=\"hg-cmd\">hg copy</command> command, "
5466 "Mercurial makes a copy of each source file as it currently stands in the "
5467 "working directory. This means that if you make some modifications to a file, "
5468 "then <command role=\"hg-cmd\">hg copy</command> it without first having "
5469 "committed those changes, the new copy will also contain the modifications you "
5470 "have made up until that point. (I find this behaviour a little "
5471 "counterintuitive, which is why I mention it here.)"
5472 msgstr ""
5474 #. type: Content of: <book><chapter><sect1><sect2><para>
5475 #: ../en/ch05-daily.xml:351
5476 msgid ""
5477 "The <command role=\"hg-cmd\">hg copy</command> command acts similarly to the "
5478 "Unix <command>cp</command> command (you can use the <command role=\"hg-cmd"
5479 "\">hg cp</command> alias if you prefer). The last argument is the "
5480 "<emphasis>destination</emphasis>, and all prior arguments are "
5481 "<emphasis>sources</emphasis>. If you pass it a single file as the source, "
5482 "and the destination does not exist, it creates a new file with that name."
5483 msgstr ""
5485 #. type: Content of: <book><chapter><sect1><sect2><para>
5486 #: ../en/ch05-daily.xml:362
5487 msgid ""
5488 "If the destination is a directory, Mercurial copies its sources into that "
5489 "directory."
5490 msgstr ""
5492 #. type: Content of: <book><chapter><sect1><sect2><para>
5493 #: ../en/ch05-daily.xml:367
5494 msgid ""
5495 "Copying a directory is recursive, and preserves the directory structure of "
5496 "the source."
5497 msgstr ""
5499 #. type: Content of: <book><chapter><sect1><sect2><para>
5500 #: ../en/ch05-daily.xml:373
5501 msgid ""
5502 "If the source and destination are both directories, the source tree is "
5503 "recreated in the destination directory."
5504 msgstr ""
5506 #
5507 #. type: Content of: <book><chapter><sect1><sect2><para>
5508 #: ../en/ch05-daily.xml:378
5509 msgid ""
5510 "As with the <command role=\"hg-cmd\">hg rename</command> command, if you copy "
5511 "a file manually and then want Mercurial to know that you've copied the file, "
5512 "simply use the <option role=\"hg-opt-copy\">--after</option> option to "
5513 "<command role=\"hg-cmd\">hg copy</command>."
5514 msgstr ""
5516 #. type: Content of: <book><chapter><sect1><title>
5517 #: ../en/ch05-daily.xml:389
5518 msgid "Renaming files"
5519 msgstr "改名文件"
5521 #. type: Content of: <book><chapter><sect1><para>
5522 #: ../en/ch05-daily.xml:391
5523 msgid ""
5524 "It's rather more common to need to rename a file than to make a copy of it. "
5525 "The reason I discussed the <command role=\"hg-cmd\">hg copy</command> command "
5526 "before talking about renaming files is that Mercurial treats a rename in "
5527 "essentially the same way as a copy. Therefore, knowing what Mercurial does "
5528 "when you copy a file tells you what to expect when you rename a file."
5529 msgstr ""
5531 #. type: Content of: <book><chapter><sect1><para>
5532 #: ../en/ch05-daily.xml:399
5533 msgid ""
5534 "When you use the <command role=\"hg-cmd\">hg rename</command> command, "
5535 "Mercurial makes a copy of each source file, then deletes it and marks the "
5536 "file as removed."
5537 msgstr ""
5539 #. type: Content of: <book><chapter><sect1><para>
5540 #: ../en/ch05-daily.xml:405
5541 msgid ""
5542 "The <command role=\"hg-cmd\">hg status</command> command shows the newly "
5543 "copied file as added, and the copied-from file as removed."
5544 msgstr ""
5546 #. type: Content of: <book><chapter><sect1><para>
5547 #: ../en/ch05-daily.xml:411
5548 msgid ""
5549 "As with the results of a <command role=\"hg-cmd\">hg copy</command>, we must "
5550 "use the <option role=\"hg-opt-status\">-C</option> option to <command role="
5551 "\"hg-cmd\">hg status</command> to see that the added file is really being "
5552 "tracked by Mercurial as a copy of the original, now removed, file."
5553 msgstr ""
5555 #. type: Content of: <book><chapter><sect1><para>
5556 #: ../en/ch05-daily.xml:420
5557 msgid ""
5558 "As with <command role=\"hg-cmd\">hg remove</command> and <command role=\"hg-"
5559 "cmd\">hg copy</command>, you can tell Mercurial about a rename after the fact "
5560 "using the <option role=\"hg-opt-rename\">--after</option> option. In most "
5561 "other respects, the behaviour of the <command role=\"hg-cmd\">hg rename</"
5562 "command> command, and the options it accepts, are similar to the <command "
5563 "role=\"hg-cmd\">hg copy</command> command."
5564 msgstr ""
5566 #. type: Content of: <book><chapter><sect1><sect2><title>
5567 #: ../en/ch05-daily.xml:430
5568 msgid "Renaming files and merging changes"
5569 msgstr "改名文件与合并修改"
5571 #. type: Content of: <book><chapter><sect1><sect2><para>
5572 #: ../en/ch05-daily.xml:432
5573 msgid ""
5574 "Since Mercurial's rename is implemented as copy-and-remove, the same "
5575 "propagation of changes happens when you merge after a rename as after a copy."
5576 msgstr ""
5578 #. type: Content of: <book><chapter><sect1><sect2><para>
5579 #: ../en/ch05-daily.xml:436
5580 msgid ""
5581 "If I modify a file, and you rename it to a new name, and then we merge our "
5582 "respective changes, my modifications to the file under its original name will "
5583 "be propagated into the file under its new name. (This is something you might "
5584 "expect to <quote>simply work,</quote> but not all revision control systems "
5585 "actually do this.)"
5586 msgstr ""
5588 #. type: Content of: <book><chapter><sect1><sect2><para>
5589 #: ../en/ch05-daily.xml:443
5590 msgid ""
5591 "Whereas having changes follow a copy is a feature where you can perhaps nod "
5592 "and say <quote>yes, that might be useful,</quote> it should be clear that "
5593 "having them follow a rename is definitely important. Without this facility, "
5594 "it would simply be too easy for changes to become orphaned when files are "
5595 "renamed."
5596 msgstr ""
5598 #. type: Content of: <book><chapter><sect1><sect2><title>
5599 #: ../en/ch05-daily.xml:452
5600 msgid "Divergent renames and merging"
5601 msgstr "改名与合并的分歧"
5603 #. type: Content of: <book><chapter><sect1><sect2><para>
5604 #: ../en/ch05-daily.xml:454
5605 msgid ""
5606 "The case of diverging names occurs when two developers start with a "
5607 "file&emdash;let's call it <filename>foo</filename>&emdash;in their respective "
5608 "repositories."
5609 msgstr ""
5611 #. type: Content of: <book><chapter><sect1><sect2><para>
5612 #: ../en/ch05-daily.xml:461
5613 msgid "Anne renames the file to <filename>bar</filename>."
5614 msgstr ""
5616 #. type: Content of: <book><chapter><sect1><sect2><para>
5617 #: ../en/ch05-daily.xml:465
5618 msgid "Meanwhile, Bob renames it to <filename>quux</filename>."
5619 msgstr ""
5621 #. type: Content of: <book><chapter><sect1><sect2><para>
5622 #: ../en/ch05-daily.xml:470
5623 msgid ""
5624 "I like to think of this as a conflict because each developer has expressed "
5625 "different intentions about what the file ought to be named."
5626 msgstr ""
5628 #
5629 #. type: Content of: <book><chapter><sect1><sect2><para>
5630 #: ../en/ch05-daily.xml:474
5631 msgid ""
5632 "What do you think should happen when they merge their work? Mercurial's "
5633 "actual behaviour is that it always preserves <emphasis>both</emphasis> names "
5634 "when it merges changesets that contain divergent renames."
5635 msgstr ""
5637 #. type: Content of: <book><chapter><sect1><sect2><para>
5638 #: ../en/ch05-daily.xml:481
5639 msgid ""
5640 "Notice that Mercurial does warn about the divergent renames, but it leaves it "
5641 "up to you to do something about the divergence after the merge."
5642 msgstr ""
5644 #. type: Content of: <book><chapter><sect1><sect2><title>
5645 #: ../en/ch05-daily.xml:487
5646 msgid "Convergent renames and merging"
5647 msgstr "收敛改名与合并"
5649 #. type: Content of: <book><chapter><sect1><sect2><para>
5650 #: ../en/ch05-daily.xml:489
5651 msgid ""
5652 "Another kind of rename conflict occurs when two people choose to rename "
5653 "different <emphasis>source</emphasis> files to the same "
5654 "<emphasis>destination</emphasis>. In this case, Mercurial runs its normal "
5655 "merge machinery, and lets you guide it to a suitable resolution."
5656 msgstr ""
5658 #. type: Content of: <book><chapter><sect1><sect2><title>
5659 #: ../en/ch05-daily.xml:497
5660 msgid "Other name-related corner cases"
5661 msgstr "其它名称相关的角落"
5663 #. type: Content of: <book><chapter><sect1><sect2><para>
5664 #: ../en/ch05-daily.xml:499
5665 msgid ""
5666 "Mercurial has a longstanding bug in which it fails to handle a merge where "
5667 "one side has a file with a given name, while another has a directory with the "
5668 "same name. This is documented as <ulink role=\"hg-bug\" url=\"http://www."
5669 "selenic.com/mercurial/bts/issue29\">issue 29</ulink>."
5670 msgstr ""
5672 #. type: Content of: <book><chapter><sect1><title>
5673 #: ../en/ch05-daily.xml:511
5674 msgid "Recovering from mistakes"
5675 msgstr "从错误恢复"
5677 #. type: Content of: <book><chapter><sect1><para>
5678 #: ../en/ch05-daily.xml:513
5679 msgid ""
5680 "Mercurial has some useful commands that will help you to recover from some "
5681 "common mistakes."
5682 msgstr ""
5684 #. type: Content of: <book><chapter><sect1><para>
5685 #: ../en/ch05-daily.xml:516
5686 msgid ""
5687 "The <command role=\"hg-cmd\">hg revert</command> command lets you undo "
5688 "changes that you have made to your working directory. For example, if you "
5689 "<command role=\"hg-cmd\">hg add</command> a file by accident, just run "
5690 "<command role=\"hg-cmd\">hg revert</command> with the name of the file you "
5691 "added, and while the file won't be touched in any way, it won't be tracked "
5692 "for adding by Mercurial any longer, either. You can also use <command role="
5693 "\"hg-cmd\">hg revert</command> to get rid of erroneous changes to a file."
5694 msgstr ""
5696 #. type: Content of: <book><chapter><sect1><para>
5697 #: ../en/ch05-daily.xml:526
5698 msgid ""
5699 "It's useful to remember that the <command role=\"hg-cmd\">hg revert</command> "
5700 "command is useful for changes that you have not yet committed. Once you've "
5701 "committed a change, if you decide it was a mistake, you can still do "
5702 "something about it, though your options may be more limited."
5703 msgstr ""
5705 #. type: Content of: <book><chapter><sect1><para>
5706 #: ../en/ch05-daily.xml:532
5707 msgid ""
5708 "For more information about the <command role=\"hg-cmd\">hg revert</command> "
5709 "command, and details about how to deal with changes you have already "
5710 "committed, see chapter <xref linkend=\"chap.undo\"/>."
5711 msgstr ""
5713 #. type: Content of: <book><chapter><title>
5714 #: ../en/ch06-collab.xml:5
5715 msgid "Collaborating with other people"
5716 msgstr "团体协作"
5718 #. type: Content of: <book><chapter><para>
5719 #: ../en/ch06-collab.xml:7
5720 msgid ""
5721 "As a completely decentralised tool, Mercurial doesn't impose any policy on "
5722 "how people ought to work with each other. However, if you're new to "
5723 "distributed revision control, it helps to have some tools and examples in "
5724 "mind when you're thinking about possible workflow models."
5725 msgstr ""
5727 #. type: Content of: <book><chapter><sect1><title>
5728 #: ../en/ch06-collab.xml:14
5729 msgid "Mercurial's web interface"
5730 msgstr "Mercurial 的 web 接口"
5732 #. type: Content of: <book><chapter><sect1><para>
5733 #: ../en/ch06-collab.xml:16
5734 msgid ""
5735 "Mercurial has a powerful web interface that provides several useful "
5736 "capabilities."
5737 msgstr ""
5739 #. type: Content of: <book><chapter><sect1><para>
5740 #: ../en/ch06-collab.xml:19
5741 msgid ""
5742 "For interactive use, the web interface lets you browse a single repository or "
5743 "a collection of repositories. You can view the history of a repository, "
5744 "examine each change (comments and diffs), and view the contents of each "
5745 "directory and file."
5746 msgstr ""
5748 #. type: Content of: <book><chapter><sect1><para>
5749 #: ../en/ch06-collab.xml:24
5750 msgid ""
5751 "Also for human consumption, the web interface provides an RSS feed of the "
5752 "changes in a repository. This lets you <quote>subscribe</quote> to a "
5753 "repository using your favourite feed reader, and be automatically notified of "
5754 "activity in that repository as soon as it happens. I find this capability "
5755 "much more convenient than the model of subscribing to a mailing list to which "
5756 "notifications are sent, as it requires no additional configuration on the "
5757 "part of whoever is serving the repository."
5758 msgstr ""
5760 #. type: Content of: <book><chapter><sect1><para>
5761 #: ../en/ch06-collab.xml:34
5762 msgid ""
5763 "The web interface also lets remote users clone a repository, pull changes "
5764 "from it, and (when the server is configured to permit it) push changes back "
5765 "to it. Mercurial's HTTP tunneling protocol aggressively compresses data, so "
5766 "that it works efficiently even over low-bandwidth network connections."
5767 msgstr ""
5769 #. type: Content of: <book><chapter><sect1><para>
5770 #: ../en/ch06-collab.xml:40
5771 msgid ""
5772 "The easiest way to get started with the web interface is to use your web "
5773 "browser to visit an existing repository, such as the master Mercurial "
5774 "repository at <ulink url=\"http://www.selenic.com/repo/hg?style=gitweb"
5775 "\">http://www.selenic.com/repo/hg?style=gitweb</ulink>."
5776 msgstr ""
5778 #. type: Content of: <book><chapter><sect1><para>
5779 #: ../en/ch06-collab.xml:45
5780 msgid ""
5781 "If you're interested in providing a web interface to your own repositories, "
5782 "Mercurial provides two ways to do this. The first is using the <command role="
5783 "\"hg-cmd\">hg serve</command> command, which is best suited to short-term "
5784 "<quote>lightweight</quote> serving. See section <xref linkend=\"sec.collab."
5785 "serve\"/> below for details of how to use this command. If you have a long-"
5786 "lived repository that you'd like to make permanently available, Mercurial has "
5787 "built-in support for the CGI (Common Gateway Interface) standard, which all "
5788 "common web servers support. See section <xref linkend=\"sec.collab.cgi\"/> "
5789 "for details of CGI configuration."
5790 msgstr ""
5792 #. type: Content of: <book><chapter><sect1><title>
5793 #: ../en/ch06-collab.xml:60
5794 msgid "Collaboration models"
5795 msgstr "协作模型"
5797 #. type: Content of: <book><chapter><sect1><para>
5798 #: ../en/ch06-collab.xml:62
5799 msgid ""
5800 "With a suitably flexible tool, making decisions about workflow is much more "
5801 "of a social engineering challenge than a technical one. Mercurial imposes few "
5802 "limitations on how you can structure the flow of work in a project, so it's "
5803 "up to you and your group to set up and live with a model that matches your "
5804 "own particular needs."
5805 msgstr ""
5807 #. type: Content of: <book><chapter><sect1><sect2><title>
5808 #: ../en/ch06-collab.xml:70
5809 msgid "Factors to keep in mind"
5810 msgstr "要牢记的因素"
5812 #. type: Content of: <book><chapter><sect1><sect2><para>
5813 #: ../en/ch06-collab.xml:72
5814 msgid ""
5815 "The most important aspect of any model that you must keep in mind is how well "
5816 "it matches the needs and capabilities of the people who will be using it. "
5817 "This might seem self-evident; even so, you still can't afford to forget it "
5818 "for a moment."
5819 msgstr ""
5821 #. type: Content of: <book><chapter><sect1><sect2><para>
5822 #: ../en/ch06-collab.xml:78
5823 msgid ""
5824 "I once put together a workflow model that seemed to make perfect sense to me, "
5825 "but that caused a considerable amount of consternation and strife within my "
5826 "development team. In spite of my attempts to explain why we needed a complex "
5827 "set of branches, and how changes ought to flow between them, a few team "
5828 "members revolted. Even though they were smart people, they didn't want to "
5829 "pay attention to the constraints we were operating under, or face the "
5830 "consequences of those constraints in the details of the model that I was "
5831 "advocating."
5832 msgstr ""
5834 #. type: Content of: <book><chapter><sect1><sect2><para>
5835 #: ../en/ch06-collab.xml:88
5836 msgid ""
5837 "Don't sweep foreseeable social or technical problems under the rug. Whatever "
5838 "scheme you put into effect, you should plan for mistakes and problem "
5839 "scenarios. Consider adding automated machinery to prevent, or quickly "
5840 "recover from, trouble that you can anticipate. As an example, if you intend "
5841 "to have a branch with not-for-release changes in it, you'd do well to think "
5842 "early about the possibility that someone might accidentally merge those "
5843 "changes into a release branch. You could avoid this particular problem by "
5844 "writing a hook that prevents changes from being merged from an inappropriate "
5845 "branch."
5846 msgstr ""
5848 #. type: Content of: <book><chapter><sect1><sect2><title>
5849 #: ../en/ch06-collab.xml:102
5850 msgid "Informal anarchy"
5851 msgstr "无政府状态"
5853 #. type: Content of: <book><chapter><sect1><sect2><para>
5854 #: ../en/ch06-collab.xml:104
5855 msgid ""
5856 "I wouldn't suggest an <quote>anything goes</quote> approach as something "
5857 "sustainable, but it's a model that's easy to grasp, and it works perfectly "
5858 "well in a few unusual situations."
5859 msgstr ""
5861 #. type: Content of: <book><chapter><sect1><sect2><para>
5862 #: ../en/ch06-collab.xml:109
5863 msgid ""
5864 "As one example, many projects have a loose-knit group of collaborators who "
5865 "rarely physically meet each other. Some groups like to overcome the "
5866 "isolation of working at a distance by organising occasional <quote>sprints</"
5867 "quote>. In a sprint, a number of people get together in a single location (a "
5868 "company's conference room, a hotel meeting room, that kind of place) and "
5869 "spend several days more or less locked in there, hacking intensely on a "
5870 "handful of projects."
5871 msgstr ""
5873 #. type: Content of: <book><chapter><sect1><sect2><para>
5874 #: ../en/ch06-collab.xml:118
5875 msgid ""
5876 "A sprint is the perfect place to use the <command role=\"hg-cmd\">hg serve</"
5877 "command> command, since <command role=\"hg-cmd\">hg serve</command> does not "
5878 "require any fancy server infrastructure. You can get started with <command "
5879 "role=\"hg-cmd\">hg serve</command> in moments, by reading section <xref "
5880 "linkend=\"sec.collab.serve\"/> below. Then simply tell the person next to "
5881 "you that you're running a server, send the URL to them in an instant message, "
5882 "and you immediately have a quick-turnaround way to work together. They can "
5883 "type your URL into their web browser and quickly review your changes; or they "
5884 "can pull a bugfix from you and verify it; or they can clone a branch "
5885 "containing a new feature and try it out."
5886 msgstr ""
5888 #. type: Content of: <book><chapter><sect1><sect2><para>
5889 #: ../en/ch06-collab.xml:132
5890 msgid ""
5891 "The charm, and the problem, with doing things in an ad hoc fashion like this "
5892 "is that only people who know about your changes, and where they are, can see "
5893 "them. Such an informal approach simply doesn't scale beyond a handful "
5894 "people, because each individual needs to know about $n$ different "
5895 "repositories to pull from."
5896 msgstr ""
5898 #. type: Content of: <book><chapter><sect1><sect2><title>
5899 #: ../en/ch06-collab.xml:141
5900 msgid "A single central repository"
5901 msgstr "单一中央版本库"
5903 #. type: Content of: <book><chapter><sect1><sect2><para>
5904 #: ../en/ch06-collab.xml:143
5905 msgid ""
5906 "For smaller projects migrating from a centralised revision control tool, "
5907 "perhaps the easiest way to get started is to have changes flow through a "
5908 "single shared central repository. This is also the most common "
5909 "<quote>building block</quote> for more ambitious workflow schemes."
5910 msgstr ""
5912 #. type: Content of: <book><chapter><sect1><sect2><para>
5913 #: ../en/ch06-collab.xml:149
5914 msgid ""
5915 "Contributors start by cloning a copy of this repository. They can pull "
5916 "changes from it whenever they need to, and some (perhaps all) developers have "
5917 "permission to push a change back when they're ready for other people to see "
5918 "it."
5919 msgstr ""
5921 #. type: Content of: <book><chapter><sect1><sect2><para>
5922 #: ../en/ch06-collab.xml:154
5923 msgid ""
5924 "Under this model, it can still often make sense for people to pull changes "
5925 "directly from each other, without going through the central repository. "
5926 "Consider a case in which I have a tentative bug fix, but I am worried that if "
5927 "I were to publish it to the central repository, it might subsequently break "
5928 "everyone else's trees as they pull it. To reduce the potential for damage, I "
5929 "can ask you to clone my repository into a temporary repository of your own "
5930 "and test it. This lets us put off publishing the potentially unsafe change "
5931 "until it has had a little testing."
5932 msgstr ""
5934 #. type: Content of: <book><chapter><sect1><sect2><para>
5935 #: ../en/ch06-collab.xml:165
5936 msgid ""
5937 "In this kind of scenario, people usually use the <command>ssh</command> "
5938 "protocol to securely push changes to the central repository, as documented in "
5939 "section <xref linkend=\"sec.collab.ssh\"/>. It's also usual to publish a "
5940 "read-only copy of the repository over HTTP using CGI, as in section <xref "
5941 "linkend=\"sec.collab.cgi\"/>. Publishing over HTTP satisfies the needs of "
5942 "people who don't have push access, and those who want to use web browsers to "
5943 "browse the repository's history."
5944 msgstr ""
5946 #. type: Content of: <book><chapter><sect1><sect2><title>
5947 #: ../en/ch06-collab.xml:178
5948 msgid "Working with multiple branches"
5949 msgstr "使用多个分支工作"
5951 #. type: Content of: <book><chapter><sect1><sect2><para>
5952 #: ../en/ch06-collab.xml:180
5953 msgid ""
5954 "Projects of any significant size naturally tend to make progress on several "
5955 "fronts simultaneously. In the case of software, it's common for a project to "
5956 "go through periodic official releases. A release might then go into "
5957 "<quote>maintenance mode</quote> for a while after its first publication; "
5958 "maintenance releases tend to contain only bug fixes, not new features. In "
5959 "parallel with these maintenance releases, one or more future releases may be "
5960 "under development. People normally use the word <quote>branch</quote> to "
5961 "refer to one of these many slightly different directions in which development "
5962 "is proceeding."
5963 msgstr ""
5965 #. type: Content of: <book><chapter><sect1><sect2><para>
5966 #: ../en/ch06-collab.xml:193
5967 msgid ""
5968 "Mercurial is particularly well suited to managing a number of simultaneous, "
5969 "but not identical, branches. Each <quote>development direction</quote> can "
5970 "live in its own central repository, and you can merge changes from one to "
5971 "another as the need arises. Because repositories are independent of each "
5972 "other, unstable changes in a development branch will never affect a stable "
5973 "branch unless someone explicitly merges those changes in."
5974 msgstr ""
5976 #. type: Content of: <book><chapter><sect1><sect2><para>
5977 #: ../en/ch06-collab.xml:202
5978 msgid ""
5979 "Here's an example of how this can work in practice. Let's say you have one "
5980 "<quote>main branch</quote> on a central server."
5981 msgstr ""
5983 #. type: Content of: <book><chapter><sect1><sect2><para>
5984 #: ../en/ch06-collab.xml:208
5985 msgid "People clone it, make changes locally, test them, and push them back."
5986 msgstr ""
5988 #. type: Content of: <book><chapter><sect1><sect2><para>
5989 #: ../en/ch06-collab.xml:211
5990 msgid ""
5991 "Once the main branch reaches a release milestone, you can use the <command "
5992 "role=\"hg-cmd\">hg tag</command> command to give a permanent name to the "
5993 "milestone revision."
5994 msgstr ""
5996 #. type: Content of: <book><chapter><sect1><sect2><para>
5997 #: ../en/ch06-collab.xml:217
5998 msgid "Let's say some ongoing development occurs on the main branch."
5999 msgstr ""
6001 #. type: Content of: <book><chapter><sect1><sect2><para>
6002 #: ../en/ch06-collab.xml:222
6003 msgid ""
6004 "Using the tag that was recorded at the milestone, people who clone that "
6005 "repository at any time in the future can use <command role=\"hg-cmd\">hg "
6006 "update</command> to get a copy of the working directory exactly as it was "
6007 "when that tagged revision was committed."
6008 msgstr ""
6010 #
6011 #. type: Content of: <book><chapter><sect1><sect2><para>
6012 #: ../en/ch06-collab.xml:230
6013 msgid ""
6014 "In addition, immediately after the main branch is tagged, someone can then "
6015 "clone the main branch on the server to a new <quote>stable</quote> branch, "
6016 "also on the server."
6017 msgstr ""
6019 #. type: Content of: <book><chapter><sect1><sect2><para>
6020 #: ../en/ch06-collab.xml:236
6021 msgid ""
6022 "Someone who needs to make a change to the stable branch can then clone "
6023 "<emphasis>that</emphasis> repository, make their changes, commit, and push "
6024 "their changes back there."
6025 msgstr ""
6027 #. type: Content of: <book><chapter><sect1><sect2><para>
6028 #: ../en/ch06-collab.xml:242
6029 msgid ""
6030 "Because Mercurial repositories are independent, and Mercurial doesn't move "
6031 "changes around automatically, the stable and main branches are "
6032 "<emphasis>isolated</emphasis> from each other. The changes that you made on "
6033 "the main branch don't <quote>leak</quote> to the stable branch, and vice "
6034 "versa."
6035 msgstr ""
6037 #. type: Content of: <book><chapter><sect1><sect2><para>
6038 #: ../en/ch06-collab.xml:249
6039 msgid ""
6040 "You'll often want all of your bugfixes on the stable branch to show up on the "
6041 "main branch, too. Rather than rewrite a bugfix on the main branch, you can "
6042 "simply pull and merge changes from the stable to the main branch, and "
6043 "Mercurial will bring those bugfixes in for you."
6044 msgstr ""
6046 #. type: Content of: <book><chapter><sect1><sect2><para>
6047 #: ../en/ch06-collab.xml:257
6048 msgid ""
6049 "The main branch will still contain changes that are not on the stable branch, "
6050 "but it will also contain all of the bugfixes from the stable branch. The "
6051 "stable branch remains unaffected by these changes."
6052 msgstr ""
6054 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
6055 #: ../en/ch06-collab.xml:264 ../en/ch06-collab.xml:278
6056 msgid "Feature branches"
6057 msgstr "特性分支"
6059 #. type: Content of: <book><chapter><sect1><sect2><para>
6060 #: ../en/ch06-collab.xml:266
6061 msgid ""
6062 "For larger projects, an effective way to manage change is to break up a team "
6063 "into smaller groups. Each group has a shared branch of its own, cloned from "
6064 "a single <quote>master</quote> branch used by the entire project. People "
6065 "working on an individual branch are typically quite isolated from "
6066 "developments on other branches."
6067 msgstr ""
6069 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
6070 #: ../en/ch06-collab.xml:275
6071 msgid ""
6072 "<imageobject><imagedata fileref=\"images/feature-branches.png\"/> </"
6073 "imageobject>"
6074 msgstr ""
6076 #. type: Content of: <book><chapter><sect1><sect2><para>
6077 #: ../en/ch06-collab.xml:283
6078 msgid ""
6079 "When a particular feature is deemed to be in suitable shape, someone on that "
6080 "feature team pulls and merges from the master branch into the feature branch, "
6081 "then pushes back up to the master branch."
6082 msgstr ""
6084 #. type: Content of: <book><chapter><sect1><sect2><title>
6085 #: ../en/ch06-collab.xml:290
6086 msgid "The release train"
6087 msgstr "发布列车"
6089 #. type: Content of: <book><chapter><sect1><sect2><para>
6090 #: ../en/ch06-collab.xml:292
6091 msgid ""
6092 "Some projects are organised on a <quote>train</quote> basis: a release is "
6093 "scheduled to happen every few months, and whatever features are ready when "
6094 "the <quote>train</quote> is ready to leave are allowed in."
6095 msgstr ""
6097 #. type: Content of: <book><chapter><sect1><sect2><para>
6098 #: ../en/ch06-collab.xml:297
6099 msgid ""
6100 "This model resembles working with feature branches. The difference is that "
6101 "when a feature branch misses a train, someone on the feature team pulls and "
6102 "merges the changes that went out on that train release into the feature "
6103 "branch, and the team continues its work on top of that release so that their "
6104 "feature can make the next release."
6105 msgstr ""
6107 #. type: Content of: <book><chapter><sect1><sect2><title>
6108 #: ../en/ch06-collab.xml:306
6109 msgid "The Linux kernel model"
6110 msgstr "Linux 内核模型"
6112 #. type: Content of: <book><chapter><sect1><sect2><para>
6113 #: ../en/ch06-collab.xml:308
6114 msgid ""
6115 "The development of the Linux kernel has a shallow hierarchical structure, "
6116 "surrounded by a cloud of apparent chaos. Because most Linux developers use "
6117 "<command>git</command>, a distributed revision control tool with capabilities "
6118 "similar to Mercurial, it's useful to describe the way work flows in that "
6119 "environment; if you like the ideas, the approach translates well across tools."
6120 msgstr ""
6122 #. type: Content of: <book><chapter><sect1><sect2><para>
6123 #: ../en/ch06-collab.xml:316
6124 msgid ""
6125 "At the center of the community sits Linus Torvalds, the creator of Linux. He "
6126 "publishes a single source repository that is considered the "
6127 "<quote>authoritative</quote> current tree by the entire developer community. "
6128 "Anyone can clone Linus's tree, but he is very choosy about whose trees he "
6129 "pulls from."
6130 msgstr ""
6132 #. type: Content of: <book><chapter><sect1><sect2><para>
6133 #: ../en/ch06-collab.xml:323
6134 msgid ""
6135 "Linus has a number of <quote>trusted lieutenants</quote>. As a general rule, "
6136 "he pulls whatever changes they publish, in most cases without even reviewing "
6137 "those changes. Some of those lieutenants are generally agreed to be "
6138 "<quote>maintainers</quote>, responsible for specific subsystems within the "
6139 "kernel. If a random kernel hacker wants to make a change to a subsystem that "
6140 "they want to end up in Linus's tree, they must find out who the subsystem's "
6141 "maintainer is, and ask that maintainer to take their change. If the "
6142 "maintainer reviews their changes and agrees to take them, they'll pass them "
6143 "along to Linus in due course."
6144 msgstr ""
6146 #. type: Content of: <book><chapter><sect1><sect2><para>
6147 #: ../en/ch06-collab.xml:335
6148 msgid ""
6149 "Individual lieutenants have their own approaches to reviewing, accepting, and "
6150 "publishing changes; and for deciding when to feed them to Linus. In "
6151 "addition, there are several well known branches that people use for different "
6152 "purposes. For example, a few people maintain <quote>stable</quote> "
6153 "repositories of older versions of the kernel, to which they apply critical "
6154 "fixes as needed. Some maintainers publish multiple trees: one for "
6155 "experimental changes; one for changes that they are about to feed upstream; "
6156 "and so on. Others just publish a single tree."
6157 msgstr ""
6159 #. type: Content of: <book><chapter><sect1><sect2><para>
6160 #: ../en/ch06-collab.xml:346
6161 msgid ""
6162 "This model has two notable features. The first is that it's <quote>pull "
6163 "only</quote>. You have to ask, convince, or beg another developer to take a "
6164 "change from you, because there are almost no trees to which more than one "
6165 "person can push, and there's no way to push changes into a tree that someone "
6166 "else controls."
6167 msgstr ""
6169 #. type: Content of: <book><chapter><sect1><sect2><para>
6170 #: ../en/ch06-collab.xml:353
6171 msgid ""
6172 "The second is that it's based on reputation and acclaim. If you're an "
6173 "unknown, Linus will probably ignore changes from you without even "
6174 "responding. But a subsystem maintainer will probably review them, and will "
6175 "likely take them if they pass their criteria for suitability. The more "
6176 "<quote>good</quote> changes you contribute to a maintainer, the more likely "
6177 "they are to trust your judgment and accept your changes. If you're well-"
6178 "known and maintain a long-lived branch for something Linus hasn't yet "
6179 "accepted, people with similar interests may pull your changes regularly to "
6180 "keep up with your work."
6181 msgstr ""
6183 #. type: Content of: <book><chapter><sect1><sect2><para>
6184 #: ../en/ch06-collab.xml:364
6185 msgid ""
6186 "Reputation and acclaim don't necessarily cross subsystem or <quote>people</"
6187 "quote> boundaries. If you're a respected but specialised storage hacker, and "
6188 "you try to fix a networking bug, that change will receive a level of scrutiny "
6189 "from a network maintainer comparable to a change from a complete stranger."
6190 msgstr ""
6192 #. type: Content of: <book><chapter><sect1><sect2><para>
6193 #: ../en/ch06-collab.xml:371
6194 msgid ""
6195 "To people who come from more orderly project backgrounds, the comparatively "
6196 "chaotic Linux kernel development process often seems completely insane. It's "
6197 "subject to the whims of individuals; people make sweeping changes whenever "
6198 "they deem it appropriate; and the pace of development is astounding. And yet "
6199 "Linux is a highly successful, well-regarded piece of software."
6200 msgstr ""
6202 #. type: Content of: <book><chapter><sect1><sect2><title>
6203 #: ../en/ch06-collab.xml:381
6204 msgid "Pull-only versus shared-push collaboration"
6205 msgstr "只读与共享写协作"
6207 #. type: Content of: <book><chapter><sect1><sect2><para>
6208 #: ../en/ch06-collab.xml:383
6209 msgid ""
6210 "A perpetual source of heat in the open source community is whether a "
6211 "development model in which people only ever pull changes from others is "
6212 "<quote>better than</quote> one in which multiple people can push changes to a "
6213 "shared repository."
6214 msgstr ""
6216 #. type: Content of: <book><chapter><sect1><sect2><para>
6217 #: ../en/ch06-collab.xml:389
6218 msgid ""
6219 "Typically, the backers of the shared-push model use tools that actively "
6220 "enforce this approach. If you're using a centralised revision control tool "
6221 "such as Subversion, there's no way to make a choice over which model you'll "
6222 "use: the tool gives you shared-push, and if you want to do anything else, "
6223 "you'll have to roll your own approach on top (such as applying a patch by "
6224 "hand)."
6225 msgstr ""
6227 #. type: Content of: <book><chapter><sect1><sect2><para>
6228 #: ../en/ch06-collab.xml:397
6229 msgid ""
6230 "A good distributed revision control tool, such as Mercurial, will support "
6231 "both models. You and your collaborators can then structure how you work "
6232 "together based on your own needs and preferences, not on what contortions "
6233 "your tools force you into."
6234 msgstr ""
6236 #. type: Content of: <book><chapter><sect1><sect2><title>
6237 #: ../en/ch06-collab.xml:405
6238 msgid "Where collaboration meets branch management"
6239 msgstr "协作与分支管理"
6241 #. type: Content of: <book><chapter><sect1><sect2><para>
6242 #: ../en/ch06-collab.xml:407
6243 msgid ""
6244 "Once you and your team set up some shared repositories and start propagating "
6245 "changes back and forth between local and shared repos, you begin to face a "
6246 "related, but slightly different challenge: that of managing the multiple "
6247 "directions in which your team may be moving at once. Even though this "
6248 "subject is intimately related to how your team collaborates, it's dense "
6249 "enough to merit treatment of its own, in chapter <xref linkend=\"chap.branch"
6250 "\"/>."
6251 msgstr ""
6253 #. type: Content of: <book><chapter><sect1><title>
6254 #: ../en/ch06-collab.xml:419
6255 msgid "The technical side of sharing"
6256 msgstr "共享的技术因素"
6258 #. type: Content of: <book><chapter><sect1><para>
6259 #: ../en/ch06-collab.xml:421
6260 msgid ""
6261 "The remainder of this chapter is devoted to the question of serving data to "
6262 "your collaborators."
6263 msgstr ""
6265 #. type: Content of: <book><chapter><sect1><title>
6266 #: ../en/ch06-collab.xml:426
6267 msgid "Informal sharing with <command role=\"hg-cmd\">hg serve</command>"
6268 msgstr "使用 <command role=\"hg-cmd\">hg serve</command> 进行非正式共享"
6270 #. type: Content of: <book><chapter><sect1><para>
6271 #: ../en/ch06-collab.xml:429
6272 msgid ""
6273 "Mercurial's <command role=\"hg-cmd\">hg serve</command> command is "
6274 "wonderfully suited to small, tight-knit, and fast-paced group environments. "
6275 "It also provides a great way to get a feel for using Mercurial commands over "
6276 "a network."
6277 msgstr ""
6279 #. type: Content of: <book><chapter><sect1><para>
6280 #: ../en/ch06-collab.xml:434
6281 msgid ""
6282 "Run <command role=\"hg-cmd\">hg serve</command> inside a repository, and in "
6283 "under a second it will bring up a specialised HTTP server; this will accept "
6284 "connections from any client, and serve up data for that repository until you "
6285 "terminate it. Anyone who knows the URL of the server you just started, and "
6286 "can talk to your computer over the network, can then use a web browser or "
6287 "Mercurial to read data from that repository. A URL for a <command role=\"hg-"
6288 "cmd\">hg serve</command> instance running on a laptop is likely to look "
6289 "something like <literal>http://my-laptop.local:8000/</literal>."
6290 msgstr ""
6292 #. type: Content of: <book><chapter><sect1><para>
6293 #: ../en/ch06-collab.xml:445
6294 msgid ""
6295 "The <command role=\"hg-cmd\">hg serve</command> command is <emphasis>not</"
6296 "emphasis> a general-purpose web server. It can do only two things:"
6297 msgstr ""
6299 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
6300 #: ../en/ch06-collab.xml:449
6301 msgid ""
6302 "Allow people to browse the history of the repository it's serving, from their "
6303 "normal web browsers."
6304 msgstr ""
6306 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
6307 #: ../en/ch06-collab.xml:453
6308 msgid ""
6309 "Speak Mercurial's wire protocol, so that people can <command role=\"hg-cmd"
6310 "\">hg clone</command> or <command role=\"hg-cmd\">hg pull</command> changes "
6311 "from that repository."
6312 msgstr ""
6314 #. type: Content of: <book><chapter><sect1><para>
6315 #: ../en/ch06-collab.xml:458
6316 msgid ""
6317 "In particular, <command role=\"hg-cmd\">hg serve</command> won't allow remote "
6318 "users to <emphasis>modify</emphasis> your repository. It's intended for read-"
6319 "only use."
6320 msgstr ""
6322 #. type: Content of: <book><chapter><sect1><para>
6323 #: ../en/ch06-collab.xml:462
6324 msgid ""
6325 "If you're getting started with Mercurial, there's nothing to prevent you from "
6326 "using <command role=\"hg-cmd\">hg serve</command> to serve up a repository on "
6327 "your own computer, then use commands like <command role=\"hg-cmd\">hg clone</"
6328 "command>, <command role=\"hg-cmd\">hg incoming</command>, and so on to talk "
6329 "to that server as if the repository was hosted remotely. This can help you to "
6330 "quickly get acquainted with using commands on network-hosted repositories."
6331 msgstr ""
6333 #. type: Content of: <book><chapter><sect1><sect2><title>
6334 #: ../en/ch06-collab.xml:472
6335 msgid "A few things to keep in mind"
6336 msgstr "要牢记的几件事"
6338 #. type: Content of: <book><chapter><sect1><sect2><para>
6339 #: ../en/ch06-collab.xml:474
6340 msgid ""
6341 "Because it provides unauthenticated read access to all clients, you should "
6342 "only use <command role=\"hg-cmd\">hg serve</command> in an environment where "
6343 "you either don't care, or have complete control over, who can access your "
6344 "network and pull data from your repository."
6345 msgstr ""
6347 #. type: Content of: <book><chapter><sect1><sect2><para>
6348 #: ../en/ch06-collab.xml:480
6349 msgid ""
6350 "The <command role=\"hg-cmd\">hg serve</command> command knows nothing about "
6351 "any firewall software you might have installed on your system or network. It "
6352 "cannot detect or control your firewall software. If other people are unable "
6353 "to talk to a running <command role=\"hg-cmd\">hg serve</command> instance, "
6354 "the second thing you should do (<emphasis>after</emphasis> you make sure that "
6355 "they're using the correct URL) is check your firewall configuration."
6356 msgstr ""
6358 #. type: Content of: <book><chapter><sect1><sect2><para>
6359 #: ../en/ch06-collab.xml:489
6360 msgid ""
6361 "By default, <command role=\"hg-cmd\">hg serve</command> listens for incoming "
6362 "connections on port 8000. If another process is already listening on the "
6363 "port you want to use, you can specify a different port to listen on using the "
6364 "<option role=\"hg-opt-serve\">-p</option> option."
6365 msgstr ""
6367 #. type: Content of: <book><chapter><sect1><sect2><para>
6368 #: ../en/ch06-collab.xml:495
6369 msgid ""
6370 "Normally, when <command role=\"hg-cmd\">hg serve</command> starts, it prints "
6371 "no output, which can be a bit unnerving. If you'd like to confirm that it is "
6372 "indeed running correctly, and find out what URL you should send to your "
6373 "collaborators, start it with the <option role=\"hg-opt-global\">-v</option> "
6374 "option."
6375 msgstr ""
6377 #. type: Content of: <book><chapter><sect1><title>
6378 #: ../en/ch06-collab.xml:505
6379 msgid "Using the Secure Shell (ssh) protocol"
6380 msgstr "使用 ssh 协议"
6382 #. type: Content of: <book><chapter><sect1><para>
6383 #: ../en/ch06-collab.xml:507
6384 msgid ""
6385 "You can pull and push changes securely over a network connection using the "
6386 "Secure Shell (<literal>ssh</literal>) protocol. To use this successfully, "
6387 "you may have to do a little bit of configuration on the client or server "
6388 "sides."
6389 msgstr ""
6391 #. type: Content of: <book><chapter><sect1><para>
6392 #: ../en/ch06-collab.xml:512
6393 msgid ""
6394 "If you're not familiar with ssh, it's a network protocol that lets you "
6395 "securely communicate with another computer. To use it with Mercurial, you'll "
6396 "be setting up one or more user accounts on a server so that remote users can "
6397 "log in and execute commands."
6398 msgstr ""
6400 #. type: Content of: <book><chapter><sect1><para>
6401 #: ../en/ch06-collab.xml:518
6402 msgid ""
6403 "(If you <emphasis>are</emphasis> familiar with ssh, you'll probably find some "
6404 "of the material that follows to be elementary in nature.)"
6405 msgstr ""
6407 #. type: Content of: <book><chapter><sect1><sect2><title>
6408 #: ../en/ch06-collab.xml:523
6409 msgid "How to read and write ssh URLs"
6410 msgstr "如何读写 ssh 路径"
6412 #. type: Content of: <book><chapter><sect1><sect2><para>
6413 #: ../en/ch06-collab.xml:525
6414 msgid "An ssh URL tends to look like this:"
6415 msgstr ""
6417 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
6418 #: ../en/ch06-collab.xml:528
6419 msgid ""
6420 "The <quote><literal>ssh://</literal></quote> part tells Mercurial to use the "
6421 "ssh protocol."
6422 msgstr ""
6424 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
6425 #: ../en/ch06-collab.xml:531
6426 msgid ""
6427 "The <quote><literal>bos@</literal></quote> component indicates what username "
6428 "to log into the server as. You can leave this out if the remote username is "
6429 "the same as your local username."
6430 msgstr ""
6432 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
6433 #: ../en/ch06-collab.xml:536
6434 msgid ""
6435 "The <quote><literal>hg.serpentine.com</literal></quote> gives the hostname of "
6436 "the server to log into."
6437 msgstr ""
6439 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
6440 #: ../en/ch06-collab.xml:540
6441 msgid ""
6442 "The <quote>:22</quote> identifies the port number to connect to the server "
6443 "on. The default port is 22, so you only need to specify this part if you're "
6444 "<emphasis>not</emphasis> using port 22."
6445 msgstr ""
6447 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
6448 #: ../en/ch06-collab.xml:545
6449 msgid ""
6450 "The remainder of the URL is the local path to the repository on the server."
6451 msgstr ""
6453 #. type: Content of: <book><chapter><sect1><sect2><para>
6454 #: ../en/ch06-collab.xml:549
6455 msgid ""
6456 "There's plenty of scope for confusion with the path component of ssh URLs, as "
6457 "there is no standard way for tools to interpret it. Some programs behave "
6458 "differently than others when dealing with these paths. This isn't an ideal "
6459 "situation, but it's unlikely to change. Please read the following paragraphs "
6460 "carefully."
6461 msgstr ""
6463 #. type: Content of: <book><chapter><sect1><sect2><para>
6464 #: ../en/ch06-collab.xml:556
6465 msgid ""
6466 "Mercurial treats the path to a repository on the server as relative to the "
6467 "remote user's home directory. For example, if user <literal>foo</literal> on "
6468 "the server has a home directory of <filename class=\"directory\">/home/foo</"
6469 "filename>, then an ssh URL that contains a path component of <filename class="
6470 "\"directory\">bar</filename> <emphasis>really</emphasis> refers to the "
6471 "directory <filename class=\"directory\">/home/foo/bar</filename>."
6472 msgstr ""
6474 #. type: Content of: <book><chapter><sect1><sect2><para>
6475 #: ../en/ch06-collab.xml:565
6476 msgid ""
6477 "If you want to specify a path relative to another user's home directory, you "
6478 "can use a path that starts with a tilde character followed by the user's name "
6479 "(let's call them <literal>otheruser</literal>), like this."
6480 msgstr ""
6482 #. type: Content of: <book><chapter><sect1><sect2><para>
6483 #: ../en/ch06-collab.xml:571
6484 msgid ""
6485 "And if you really want to specify an <emphasis>absolute</emphasis> path on "
6486 "the server, begin the path component with two slashes, as in this example."
6487 msgstr ""
6489 #. type: Content of: <book><chapter><sect1><sect2><title>
6490 #: ../en/ch06-collab.xml:578
6491 msgid "Finding an ssh client for your system"
6492 msgstr "为你的系统寻找 ssh 客户端"
6494 #. type: Content of: <book><chapter><sect1><sect2><para>
6495 #: ../en/ch06-collab.xml:580
6496 msgid ""
6497 "Almost every Unix-like system comes with OpenSSH preinstalled. If you're "
6498 "using such a system, run <literal>which ssh</literal> to find out if the "
6499 "<command>ssh</command> command is installed (it's usually in <filename class="
6500 "\"directory\">/usr/bin</filename>). In the unlikely event that it isn't "
6501 "present, take a look at your system documentation to figure out how to "
6502 "install it."
6503 msgstr ""
6505 #. type: Content of: <book><chapter><sect1><sect2><para>
6506 #: ../en/ch06-collab.xml:588
6507 msgid ""
6508 "On Windows, you'll first need to download a suitable ssh client. There are "
6509 "two alternatives."
6510 msgstr ""
6512 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6513 #: ../en/ch06-collab.xml:591
6514 msgid ""
6515 "Simon Tatham's excellent PuTTY package <citation>web:putty</citation> "
6516 "provides a complete suite of ssh client commands."
6517 msgstr ""
6519 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6520 #: ../en/ch06-collab.xml:595
6521 msgid ""
6522 "If you have a high tolerance for pain, you can use the Cygwin port of OpenSSH."
6523 msgstr ""
6525 #. type: Content of: <book><chapter><sect1><sect2><para>
6526 #: ../en/ch06-collab.xml:598
6527 msgid ""
6528 "In either case, you'll need to edit your \\hgini\\ file to tell Mercurial "
6529 "where to find the actual client command. For example, if you're using PuTTY, "
6530 "you'll need to use the <command>plink</command> command as a command-line ssh "
6531 "client."
6532 msgstr ""
6534 #. type: Content of: <book><chapter><sect1><sect2><note><para>
6535 #: ../en/ch06-collab.xml:607
6536 msgid ""
6537 "The path to <command>plink</command> shouldn't contain any whitespace "
6538 "characters, or Mercurial may not be able to run it correctly (so putting it "
6539 "in <filename class=\"directory\">C:\\\\Program Files</filename> is probably "
6540 "not a good idea)."
6541 msgstr ""
6543 #. type: Content of: <book><chapter><sect1><sect2><title>
6544 #: ../en/ch06-collab.xml:616
6545 msgid "Generating a key pair"
6546 msgstr "产生密钥对"
6548 #. type: Content of: <book><chapter><sect1><sect2><para>
6549 #: ../en/ch06-collab.xml:618
6550 msgid ""
6551 "To avoid the need to repetitively type a password every time you need to use "
6552 "your ssh client, I recommend generating a key pair. On a Unix-like system, "
6553 "the <command>ssh-keygen</command> command will do the trick. On Windows, if "
6554 "you're using PuTTY, the <command>puttygen</command> command is what you'll "
6555 "need."
6556 msgstr ""
6558 #. type: Content of: <book><chapter><sect1><sect2><para>
6559 #: ../en/ch06-collab.xml:626
6560 msgid ""
6561 "When you generate a key pair, it's usually <emphasis>highly</emphasis> "
6562 "advisable to protect it with a passphrase. (The only time that you might not "
6563 "want to do this is when you're using the ssh protocol for automated tasks on "
6564 "a secure network.)"
6565 msgstr ""
6567 #. type: Content of: <book><chapter><sect1><sect2><para>
6568 #: ../en/ch06-collab.xml:632
6569 msgid ""
6570 "Simply generating a key pair isn't enough, however. You'll need to add the "
6571 "public key to the set of authorised keys for whatever user you're logging in "
6572 "remotely as. For servers using OpenSSH (the vast majority), this will mean "
6573 "adding the public key to a list in a file called <filename role=\"special"
6574 "\">authorized_keys</filename> in their <filename role=\"special\" class="
6575 "\"directory\">.ssh</filename> directory."
6576 msgstr ""
6578 #. type: Content of: <book><chapter><sect1><sect2><para>
6579 #: ../en/ch06-collab.xml:641
6580 msgid ""
6581 "On a Unix-like system, your public key will have a <filename>.pub</filename> "
6582 "extension. If you're using <command>puttygen</command> on Windows, you can "
6583 "save the public key to a file of your choosing, or paste it from the window "
6584 "it's displayed in straight into the <filename role=\"special"
6585 "\">authorized_keys</filename> file."
6586 msgstr ""
6588 #. type: Content of: <book><chapter><sect1><sect2><title>
6589 #: ../en/ch06-collab.xml:650
6590 msgid "Using an authentication agent"
6591 msgstr "使用认证代理"
6593 #. type: Content of: <book><chapter><sect1><sect2><para>
6594 #: ../en/ch06-collab.xml:652
6595 msgid ""
6596 "An authentication agent is a daemon that stores passphrases in memory (so it "
6597 "will forget passphrases if you log out and log back in again). An ssh client "
6598 "will notice if it's running, and query it for a passphrase. If there's no "
6599 "authentication agent running, or the agent doesn't store the necessary "
6600 "passphrase, you'll have to type your passphrase every time Mercurial tries to "
6601 "communicate with a server on your behalf (e.g. whenever you pull or push "
6602 "changes)."
6603 msgstr ""
6605 #. type: Content of: <book><chapter><sect1><sect2><para>
6606 #: ../en/ch06-collab.xml:661
6607 msgid ""
6608 "The downside of storing passphrases in an agent is that it's possible for a "
6609 "well-prepared attacker to recover the plain text of your passphrases, in some "
6610 "cases even if your system has been power-cycled. You should make your own "
6611 "judgment as to whether this is an acceptable risk. It certainly saves a lot "
6612 "of repeated typing."
6613 msgstr ""
6615 #. type: Content of: <book><chapter><sect1><sect2><para>
6616 #: ../en/ch06-collab.xml:668
6617 msgid ""
6618 "On Unix-like systems, the agent is called <command>ssh-agent</command>, and "
6619 "it's often run automatically for you when you log in. You'll need to use the "
6620 "<command>ssh-add</command> command to add passphrases to the agent's store. "
6621 "On Windows, if you're using PuTTY, the <command>pageant</command> command "
6622 "acts as the agent. It adds an icon to your system tray that will let you "
6623 "manage stored passphrases."
6624 msgstr ""
6626 #. type: Content of: <book><chapter><sect1><sect2><title>
6627 #: ../en/ch06-collab.xml:679
6628 msgid "Configuring the server side properly"
6629 msgstr "正确配置服务器端"
6631 #. type: Content of: <book><chapter><sect1><sect2><para>
6632 #: ../en/ch06-collab.xml:681
6633 msgid ""
6634 "Because ssh can be fiddly to set up if you're new to it, there's a variety of "
6635 "things that can go wrong. Add Mercurial on top, and there's plenty more "
6636 "scope for head-scratching. Most of these potential problems occur on the "
6637 "server side, not the client side. The good news is that once you've gotten a "
6638 "configuration working, it will usually continue to work indefinitely."
6639 msgstr ""
6641 #. type: Content of: <book><chapter><sect1><sect2><para>
6642 #: ../en/ch06-collab.xml:689
6643 msgid ""
6644 "Before you try using Mercurial to talk to an ssh server, it's best to make "
6645 "sure that you can use the normal <command>ssh</command> or <command>putty</"
6646 "command> command to talk to the server first. If you run into problems with "
6647 "using these commands directly, Mercurial surely won't work. Worse, it will "
6648 "obscure the underlying problem. Any time you want to debug ssh-related "
6649 "Mercurial problems, you should drop back to making sure that plain ssh client "
6650 "commands work first, <emphasis>before</emphasis> you worry about whether "
6651 "there's a problem with Mercurial."
6652 msgstr ""
6654 #. type: Content of: <book><chapter><sect1><sect2><para>
6655 #: ../en/ch06-collab.xml:700
6656 msgid ""
6657 "The first thing to be sure of on the server side is that you can actually log "
6658 "in from another machine at all. If you can't use <command>ssh</command> or "
6659 "<command>putty</command> to log in, the error message you get may give you a "
6660 "few hints as to what's wrong. The most common problems are as follows."
6661 msgstr ""
6663 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6664 #: ../en/ch06-collab.xml:707
6665 msgid ""
6666 "If you get a <quote>connection refused</quote> error, either there isn't an "
6667 "SSH daemon running on the server at all, or it's inaccessible due to firewall "
6668 "configuration."
6669 msgstr ""
6671 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6672 #: ../en/ch06-collab.xml:712
6673 msgid ""
6674 "If you get a <quote>no route to host</quote> error, you either have an "
6675 "incorrect address for the server or a seriously locked down firewall that "
6676 "won't admit its existence at all."
6677 msgstr ""
6679 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6680 #: ../en/ch06-collab.xml:717
6681 msgid ""
6682 "If you get a <quote>permission denied</quote> error, you may have mistyped "
6683 "the username on the server, or you could have mistyped your key's passphrase "
6684 "or the remote user's password."
6685 msgstr ""
6687 #. type: Content of: <book><chapter><sect1><sect2><para>
6688 #: ../en/ch06-collab.xml:722
6689 msgid ""
6690 "In summary, if you're having trouble talking to the server's ssh daemon, "
6691 "first make sure that one is running at all. On many systems it will be "
6692 "installed, but disabled, by default. Once you're done with this step, you "
6693 "should then check that the server's firewall is configured to allow incoming "
6694 "connections on the port the ssh daemon is listening on (usually 22). Don't "
6695 "worry about more exotic possibilities for misconfiguration until you've "
6696 "checked these two first."
6697 msgstr ""
6699 #. type: Content of: <book><chapter><sect1><sect2><para>
6700 #: ../en/ch06-collab.xml:732
6701 msgid ""
6702 "If you're using an authentication agent on the client side to store "
6703 "passphrases for your keys, you ought to be able to log into the server "
6704 "without being prompted for a passphrase or a password. If you're prompted "
6705 "for a passphrase, there are a few possible culprits."
6706 msgstr ""
6708 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6709 #: ../en/ch06-collab.xml:738
6710 msgid ""
6711 "You might have forgotten to use <command>ssh-add</command> or "
6712 "<command>pageant</command> to store the passphrase."
6713 msgstr ""
6715 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6716 #: ../en/ch06-collab.xml:742
6717 msgid "You might have stored the passphrase for the wrong key."
6718 msgstr ""
6720 #. type: Content of: <book><chapter><sect1><sect2><para>
6721 #: ../en/ch06-collab.xml:745
6722 msgid ""
6723 "If you're being prompted for the remote user's password, there are another "
6724 "few possible problems to check."
6725 msgstr ""
6727 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6728 #: ../en/ch06-collab.xml:748
6729 msgid ""
6730 "Either the user's home directory or their <filename role=\"special\" class="
6731 "\"directory\">.ssh</filename> directory might have excessively liberal "
6732 "permissions. As a result, the ssh daemon will not trust or read their "
6733 "<filename role=\"special\">authorized_keys</filename> file. For example, a "
6734 "group-writable home or <filename role=\"special\" class=\"directory\">.ssh</"
6735 "filename> directory will often cause this symptom."
6736 msgstr ""
6738 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6739 #: ../en/ch06-collab.xml:757
6740 msgid ""
6741 "The user's <filename role=\"special\">authorized_keys</filename> file may "
6742 "have a problem. If anyone other than the user owns or can write to that file, "
6743 "the ssh daemon will not trust or read it."
6744 msgstr ""
6746 #. type: Content of: <book><chapter><sect1><sect2><para>
6747 #: ../en/ch06-collab.xml:764
6748 msgid ""
6749 "In the ideal world, you should be able to run the following command "
6750 "successfully, and it should print exactly one line of output, the current "
6751 "date and time."
6752 msgstr ""
6754 #. type: Content of: <book><chapter><sect1><sect2><para>
6755 #: ../en/ch06-collab.xml:769
6756 msgid ""
6757 "If, on your server, you have login scripts that print banners or other junk "
6758 "even when running non-interactive commands like this, you should fix them "
6759 "before you continue, so that they only print output if they're run "
6760 "interactively. Otherwise these banners will at least clutter up Mercurial's "
6761 "output. Worse, they could potentially cause problems with running Mercurial "
6762 "commands remotely. Mercurial makes tries to detect and ignore banners in non-"
6763 "interactive <command>ssh</command> sessions, but it is not foolproof. (If "
6764 "you're editing your login scripts on your server, the usual way to see if a "
6765 "login script is running in an interactive shell is to check the return code "
6766 "from the command <literal>tty -s</literal>.)"
6767 msgstr ""
6769 #. type: Content of: <book><chapter><sect1><sect2><para>
6770 #: ../en/ch06-collab.xml:783
6771 msgid ""
6772 "Once you've verified that plain old ssh is working with your server, the next "
6773 "step is to ensure that Mercurial runs on the server. The following command "
6774 "should run successfully:"
6775 msgstr ""
6777 #. type: Content of: <book><chapter><sect1><sect2><para>
6778 #: ../en/ch06-collab.xml:788
6779 msgid ""
6780 "If you see an error message instead of normal <command role=\"hg-cmd\">hg "
6781 "version</command> output, this is usually because you haven't installed "
6782 "Mercurial to <filename class=\"directory\">/usr/bin</filename>. Don't worry "
6783 "if this is the case; you don't need to do that. But you should check for a "
6784 "few possible problems."
6785 msgstr ""
6787 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6788 #: ../en/ch06-collab.xml:795
6789 msgid ""
6790 "Is Mercurial really installed on the server at all? I know this sounds "
6791 "trivial, but it's worth checking!"
6792 msgstr ""
6794 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6795 #: ../en/ch06-collab.xml:799
6796 msgid ""
6797 "Maybe your shell's search path (usually set via the <envar>PATH</envar> "
6798 "environment variable) is simply misconfigured."
6799 msgstr ""
6801 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6802 #: ../en/ch06-collab.xml:803
6803 msgid ""
6804 "Perhaps your <envar>PATH</envar> environment variable is only being set to "
6805 "point to the location of the <command>hg</command> executable if the login "
6806 "session is interactive. This can happen if you're setting the path in the "
6807 "wrong shell login script. See your shell's documentation for details."
6808 msgstr ""
6810 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
6811 #: ../en/ch06-collab.xml:810
6812 msgid ""
6813 "The <envar>PYTHONPATH</envar> environment variable may need to contain the "
6814 "path to the Mercurial Python modules. It might not be set at all; it could "
6815 "be incorrect; or it may be set only if the login is interactive."
6816 msgstr ""
6818 #. type: Content of: <book><chapter><sect1><sect2><para>
6819 #: ../en/ch06-collab.xml:817
6820 msgid ""
6821 "If you can run <command role=\"hg-cmd\">hg version</command> over an ssh "
6822 "connection, well done! You've got the server and client sorted out. You "
6823 "should now be able to use Mercurial to access repositories hosted by that "
6824 "username on that server. If you run into problems with Mercurial and ssh at "
6825 "this point, try using the <option role=\"hg-opt-global\">--debug</option> "
6826 "option to get a clearer picture of what's going on."
6827 msgstr ""
6829 #. type: Content of: <book><chapter><sect1><sect2><title>
6830 #: ../en/ch06-collab.xml:827
6831 msgid "Using compression with ssh"
6832 msgstr "通过 ssh 使用压缩"
6834 #. type: Content of: <book><chapter><sect1><sect2><para>
6835 #: ../en/ch06-collab.xml:829
6836 msgid ""
6837 "Mercurial does not compress data when it uses the ssh protocol, because the "
6838 "ssh protocol can transparently compress data. However, the default behaviour "
6839 "of ssh clients is <emphasis>not</emphasis> to request compression."
6840 msgstr ""
6842 #. type: Content of: <book><chapter><sect1><sect2><para>
6843 #: ../en/ch06-collab.xml:834
6844 msgid ""
6845 "Over any network other than a fast LAN (even a wireless network), using "
6846 "compression is likely to significantly speed up Mercurial's network "
6847 "operations. For example, over a WAN, someone measured compression as "
6848 "reducing the amount of time required to clone a particularly large repository "
6849 "from 51 minutes to 17 minutes."
6850 msgstr ""
6852 #. type: Content of: <book><chapter><sect1><sect2><para>
6853 #: ../en/ch06-collab.xml:841
6854 msgid ""
6855 "Both <command>ssh</command> and <command>plink</command> accept a <option "
6856 "role=\"cmd-opt-ssh\">-C</option> option which turns on compression. You can "
6857 "easily edit your <filename role=\"special\"> /.hgrc</filename>\\ to enable "
6858 "compression for all of Mercurial's uses of the ssh protocol."
6859 msgstr ""
6861 #. type: Content of: <book><chapter><sect1><sect2><para>
6862 #: ../en/ch06-collab.xml:848
6863 msgid ""
6864 "If you use <command>ssh</command>, you can configure it to always use "
6865 "compression when talking to your server. To do this, edit your <filename "
6866 "role=\"special\">.ssh/config</filename> file (which may not yet exist), as "
6867 "follows."
6868 msgstr ""
6870 #. type: Content of: <book><chapter><sect1><sect2><para>
6871 #: ../en/ch06-collab.xml:855
6872 msgid ""
6873 "This defines an alias, <literal>hg</literal>. When you use it on the "
6874 "<command>ssh</command> command line or in a Mercurial <literal>ssh</literal>-"
6875 "protocol URL, it will cause <command>ssh</command> to connect to <literal>hg."
6876 "example.com</literal> and use compression. This gives you both a shorter "
6877 "name to type and compression, each of which is a good thing in its own right."
6878 msgstr ""
6880 #. type: Content of: <book><chapter><sect1><title>
6881 #: ../en/ch06-collab.xml:866
6882 msgid "Serving over HTTP using CGI"
6883 msgstr "使用 CGI 通过 HTTP 提供服务"
6885 #. type: Content of: <book><chapter><sect1><para>
6886 #: ../en/ch06-collab.xml:868
6887 msgid ""
6888 "Depending on how ambitious you are, configuring Mercurial's CGI interface can "
6889 "take anything from a few moments to several hours."
6890 msgstr ""
6892 #. type: Content of: <book><chapter><sect1><para>
6893 #: ../en/ch06-collab.xml:872
6894 msgid ""
6895 "We'll begin with the simplest of examples, and work our way towards a more "
6896 "complex configuration. Even for the most basic case, you're almost certainly "
6897 "going to need to read and modify your web server's configuration."
6898 msgstr ""
6900 #. type: Content of: <book><chapter><sect1><note><para>
6901 #: ../en/ch06-collab.xml:878
6902 msgid ""
6903 "Configuring a web server is a complex, fiddly, and highly system-dependent "
6904 "activity. I can't possibly give you instructions that will cover anything "
6905 "like all of the cases you will encounter. Please use your discretion and "
6906 "judgment in following the sections below. Be prepared to make plenty of "
6907 "mistakes, and to spend a lot of time reading your server's error logs."
6908 msgstr ""
6910 #. type: Content of: <book><chapter><sect1><sect2><title>
6911 #: ../en/ch06-collab.xml:888
6912 msgid "Web server configuration checklist"
6913 msgstr "Web 服务器配置检查表"
6915 #. type: Content of: <book><chapter><sect1><sect2><para>
6916 #: ../en/ch06-collab.xml:890
6917 msgid ""
6918 "Before you continue, do take a few moments to check a few aspects of your "
6919 "system's setup."
6920 msgstr ""
6922 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
6923 #: ../en/ch06-collab.xml:894
6924 msgid ""
6925 "Do you have a web server installed at all? Mac OS X ships with Apache, but "
6926 "many other systems may not have a web server installed."
6927 msgstr ""
6929 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
6930 #: ../en/ch06-collab.xml:898
6931 msgid ""
6932 "If you have a web server installed, is it actually running? On most systems, "
6933 "even if one is present, it will be disabled by default."
6934 msgstr ""
6936 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
6937 #: ../en/ch06-collab.xml:902
6938 msgid ""
6939 "Is your server configured to allow you to run CGI programs in the directory "
6940 "where you plan to do so? Most servers default to explicitly disabling the "
6941 "ability to run CGI programs."
6942 msgstr ""
6944 #. type: Content of: <book><chapter><sect1><sect2><para>
6945 #: ../en/ch06-collab.xml:908
6946 msgid ""
6947 "If you don't have a web server installed, and don't have substantial "
6948 "experience configuring Apache, you should consider using the "
6949 "<literal>lighttpd</literal> web server instead of Apache. Apache has a well-"
6950 "deserved reputation for baroque and confusing configuration. While "
6951 "<literal>lighttpd</literal> is less capable in some ways than Apache, most of "
6952 "these capabilities are not relevant to serving Mercurial repositories. And "
6953 "<literal>lighttpd</literal> is undeniably <emphasis>much</emphasis> easier to "
6954 "get started with than Apache."
6955 msgstr ""
6957 #. type: Content of: <book><chapter><sect1><sect2><title>
6958 #: ../en/ch06-collab.xml:921
6959 msgid "Basic CGI configuration"
6960 msgstr "基本 CGI 配置"
6962 #. type: Content of: <book><chapter><sect1><sect2><para>
6963 #: ../en/ch06-collab.xml:923
6964 msgid ""
6965 "On Unix-like systems, it's common for users to have a subdirectory named "
6966 "something like <filename class=\"directory\">public_html</filename> in their "
6967 "home directory, from which they can serve up web pages. A file named "
6968 "<filename>foo</filename> in this directory will be accessible at a URL of the "
6969 "form <literal>http://www.example.com/\\ {</literal>username/foo}."
6970 msgstr ""
6972 #. type: Content of: <book><chapter><sect1><sect2><para>
6973 #: ../en/ch06-collab.xml:932
6974 msgid ""
6975 "To get started, find the <filename role=\"special\">hgweb.cgi</filename> "
6976 "script that should be present in your Mercurial installation. If you can't "
6977 "quickly find a local copy on your system, simply download one from the master "
6978 "Mercurial repository at <ulink url=\"http://www.selenic.com/repo/hg/raw-file/"
6979 "tip/hgweb.cgi\">http://www.selenic.com/repo/hg/raw-file/tip/hgweb.cgi</ulink>."
6980 msgstr ""
6982 #. type: Content of: <book><chapter><sect1><sect2><para>
6983 #: ../en/ch06-collab.xml:939 ../en/ch06-collab.xml:1112
6984 msgid ""
6985 "You'll need to copy this script into your <filename class=\"directory"
6986 "\">public_html</filename> directory, and ensure that it's executable."
6987 msgstr ""
6989 #. type: Content of: <book><chapter><sect1><sect2><para>
6990 #: ../en/ch06-collab.xml:944
6991 msgid ""
6992 "The <literal>755</literal> argument to <command>chmod</command> is a little "
6993 "more general than just making the script executable: it ensures that the "
6994 "script is executable by anyone, and that <quote>group</quote> and "
6995 "<quote>other</quote> write permissions are <emphasis>not</emphasis> set. If "
6996 "you were to leave those write permissions enabled, Apache's <literal>suexec</"
6997 "literal> subsystem would likely refuse to execute the script. In fact, "
6998 "<literal>suexec</literal> also insists that the <emphasis>directory</"
6999 "emphasis> in which the script resides must not be writable by others."
7000 msgstr ""
7002 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
7003 #: ../en/ch06-collab.xml:958
7004 msgid "What could <emphasis>possibly</emphasis> go wrong?"
7005 msgstr "什么<emphasis>可能</emphasis>会出错?"
7007 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7008 #: ../en/ch06-collab.xml:961
7009 msgid ""
7010 "Once you've copied the CGI script into place, go into a web browser, and try "
7011 "to open the URL <ulink url=\"http://myhostname/ myuser/hgweb.cgi\">http://"
7012 "myhostname/ myuser/hgweb.cgi</ulink>, <emphasis>but</emphasis> brace yourself "
7013 "for instant failure. There's a high probability that trying to visit this "
7014 "URL will fail, and there are many possible reasons for this. In fact, you're "
7015 "likely to stumble over almost every one of the possible errors below, so "
7016 "please read carefully. The following are all of the problems I ran into on a "
7017 "system running Fedora 7, with a fresh installation of Apache, and a user "
7018 "account that I created specially to perform this exercise."
7019 msgstr ""
7021 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7022 #: ../en/ch06-collab.xml:975
7023 msgid ""
7024 "Your web server may have per-user directories disabled. If you're using "
7025 "Apache, search your config file for a <literal>UserDir</literal> directive. "
7026 "If there's none present, per-user directories will be disabled. If one "
7027 "exists, but its value is <literal>disabled</literal>, then per-user "
7028 "directories will be disabled. Otherwise, the string after <literal>UserDir</"
7029 "literal> gives the name of the subdirectory that Apache will look in under "
7030 "your home directory, for example <filename class=\"directory\">public_html</"
7031 "filename>."
7032 msgstr ""
7034 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7035 #: ../en/ch06-collab.xml:986
7036 msgid ""
7037 "Your file access permissions may be too restrictive. The web server must be "
7038 "able to traverse your home directory and directories under your <filename "
7039 "class=\"directory\">public_html</filename> directory, and read files under "
7040 "the latter too. Here's a quick recipe to help you to make your permissions "
7041 "more appropriate."
7042 msgstr ""
7044 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7045 #: ../en/ch06-collab.xml:996
7046 msgid ""
7047 "The other possibility with permissions is that you might get a completely "
7048 "empty window when you try to load the script. In this case, it's likely that "
7049 "your access permissions are <emphasis>too permissive</emphasis>. Apache's "
7050 "<literal>suexec</literal> subsystem won't execute a script that's group- or "
7051 "world-writable, for example."
7052 msgstr ""
7054 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7055 #: ../en/ch06-collab.xml:1003
7056 msgid ""
7057 "Your web server may be configured to disallow execution of CGI programs in "
7058 "your per-user web directory. Here's Apache's default per-user configuration "
7059 "from my Fedora system."
7060 msgstr ""
7062 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7063 #: ../en/ch06-collab.xml:1014
7064 msgid ""
7065 "If you find a similar-looking <literal>Directory</literal> group in your "
7066 "Apache configuration, the directive to look at inside it is <literal>Options</"
7067 "literal>. Add <literal>ExecCGI</literal> to the end of this list if it's "
7068 "missing, and restart the web server."
7069 msgstr ""
7071 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7072 #: ../en/ch06-collab.xml:1021
7073 msgid ""
7074 "If you find that Apache serves you the text of the CGI script instead of "
7075 "executing it, you may need to either uncomment (if already present) or add a "
7076 "directive like this."
7077 msgstr ""
7079 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7080 #: ../en/ch06-collab.xml:1027
7081 msgid ""
7082 "The next possibility is that you might be served with a colourful Python "
7083 "backtrace claiming that it can't import a <literal>mercurial</literal>-"
7084 "related module. This is actually progress! The server is now capable of "
7085 "executing your CGI script. This error is only likely to occur if you're "
7086 "running a private installation of Mercurial, instead of a system-wide "
7087 "version. Remember that the web server runs the CGI program without any of "
7088 "the environment variables that you take for granted in an interactive "
7089 "session. If this error happens to you, edit your copy of <filename role="
7090 "\"special\">hgweb.cgi</filename> and follow the directions inside it to "
7091 "correctly set your <envar>PYTHONPATH</envar> environment variable."
7092 msgstr ""
7094 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7095 #: ../en/ch06-collab.xml:1041
7096 msgid ""
7097 "Finally, you are <emphasis>certain</emphasis> to by served with another "
7098 "colourful Python backtrace: this one will complain that it can't find "
7099 "<filename class=\"directory\">/path/to/repository</filename>. Edit your "
7100 "<filename role=\"special\">hgweb.cgi</filename> script and replace the "
7101 "<filename class=\"directory\">/path/to/repository</filename> string with the "
7102 "complete path to the repository you want to serve up."
7103 msgstr ""
7105 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7106 #: ../en/ch06-collab.xml:1051
7107 msgid ""
7108 "At this point, when you try to reload the page, you should be presented with "
7109 "a nice HTML view of your repository's history. Whew!"
7110 msgstr ""
7112 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
7113 #: ../en/ch06-collab.xml:1057
7114 msgid "Configuring lighttpd"
7115 msgstr "配置 lighttpd"
7117 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7118 #: ../en/ch06-collab.xml:1059
7119 msgid ""
7120 "To be exhaustive in my experiments, I tried configuring the increasingly "
7121 "popular <literal>lighttpd</literal> web server to serve the same repository "
7122 "as I described with Apache above. I had already overcome all of the problems "
7123 "I outlined with Apache, many of which are not server-specific. As a result, "
7124 "I was fairly sure that my file and directory permissions were good, and that "
7125 "my <filename role=\"special\">hgweb.cgi</filename> script was properly edited."
7126 msgstr ""
7128 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7129 #: ../en/ch06-collab.xml:1069
7130 msgid ""
7131 "Once I had Apache running, getting <literal>lighttpd</literal> to serve the "
7132 "repository was a snap (in other words, even if you're trying to use "
7133 "<literal>lighttpd</literal>, you should read the Apache section). I first "
7134 "had to edit the <literal>mod_access</literal> section of its config file to "
7135 "enable <literal>mod_cgi</literal> and <literal>mod_userdir</literal>, both of "
7136 "which were disabled by default on my system. I then added a few lines to the "
7137 "end of the config file, to configure these modules."
7138 msgstr ""
7140 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7141 #: ../en/ch06-collab.xml:1081
7142 msgid ""
7143 "With this done, <literal>lighttpd</literal> ran immediately for me. If I had "
7144 "configured <literal>lighttpd</literal> before Apache, I'd almost certainly "
7145 "have run into many of the same system-level configuration problems as I did "
7146 "with Apache. However, I found <literal>lighttpd</literal> to be noticeably "
7147 "easier to configure than Apache, even though I've used Apache for over a "
7148 "decade, and this was my first exposure to <literal>lighttpd</literal>."
7149 msgstr ""
7151 #. type: Content of: <book><chapter><sect1><sect2><title>
7152 #: ../en/ch06-collab.xml:1094
7153 msgid "Sharing multiple repositories with one CGI script"
7154 msgstr "使用一个 CGI 脚本共享多个版本库"
7156 #. type: Content of: <book><chapter><sect1><sect2><para>
7157 #: ../en/ch06-collab.xml:1096
7158 msgid ""
7159 "The <filename role=\"special\">hgweb.cgi</filename> script only lets you "
7160 "publish a single repository, which is an annoying restriction. If you want "
7161 "to publish more than one without wracking yourself with multiple copies of "
7162 "the same script, each with different names, a better choice is to use the "
7163 "<filename role=\"special\">hgwebdir.cgi</filename> script."
7164 msgstr ""
7166 #. type: Content of: <book><chapter><sect1><sect2><para>
7167 #: ../en/ch06-collab.xml:1104
7168 msgid ""
7169 "The procedure to configure <filename role=\"special\">hgwebdir.cgi</filename> "
7170 "is only a little more involved than for <filename role=\"special\">hgweb.cgi</"
7171 "filename>. First, you must obtain a copy of the script. If you don't have "
7172 "one handy, you can download a copy from the master Mercurial repository at "
7173 "<ulink url=\"http://www.selenic.com/repo/hg/raw-file/tip/hgwebdir.cgi"
7174 "\">http://www.selenic.com/repo/hg/raw-file/tip/hgwebdir.cgi</ulink>."
7175 msgstr ""
7177 #. type: Content of: <book><chapter><sect1><sect2><para>
7178 #: ../en/ch06-collab.xml:1117
7179 msgid ""
7180 "With basic configuration out of the way, try to visit <ulink url=\"http://"
7181 "myhostname/ myuser/hgwebdir.cgi\">http://myhostname/ myuser/hgwebdir.cgi</"
7182 "ulink> in your browser. It should display an empty list of repositories. If "
7183 "you get a blank window or error message, try walking through the list of "
7184 "potential problems in section <xref linkend=\"sec.collab.wtf\"/>."
7185 msgstr ""
7187 #. type: Content of: <book><chapter><sect1><sect2><para>
7188 #: ../en/ch06-collab.xml:1126
7189 msgid ""
7190 "The <filename role=\"special\">hgwebdir.cgi</filename> script relies on an "
7191 "external configuration file. By default, it searches for a file named "
7192 "<filename role=\"special\">hgweb.config</filename> in the same directory as "
7193 "itself. You'll need to create this file, and make it world-readable. The "
7194 "format of the file is similar to a Windows <quote>ini</quote> file, as "
7195 "understood by Python's <literal>ConfigParser</literal> <citation>web:"
7196 "configparser</citation> module."
7197 msgstr ""
7199 #. type: Content of: <book><chapter><sect1><sect2><para>
7200 #: ../en/ch06-collab.xml:1136
7201 msgid ""
7202 "The easiest way to configure <filename role=\"special\">hgwebdir.cgi</"
7203 "filename> is with a section named <literal>collections</literal>. This will "
7204 "automatically publish <emphasis>every</emphasis> repository under the "
7205 "directories you name. The section should look like this:"
7206 msgstr ""
7208 #. type: Content of: <book><chapter><sect1><sect2><para>
7209 #: ../en/ch06-collab.xml:1144
7210 msgid ""
7211 "Mercurial interprets this by looking at the directory name on the "
7212 "<emphasis>right</emphasis> hand side of the <quote><literal>=</literal></"
7213 "quote> sign; finding repositories in that directory hierarchy; and using the "
7214 "text on the <emphasis>left</emphasis> to strip off matching text from the "
7215 "names it will actually list in the web interface. The remaining component of "
7216 "a path after this stripping has occurred is called a <quote>virtual path</"
7217 "quote>."
7218 msgstr ""
7220 #. type: Content of: <book><chapter><sect1><sect2><para>
7221 #: ../en/ch06-collab.xml:1153
7222 msgid ""
7223 "Given the example above, if we have a repository whose local path is "
7224 "<filename class=\"directory\">/my/root/this/repo</filename>, the CGI script "
7225 "will strip the leading <filename class=\"directory\">/my/root</filename> from "
7226 "the name, and publish the repository with a virtual path of <filename class="
7227 "\"directory\">this/repo</filename>. If the base URL for our CGI script is "
7228 "<ulink url=\"http://myhostname/ myuser/hgwebdir.cgi\">http://myhostname/ "
7229 "myuser/hgwebdir.cgi</ulink>, the complete URL for that repository will be "
7230 "<ulink url=\"http://myhostname/ myuser/hgwebdir.cgi/this/repo\">http://"
7231 "myhostname/ myuser/hgwebdir.cgi/this/repo</ulink>."
7232 msgstr ""
7234 #. type: Content of: <book><chapter><sect1><sect2><para>
7235 #: ../en/ch06-collab.xml:1167
7236 msgid ""
7237 "If we replace <filename class=\"directory\">/my/root</filename> on the left "
7238 "hand side of this example with <filename class=\"directory\">/my</filename>, "
7239 "then <filename role=\"special\">hgwebdir.cgi</filename> will only strip off "
7240 "<filename class=\"directory\">/my</filename> from the repository name, and "
7241 "will give us a virtual path of <filename class=\"directory\">root/this/repo</"
7242 "filename> instead of <filename class=\"directory\">this/repo</filename>."
7243 msgstr ""
7245 #. type: Content of: <book><chapter><sect1><sect2><para>
7246 #: ../en/ch06-collab.xml:1177
7247 msgid ""
7248 "The <filename role=\"special\">hgwebdir.cgi</filename> script will "
7249 "recursively search each directory listed in the <literal>collections</"
7250 "literal> section of its configuration file, but it will <literal>not</"
7251 "literal> recurse into the repositories it finds."
7252 msgstr ""
7254 #. type: Content of: <book><chapter><sect1><sect2><para>
7255 #: ../en/ch06-collab.xml:1183
7256 msgid ""
7257 "The <literal>collections</literal> mechanism makes it easy to publish many "
7258 "repositories in a <quote>fire and forget</quote> manner. You only need to "
7259 "set up the CGI script and configuration file one time. Afterwards, you can "
7260 "publish or unpublish a repository at any time by simply moving it into, or "
7261 "out of, the directory hierarchy in which you've configured <filename role="
7262 "\"special\">hgwebdir.cgi</filename> to look."
7263 msgstr ""
7265 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
7266 #: ../en/ch06-collab.xml:1193
7267 msgid "Explicitly specifying which repositories to publish"
7268 msgstr "明确指出要发布的版本库"
7270 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7271 #: ../en/ch06-collab.xml:1196
7272 msgid ""
7273 "In addition to the <literal>collections</literal> mechanism, the <filename "
7274 "role=\"special\">hgwebdir.cgi</filename> script allows you to publish a "
7275 "specific list of repositories. To do so, create a <literal>paths</literal> "
7276 "section, with contents of the following form."
7277 msgstr ""
7279 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7280 #: ../en/ch06-collab.xml:1204
7281 msgid ""
7282 "In this case, the virtual path (the component that will appear in a URL) is "
7283 "on the left hand side of each definition, while the path to the repository is "
7284 "on the right. Notice that there does not need to be any relationship between "
7285 "the virtual path you choose and the location of a repository in your "
7286 "filesystem."
7287 msgstr ""
7289 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7290 #: ../en/ch06-collab.xml:1211
7291 msgid ""
7292 "If you wish, you can use both the <literal>collections</literal> and "
7293 "<literal>paths</literal> mechanisms simultaneously in a single configuration "
7294 "file."
7295 msgstr ""
7297 #. type: Content of: <book><chapter><sect1><sect2><sect3><note><para>
7298 #: ../en/ch06-collab.xml:1217
7299 msgid ""
7300 "If multiple repositories have the same virtual path, <filename role=\"special"
7301 "\">hgwebdir.cgi</filename> will not report an error. Instead, it will behave "
7302 "unpredictably."
7303 msgstr ""
7305 #. type: Content of: <book><chapter><sect1><sect2><title>
7306 #: ../en/ch06-collab.xml:1226
7307 msgid "Downloading source archives"
7308 msgstr "下载源代码档案包"
7310 #. type: Content of: <book><chapter><sect1><sect2><para>
7311 #: ../en/ch06-collab.xml:1228
7312 msgid ""
7313 "Mercurial's web interface lets users download an archive of any revision. "
7314 "This archive will contain a snapshot of the working directory as of that "
7315 "revision, but it will not contain a copy of the repository data."
7316 msgstr ""
7318 #. type: Content of: <book><chapter><sect1><sect2><para>
7319 #: ../en/ch06-collab.xml:1233
7320 msgid ""
7321 "By default, this feature is not enabled. To enable it, you'll need to add an "
7322 "<envar role=\"rc-item-web\">allow_archive</envar> item to the <literal role="
7323 "\"rc-web\">web</literal> section of your <filename role=\"special\"> /.hgrc</"
7324 "filename>."
7325 msgstr ""
7327 #. type: Content of: <book><chapter><sect1><sect2><title>
7328 #: ../en/ch06-collab.xml:1241
7329 msgid "Web configuration options"
7330 msgstr "Web 配置选项"
7332 #. type: Content of: <book><chapter><sect1><sect2><para>
7333 #: ../en/ch06-collab.xml:1243
7334 msgid ""
7335 "Mercurial's web interfaces (the <command role=\"hg-cmd\">hg serve</command> "
7336 "command, and the <filename role=\"special\">hgweb.cgi</filename> and "
7337 "<filename role=\"special\">hgwebdir.cgi</filename> scripts) have a number of "
7338 "configuration options that you can set. These belong in a section named "
7339 "<literal role=\"rc-web\">web</literal>."
7340 msgstr ""
7342 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
7343 #: ../en/ch06-collab.xml:1251
7344 msgid ""
7345 "<envar role=\"rc-item-web\">allow_archive</envar>: Determines which (if any) "
7346 "archive download mechanisms Mercurial supports. If you enable this feature, "
7347 "users of the web interface will be able to download an archive of whatever "
7348 "revision of a repository they are viewing. To enable the archive feature, "
7349 "this item must take the form of a sequence of words drawn from the list below."
7350 msgstr ""
7352 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><itemizedlist><listitem><para>
7353 #: ../en/ch06-collab.xml:1260
7354 msgid ""
7355 "<literal>bz2</literal>: A <command>tar</command> archive, compressed using "
7356 "<literal>bzip2</literal> compression. This has the best compression ratio, "
7357 "but uses the most CPU time on the server."
7358 msgstr ""
7360 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><itemizedlist><listitem><para>
7361 #: ../en/ch06-collab.xml:1266
7362 msgid ""
7363 "<literal>gz</literal>: A <command>tar</command> archive, compressed using "
7364 "<literal>gzip</literal> compression."
7365 msgstr ""
7367 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><itemizedlist><listitem><para>
7368 #: ../en/ch06-collab.xml:1270
7369 msgid ""
7370 "<literal>zip</literal>: A <command>zip</command> archive, compressed using "
7371 "LZW compression. This format has the worst compression ratio, but is widely "
7372 "used in the Windows world."
7373 msgstr ""
7375 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
7376 #: ../en/ch06-collab.xml:1276
7377 msgid ""
7378 "If you provide an empty list, or don't have an <envar role=\"rc-item-web"
7379 "\">allow_archive</envar> entry at all, this feature will be disabled. Here "
7380 "is an example of how to enable all three supported formats."
7381 msgstr ""
7383 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
7384 #: ../en/ch06-collab.xml:1283
7385 msgid ""
7386 "<envar role=\"rc-item-web\">allowpull</envar>: Boolean. Determines whether "
7387 "the web interface allows remote users to <command role=\"hg-cmd\">hg pull</"
7388 "command> and <command role=\"hg-cmd\">hg clone</command> this repository over "
7389 "HTTP. If set to <literal>no</literal> or <literal>false</literal>, only the "
7390 "<quote>human-oriented</quote> portion of the web interface is available."
7391 msgstr ""
7393 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
7394 #: ../en/ch06-collab.xml:1292
7395 msgid ""
7396 "<envar role=\"rc-item-web\">contact</envar>: String. A free-form (but "
7397 "preferably brief) string identifying the person or group in charge of the "
7398 "repository. This often contains the name and email address of a person or "
7399 "mailing list. It often makes sense to place this entry in a repository's own "
7400 "<filename role=\"special\">.hg/hgrc</filename> file, but it can make sense to "
7401 "use in a global <filename role=\"special\"> /.hgrc</filename>\\ if every "
7402 "repository has a single maintainer."
7403 msgstr ""
7405 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
7406 #: ../en/ch06-collab.xml:1303
7407 msgid ""
7408 "<envar role=\"rc-item-web\">maxchanges</envar>: Integer. The default maximum "
7409 "number of changesets to display in a single page of output."
7410 msgstr ""
7412 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
7413 #: ../en/ch06-collab.xml:1307
7414 msgid ""
7415 "<envar role=\"rc-item-web\">maxfiles</envar>: Integer. The default maximum "
7416 "number of modified files to display in a single page of output."
7417 msgstr ""
7419 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
7420 #: ../en/ch06-collab.xml:1311
7421 msgid ""
7422 "<envar role=\"rc-item-web\">stripes</envar>: Integer. If the web interface "
7423 "displays alternating <quote>stripes</quote> to make it easier to visually "
7424 "align rows when you are looking at a table, this number controls the number "
7425 "of rows in each stripe."
7426 msgstr ""
7428 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
7429 #: ../en/ch06-collab.xml:1317
7430 msgid ""
7431 "<envar role=\"rc-item-web\">style</envar>: Controls the template Mercurial "
7432 "uses to display the web interface. Mercurial ships with two web templates, "
7433 "named <literal>default</literal> and <literal>gitweb</literal> (the latter is "
7434 "much more visually attractive). You can also specify a custom template of "
7435 "your own; see chapter <xref linkend=\"chap.template\"/> for details. Here, "
7436 "you can see how to enable the <literal>gitweb</literal> style."
7437 msgstr ""
7439 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
7440 #: ../en/ch06-collab.xml:1328
7441 msgid ""
7442 "<envar role=\"rc-item-web\">templates</envar>: Path. The directory in which "
7443 "to search for template files. By default, Mercurial searches in the "
7444 "directory in which it was installed."
7445 msgstr ""
7447 #. type: Content of: <book><chapter><sect1><sect2><para>
7448 #: ../en/ch06-collab.xml:1333
7449 msgid ""
7450 "If you are using <filename role=\"special\">hgwebdir.cgi</filename>, you can "
7451 "place a few configuration items in a <literal role=\"rc-web\">web</literal> "
7452 "section of the <filename role=\"special\">hgweb.config</filename> file "
7453 "instead of a <filename role=\"special\"> /.hgrc</filename>\\ file, for "
7454 "convenience. These items are <envar role=\"rc-item-web\">motd</envar> and "
7455 "<envar role=\"rc-item-web\">style</envar>."
7456 msgstr ""
7458 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
7459 #: ../en/ch06-collab.xml:1344
7460 msgid "Options specific to an individual repository"
7461 msgstr "针对单个版本库的选项"
7463 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7464 #: ../en/ch06-collab.xml:1346
7465 msgid ""
7466 "A few <literal role=\"rc-web\">web</literal> configuration items ought to be "
7467 "placed in a repository's local <filename role=\"special\">.hg/hgrc</"
7468 "filename>, rather than a user's or global <filename role=\"special\"> /.hgrc</"
7469 "filename>."
7470 msgstr ""
7472 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
7473 #: ../en/ch06-collab.xml:1352
7474 msgid ""
7475 "<envar role=\"rc-item-web\">description</envar>: String. A free-form (but "
7476 "preferably brief) string that describes the contents or purpose of the "
7477 "repository."
7478 msgstr ""
7480 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
7481 #: ../en/ch06-collab.xml:1357
7482 msgid ""
7483 "<envar role=\"rc-item-web\">name</envar>: String. The name to use for the "
7484 "repository in the web interface. This overrides the default name, which is "
7485 "the last component of the repository's path."
7486 msgstr ""
7488 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
7489 #: ../en/ch06-collab.xml:1365
7490 msgid ""
7491 "Options specific to the <command role=\"hg-cmd\">hg serve</command> command"
7492 msgstr "命令 <command role=\"hg-cmd\">hg serve</command> 的选项"
7494 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7495 #: ../en/ch06-collab.xml:1368
7496 msgid ""
7497 "Some of the items in the <literal role=\"rc-web\">web</literal> section of a "
7498 "<filename role=\"special\"> /.hgrc</filename>\\ file are only for use with "
7499 "the <command role=\"hg-cmd\">hg serve</command> command."
7500 msgstr ""
7502 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
7503 #: ../en/ch06-collab.xml:1374
7504 msgid ""
7505 "<envar role=\"rc-item-web\">accesslog</envar>: Path. The name of a file into "
7506 "which to write an access log. By default, the <command role=\"hg-cmd\">hg "
7507 "serve</command> command writes this information to standard output, not to a "
7508 "file. Log entries are written in the standard <quote>combined</quote> file "
7509 "format used by almost all web servers."
7510 msgstr ""
7512 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
7513 #: ../en/ch06-collab.xml:1382
7514 msgid ""
7515 "<envar role=\"rc-item-web\">address</envar>: String. The local address on "
7516 "which the server should listen for incoming connections. By default, the "
7517 "server listens on all addresses."
7518 msgstr ""
7520 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
7521 #: ../en/ch06-collab.xml:1387
7522 msgid ""
7523 "<envar role=\"rc-item-web\">errorlog</envar>: Path. The name of a file into "
7524 "which to write an error log. By default, the <command role=\"hg-cmd\">hg "
7525 "serve</command> command writes this information to standard error, not to a "
7526 "file."
7527 msgstr ""
7529 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
7530 #: ../en/ch06-collab.xml:1393
7531 msgid ""
7532 "<envar role=\"rc-item-web\">ipv6</envar>: Boolean. Whether to use the IPv6 "
7533 "protocol. By default, IPv6 is not used."
7534 msgstr ""
7536 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
7537 #: ../en/ch06-collab.xml:1397
7538 msgid ""
7539 "<envar role=\"rc-item-web\">port</envar>: Integer. The TCP port number on "
7540 "which the server should listen. The default port number used is 8000."
7541 msgstr ""
7543 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
7544 #: ../en/ch06-collab.xml:1404
7545 msgid ""
7546 "Choosing the right <filename role=\"special\"> /.hgrc</filename>\\ file to "
7547 "add <literal role=\"rc-web\">web</literal> items to"
7548 msgstr ""
7549 "选择正确的 <filename role=\"special\"> /.hgrc</filename> 文件增加到 <literal "
7550 "role=\"rc-web\">web</literal> 条目"
7552 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7553 #: ../en/ch06-collab.xml:1408
7554 msgid ""
7555 "It is important to remember that a web server like Apache or "
7556 "<literal>lighttpd</literal> will run under a user ID that is different to "
7557 "yours. CGI scripts run by your server, such as <filename role=\"special"
7558 "\">hgweb.cgi</filename>, will usually also run under that user ID."
7559 msgstr ""
7561 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7562 #: ../en/ch06-collab.xml:1415
7563 msgid ""
7564 "If you add <literal role=\"rc-web\">web</literal> items to your own personal "
7565 "<filename role=\"special\"> /.hgrc</filename>\\ file, CGI scripts won't read "
7566 "that <filename role=\"special\"> /.hgrc</filename>\\ file. Those settings "
7567 "will thus only affect the behaviour of the <command role=\"hg-cmd\">hg serve</"
7568 "command> command when you run it. To cause CGI scripts to see your settings, "
7569 "either create a <filename role=\"special\"> /.hgrc</filename>\\ file in the "
7570 "home directory of the user ID that runs your web server, or add those "
7571 "settings to a system-wide <filename role=\"special\"> /.hgrc</filename>\\ "
7572 "file."
7573 msgstr ""
7575 #. type: Content of: <book><chapter><title>
7576 #: ../en/ch07-filenames.xml:5
7577 msgid "File names and pattern matching"
7578 msgstr "文件名称与模式匹配"
7580 #. type: Content of: <book><chapter><para>
7581 #: ../en/ch07-filenames.xml:7
7582 msgid ""
7583 "Mercurial provides mechanisms that let you work with file names in a "
7584 "consistent and expressive way."
7585 msgstr ""
7587 #. type: Content of: <book><chapter><sect1><title>
7588 #: ../en/ch07-filenames.xml:11
7589 msgid "Simple file naming"
7590 msgstr "简单文件名称"
7592 #. type: Content of: <book><chapter><sect1><para>
7593 #: ../en/ch07-filenames.xml:13
7594 msgid ""
7595 "Mercurial uses a unified piece of machinery <quote>under the hood</quote> to "
7596 "handle file names. Every command behaves uniformly with respect to file "
7597 "names. The way in which commands work with file names is as follows."
7598 msgstr ""
7600 #. type: Content of: <book><chapter><sect1><para>
7601 #: ../en/ch07-filenames.xml:18
7602 msgid ""
7603 "If you explicitly name real files on the command line, Mercurial works with "
7604 "exactly those files, as you would expect. &interaction.filenames.files;"
7605 msgstr ""
7607 #
7608 #. type: Content of: <book><chapter><sect1><para>
7609 #: ../en/ch07-filenames.xml:22
7610 msgid ""
7611 "When you provide a directory name, Mercurial will interpret this as "
7612 "<quote>operate on every file in this directory and its subdirectories</"
7613 "quote>. Mercurial traverses the files and subdirectories in a directory in "
7614 "alphabetical order. When it encounters a subdirectory, it will traverse that "
7615 "subdirectory before continuing with the current directory."
7616 msgstr ""
7618 #. type: Content of: <book><chapter><sect1><title>
7619 #: ../en/ch07-filenames.xml:33
7620 msgid "Running commands without any file names"
7621 msgstr "不提供文件名称的执行命令"
7623 #. type: Content of: <book><chapter><sect1><para>
7624 #: ../en/ch07-filenames.xml:35
7625 msgid ""
7626 "Mercurial's commands that work with file names have useful default behaviours "
7627 "when you invoke them without providing any file names or patterns. What kind "
7628 "of behaviour you should expect depends on what the command does. Here are a "
7629 "few rules of thumb you can use to predict what a command is likely to do if "
7630 "you don't give it any names to work with."
7631 msgstr ""
7633 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
7634 #: ../en/ch07-filenames.xml:42
7635 msgid ""
7636 "Most commands will operate on the entire working directory. This is what the "
7637 "<command role=\"hg-cmd\">hg add</command> command does, for example."
7638 msgstr ""
7640 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
7641 #: ../en/ch07-filenames.xml:46
7642 msgid ""
7643 "If the command has effects that are difficult or impossible to reverse, it "
7644 "will force you to explicitly provide at least one name or pattern (see "
7645 "below). This protects you from accidentally deleting files by running "
7646 "<command role=\"hg-cmd\">hg remove</command> with no arguments, for example."
7647 msgstr ""
7649 #
7650 #. type: Content of: <book><chapter><sect1><para>
7651 #: ../en/ch07-filenames.xml:54
7652 msgid ""
7653 "It's easy to work around these default behaviours if they don't suit you. If "
7654 "a command normally operates on the whole working directory, you can invoke it "
7655 "on just the current directory and its subdirectories by giving it the name "
7656 "<quote><filename class=\"directory\">.</filename></quote>."
7657 msgstr ""
7659 #
7660 #. type: Content of: <book><chapter><sect1><para>
7661 #: ../en/ch07-filenames.xml:62
7662 msgid ""
7663 "Along the same lines, some commands normally print file names relative to the "
7664 "root of the repository, even if you're invoking them from a subdirectory. "
7665 "Such a command will print file names relative to your subdirectory if you "
7666 "give it explicit names. Here, we're going to run <command role=\"hg-cmd\">hg "
7667 "status</command> from a subdirectory, and get it to operate on the entire "
7668 "working directory while printing file names relative to our subdirectory, by "
7669 "passing it the output of the <command role=\"hg-cmd\">hg root</command> "
7670 "command."
7671 msgstr ""
7673 #. type: Content of: <book><chapter><sect1><title>
7674 #: ../en/ch07-filenames.xml:76
7675 msgid "Telling you what's going on"
7676 msgstr "告诉你正在做什么"
7678 #. type: Content of: <book><chapter><sect1><para>
7679 #: ../en/ch07-filenames.xml:78
7680 msgid ""
7681 "The <command role=\"hg-cmd\">hg add</command> example in the preceding "
7682 "section illustrates something else that's helpful about Mercurial commands. "
7683 "If a command operates on a file that you didn't name explicitly on the "
7684 "command line, it will usually print the name of the file, so that you will "
7685 "not be surprised what's going on."
7686 msgstr ""
7688 #. type: Content of: <book><chapter><sect1><para>
7689 #: ../en/ch07-filenames.xml:85
7690 msgid ""
7691 "The principle here is of <emphasis>least surprise</emphasis>. If you've "
7692 "exactly named a file on the command line, there's no point in repeating it "
7693 "back at you. If Mercurial is acting on a file <emphasis>implicitly</"
7694 "emphasis>, because you provided no names, or a directory, or a pattern (see "
7695 "below), it's safest to tell you what it's doing."
7696 msgstr ""
7698 #. type: Content of: <book><chapter><sect1><para>
7699 #: ../en/ch07-filenames.xml:92
7700 msgid ""
7701 "For commands that behave this way, you can silence them using the <option "
7702 "role=\"hg-opt-global\">-q</option> option. You can also get them to print "
7703 "the name of every file, even those you've named explicitly, using the <option "
7704 "role=\"hg-opt-global\">-v</option> option."
7705 msgstr ""
7707 #. type: Content of: <book><chapter><sect1><title>
7708 #: ../en/ch07-filenames.xml:100
7709 msgid "Using patterns to identify files"
7710 msgstr "使用模式标识文件"
7712 #. type: Content of: <book><chapter><sect1><para>
7713 #: ../en/ch07-filenames.xml:102
7714 msgid ""
7715 "In addition to working with file and directory names, Mercurial lets you use "
7716 "<emphasis>patterns</emphasis> to identify files. Mercurial's pattern "
7717 "handling is expressive."
7718 msgstr ""
7720 #. type: Content of: <book><chapter><sect1><para>
7721 #: ../en/ch07-filenames.xml:106
7722 msgid ""
7723 "On Unix-like systems (Linux, MacOS, etc.), the job of matching file names to "
7724 "patterns normally falls to the shell. On these systems, you must explicitly "
7725 "tell Mercurial that a name is a pattern. On Windows, the shell does not "
7726 "expand patterns, so Mercurial will automatically identify names that are "
7727 "patterns, and expand them for you."
7728 msgstr ""
7730 #. type: Content of: <book><chapter><sect1><para>
7731 #: ../en/ch07-filenames.xml:113
7732 msgid ""
7733 "To provide a pattern in place of a regular name on the command line, the "
7734 "mechanism is simple:"
7735 msgstr ""
7737 #. type: Content of: <book><chapter><sect1><para>
7738 #: ../en/ch07-filenames.xml:116
7739 msgid ""
7740 "That is, a pattern is identified by a short text string that says what kind "
7741 "of pattern this is, followed by a colon, followed by the actual pattern."
7742 msgstr ""
7744 #. type: Content of: <book><chapter><sect1><para>
7745 #: ../en/ch07-filenames.xml:120
7746 msgid ""
7747 "Mercurial supports two kinds of pattern syntax. The most frequently used is "
7748 "called <literal>glob</literal>; this is the same kind of pattern matching "
7749 "used by the Unix shell, and should be familiar to Windows command prompt "
7750 "users, too."
7751 msgstr ""
7753 #. type: Content of: <book><chapter><sect1><para>
7754 #: ../en/ch07-filenames.xml:125
7755 msgid ""
7756 "When Mercurial does automatic pattern matching on Windows, it uses "
7757 "<literal>glob</literal> syntax. You can thus omit the <quote><literal>glob:</"
7758 "literal></quote> prefix on Windows, but it's safe to use it, too."
7759 msgstr ""
7761 #. type: Content of: <book><chapter><sect1><para>
7762 #: ../en/ch07-filenames.xml:130
7763 msgid ""
7764 "The <literal>re</literal> syntax is more powerful; it lets you specify "
7765 "patterns using regular expressions, also known as regexps."
7766 msgstr ""
7768 #. type: Content of: <book><chapter><sect1><para>
7769 #: ../en/ch07-filenames.xml:134
7770 msgid ""
7771 "By the way, in the examples that follow, notice that I'm careful to wrap all "
7772 "of my patterns in quote characters, so that they won't get expanded by the "
7773 "shell before Mercurial sees them."
7774 msgstr ""
7776 #. type: Content of: <book><chapter><sect1><sect2><title>
7777 #: ../en/ch07-filenames.xml:140
7778 msgid "Shell-style <literal>glob</literal> patterns"
7779 msgstr "外壳风格的 <literal>glob</literal> 模式"
7781 #. type: Content of: <book><chapter><sect1><sect2><para>
7782 #: ../en/ch07-filenames.xml:142
7783 msgid ""
7784 "This is an overview of the kinds of patterns you can use when you're matching "
7785 "on glob patterns."
7786 msgstr ""
7788 #
7789 #. type: Content of: <book><chapter><sect1><sect2><para>
7790 #: ../en/ch07-filenames.xml:145
7791 msgid ""
7792 "The <quote><literal>*</literal></quote> character matches any string, within "
7793 "a single directory."
7794 msgstr ""
7796 #
7797 #. type: Content of: <book><chapter><sect1><sect2><para>
7798 #: ../en/ch07-filenames.xml:150
7799 msgid ""
7800 "The <quote><literal>**</literal></quote> pattern matches any string, and "
7801 "crosses directory boundaries. It's not a standard Unix glob token, but it's "
7802 "accepted by several popular Unix shells, and is very useful."
7803 msgstr ""
7805 #
7806 #. type: Content of: <book><chapter><sect1><sect2><para>
7807 #: ../en/ch07-filenames.xml:157
7808 msgid ""
7809 "The <quote><literal>?</literal></quote> pattern matches any single character."
7810 msgstr ""
7812 #. type: Content of: <book><chapter><sect1><sect2><para>
7813 #: ../en/ch07-filenames.xml:162
7814 msgid ""
7815 "The <quote><literal>[</literal></quote> character begins a "
7816 "<emphasis>character class</emphasis>. This matches any single character "
7817 "within the class. The class ends with a <quote><literal>]</literal></quote> "
7818 "character. A class may contain multiple <emphasis>range</emphasis>s of the "
7819 "form <quote><literal>a-f</literal></quote>, which is shorthand for "
7820 "<quote><literal>abcdef</literal></quote>."
7821 msgstr ""
7823 #. type: Content of: <book><chapter><sect1><sect2><para>
7824 #: ../en/ch07-filenames.xml:172
7825 msgid ""
7826 "If the first character after the <quote><literal>[</literal></quote> in a "
7827 "character class is a <quote><literal>!</literal></quote>, it "
7828 "<emphasis>negates</emphasis> the class, making it match any single character "
7829 "not in the class."
7830 msgstr ""
7832 #. type: Content of: <book><chapter><sect1><sect2><para>
7833 #: ../en/ch07-filenames.xml:178
7834 msgid ""
7835 "A <quote><literal>{</literal></quote> begins a group of subpatterns, where "
7836 "the whole group matches if any subpattern in the group matches. The "
7837 "<quote><literal>,</literal></quote> character separates subpatterns, and "
7838 "<quote><literal>}</literal></quote> ends the group."
7839 msgstr ""
7841 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
7842 #: ../en/ch07-filenames.xml:187
7843 msgid "Watch out!"
7844 msgstr "千万小心！"
7846 #
7847 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
7848 #: ../en/ch07-filenames.xml:189
7849 msgid ""
7850 "Don't forget that if you want to match a pattern in any directory, you should "
7851 "not be using the <quote><literal>*</literal></quote> match-any token, as this "
7852 "will only match within one directory. Instead, use the <quote><literal>**</"
7853 "literal></quote> token. This small example illustrates the difference "
7854 "between the two."
7855 msgstr ""
7857 #. type: Content of: <book><chapter><sect1><sect2><title>
7858 #: ../en/ch07-filenames.xml:201
7859 msgid "Regular expression matching with <literal>re</literal> patterns"
7860 msgstr "使用 <literal>re</literal> 模式的正则表达式匹配"
7862 #. type: Content of: <book><chapter><sect1><sect2><para>
7863 #: ../en/ch07-filenames.xml:204
7864 msgid ""
7865 "Mercurial accepts the same regular expression syntax as the Python "
7866 "programming language (it uses Python's regexp engine internally). This is "
7867 "based on the Perl language's regexp syntax, which is the most popular dialect "
7868 "in use (it's also used in Java, for example)."
7869 msgstr ""
7871 #. type: Content of: <book><chapter><sect1><sect2><para>
7872 #: ../en/ch07-filenames.xml:210
7873 msgid ""
7874 "I won't discuss Mercurial's regexp dialect in any detail here, as regexps are "
7875 "not often used. Perl-style regexps are in any case already exhaustively "
7876 "documented on a multitude of web sites, and in many books. Instead, I will "
7877 "focus here on a few things you should know if you find yourself needing to "
7878 "use regexps with Mercurial."
7879 msgstr ""
7881 #. type: Content of: <book><chapter><sect1><sect2><para>
7882 #: ../en/ch07-filenames.xml:217
7883 msgid ""
7884 "A regexp is matched against an entire file name, relative to the root of the "
7885 "repository. In other words, even if you're already in subbdirectory "
7886 "<filename class=\"directory\">foo</filename>, if you want to match files "
7887 "under this directory, your pattern must start with <quote><literal>foo/</"
7888 "literal></quote>."
7889 msgstr ""
7891 #. type: Content of: <book><chapter><sect1><sect2><para>
7892 #: ../en/ch07-filenames.xml:224
7893 msgid ""
7894 "One thing to note, if you're familiar with Perl-style regexps, is that "
7895 "Mercurial's are <emphasis>rooted</emphasis>. That is, a regexp starts "
7896 "matching against the beginning of a string; it doesn't look for a match "
7897 "anywhere within the string. To match anywhere in a string, start your "
7898 "pattern with <quote><literal>.*</literal></quote>."
7899 msgstr ""
7901 #. type: Content of: <book><chapter><sect1><title>
7902 #: ../en/ch07-filenames.xml:234
7903 msgid "Filtering files"
7904 msgstr "过滤文件"
7906 #. type: Content of: <book><chapter><sect1><para>
7907 #: ../en/ch07-filenames.xml:236
7908 msgid ""
7909 "Not only does Mercurial give you a variety of ways to specify files; it lets "
7910 "you further winnow those files using <emphasis>filters</emphasis>. Commands "
7911 "that work with file names accept two filtering options."
7912 msgstr ""
7914 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
7915 #: ../en/ch07-filenames.xml:241
7916 msgid ""
7917 "<option role=\"hg-opt-global\">-I</option>, or <option role=\"hg-opt-global"
7918 "\">--include</option>, lets you specify a pattern that file names must match "
7919 "in order to be processed."
7920 msgstr ""
7922 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
7923 #: ../en/ch07-filenames.xml:246
7924 msgid ""
7925 "<option role=\"hg-opt-global\">-X</option>, or <option role=\"hg-opt-global"
7926 "\">--exclude</option>, gives you a way to <emphasis>avoid</emphasis> "
7927 "processing files, if they match this pattern."
7928 msgstr ""
7930 #. type: Content of: <book><chapter><sect1><para>
7931 #: ../en/ch07-filenames.xml:251
7932 msgid ""
7933 "You can provide multiple <option role=\"hg-opt-global\">-I</option> and "
7934 "<option role=\"hg-opt-global\">-X</option> options on the command line, and "
7935 "intermix them as you please. Mercurial interprets the patterns you provide "
7936 "using glob syntax by default (but you can use regexps if you need to)."
7937 msgstr ""
7939 #. type: Content of: <book><chapter><sect1><para>
7940 #: ../en/ch07-filenames.xml:258
7941 msgid ""
7942 "You can read a <option role=\"hg-opt-global\">-I</option> filter as "
7943 "<quote>process only the files that match this filter</quote>."
7944 msgstr ""
7946 #. type: Content of: <book><chapter><sect1><para>
7947 #: ../en/ch07-filenames.xml:264
7948 msgid ""
7949 "The <option role=\"hg-opt-global\">-X</option> filter is best read as "
7950 "<quote>process only the files that don't match this pattern</quote>."
7951 msgstr ""
7953 #. type: Content of: <book><chapter><sect1><title>
7954 #: ../en/ch07-filenames.xml:272
7955 msgid "Ignoring unwanted files and directories"
7956 msgstr "忽略不需要的文件和目录"
7958 #. type: Content of: <book><chapter><sect1><para>
7959 #: ../en/ch07-filenames.xml:274
7960 msgid "XXX."
7961 msgstr ""
7963 #. type: Content of: <book><chapter><sect1><title>
7964 #: ../en/ch07-filenames.xml:278
7965 msgid "Case sensitivity"
7966 msgstr "大小写敏感性"
7968 #. type: Content of: <book><chapter><sect1><para>
7969 #: ../en/ch07-filenames.xml:280
7970 msgid ""
7971 "If you're working in a mixed development environment that contains both Linux "
7972 "(or other Unix) systems and Macs or Windows systems, you should keep in the "
7973 "back of your mind the knowledge that they treat the case (<quote>N</quote> "
7974 "versus <quote>n</quote>) of file names in incompatible ways. This is not "
7975 "very likely to affect you, and it's easy to deal with if it does, but it "
7976 "could surprise you if you don't know about it."
7977 msgstr ""
7979 #. type: Content of: <book><chapter><sect1><para>
7980 #: ../en/ch07-filenames.xml:289
7981 msgid ""
7982 "Operating systems and filesystems differ in the way they handle the "
7983 "<emphasis>case</emphasis> of characters in file and directory names. There "
7984 "are three common ways to handle case in names."
7985 msgstr ""
7987 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
7988 #: ../en/ch07-filenames.xml:294
7989 msgid ""
7990 "Completely case insensitive. Uppercase and lowercase versions of a letter "
7991 "are treated as identical, both when creating a file and during subsequent "
7992 "accesses. This is common on older DOS-based systems."
7993 msgstr ""
7995 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
7996 #: ../en/ch07-filenames.xml:299
7997 msgid ""
7998 "Case preserving, but insensitive. When a file or directory is created, the "
7999 "case of its name is stored, and can be retrieved and displayed by the "
8000 "operating system. When an existing file is being looked up, its case is "
8001 "ignored. This is the standard arrangement on Windows and MacOS. The names "
8002 "<filename>foo</filename> and <filename>FoO</filename> identify the same "
8003 "file. This treatment of uppercase and lowercase letters as interchangeable "
8004 "is also referred to as <emphasis>case folding</emphasis>."
8005 msgstr ""
8007 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
8008 #: ../en/ch07-filenames.xml:310
8009 msgid ""
8010 "Case sensitive. The case of a name is significant at all times. The names "
8011 "<filename>foo</filename> and {FoO} identify different files. This is the way "
8012 "Linux and Unix systems normally work."
8013 msgstr ""
8015 #. type: Content of: <book><chapter><sect1><para>
8016 #: ../en/ch07-filenames.xml:316
8017 msgid ""
8018 "On Unix-like systems, it is possible to have any or all of the above ways of "
8019 "handling case in action at once. For example, if you use a USB thumb drive "
8020 "formatted with a FAT32 filesystem on a Linux system, Linux will handle names "
8021 "on that filesystem in a case preserving, but insensitive, way."
8022 msgstr ""
8024 #. type: Content of: <book><chapter><sect1><sect2><title>
8025 #: ../en/ch07-filenames.xml:323
8026 msgid "Safe, portable repository storage"
8027 msgstr "安全，可移植的版本库存储"
8029 #. type: Content of: <book><chapter><sect1><sect2><para>
8030 #: ../en/ch07-filenames.xml:325
8031 msgid ""
8032 "Mercurial's repository storage mechanism is <emphasis>case safe</emphasis>. "
8033 "It translates file names so that they can be safely stored on both case "
8034 "sensitive and case insensitive filesystems. This means that you can use "
8035 "normal file copying tools to transfer a Mercurial repository onto, for "
8036 "example, a USB thumb drive, and safely move that drive and repository back "
8037 "and forth between a Mac, a PC running Windows, and a Linux box."
8038 msgstr ""
8040 #. type: Content of: <book><chapter><sect1><sect2><title>
8041 #: ../en/ch07-filenames.xml:336
8042 msgid "Detecting case conflicts"
8043 msgstr "检测大小写冲突"
8045 #. type: Content of: <book><chapter><sect1><sect2><para>
8046 #: ../en/ch07-filenames.xml:338
8047 msgid ""
8048 "When operating in the working directory, Mercurial honours the naming policy "
8049 "of the filesystem where the working directory is located. If the filesystem "
8050 "is case preserving, but insensitive, Mercurial will treat names that differ "
8051 "only in case as the same."
8052 msgstr ""
8054 #. type: Content of: <book><chapter><sect1><sect2><para>
8055 #: ../en/ch07-filenames.xml:344
8056 msgid ""
8057 "An important aspect of this approach is that it is possible to commit a "
8058 "changeset on a case sensitive (typically Linux or Unix) filesystem that will "
8059 "cause trouble for users on case insensitive (usually Windows and MacOS) "
8060 "users. If a Linux user commits changes to two files, one named "
8061 "<filename>myfile.c</filename> and the other named <filename>MyFile.C</"
8062 "filename>, they will be stored correctly in the repository. And in the "
8063 "working directories of other Linux users, they will be correctly represented "
8064 "as separate files."
8065 msgstr ""
8067 #. type: Content of: <book><chapter><sect1><sect2><para>
8068 #: ../en/ch07-filenames.xml:355
8069 msgid ""
8070 "If a Windows or Mac user pulls this change, they will not initially have a "
8071 "problem, because Mercurial's repository storage mechanism is case safe. "
8072 "However, once they try to <command role=\"hg-cmd\">hg update</command> the "
8073 "working directory to that changeset, or <command role=\"hg-cmd\">hg merge</"
8074 "command> with that changeset, Mercurial will spot the conflict between the "
8075 "two file names that the filesystem would treat as the same, and forbid the "
8076 "update or merge from occurring."
8077 msgstr ""
8079 #. type: Content of: <book><chapter><sect1><sect2><title>
8080 #: ../en/ch07-filenames.xml:367
8081 msgid "Fixing a case conflict"
8082 msgstr "修正大小写冲突"
8084 #. type: Content of: <book><chapter><sect1><sect2><para>
8085 #: ../en/ch07-filenames.xml:369
8086 msgid ""
8087 "If you are using Windows or a Mac in a mixed environment where some of your "
8088 "collaborators are using Linux or Unix, and Mercurial reports a case folding "
8089 "conflict when you try to <command role=\"hg-cmd\">hg update</command> or "
8090 "<command role=\"hg-cmd\">hg merge</command>, the procedure to fix the problem "
8091 "is simple."
8092 msgstr ""
8094 #. type: Content of: <book><chapter><sect1><sect2><para>
8095 #: ../en/ch07-filenames.xml:376
8096 msgid ""
8097 "Just find a nearby Linux or Unix box, clone the problem repository onto it, "
8098 "and use Mercurial's <command role=\"hg-cmd\">hg rename</command> command to "
8099 "change the names of any offending files or directories so that they will no "
8100 "longer cause case folding conflicts. Commit this change, <command role=\"hg-"
8101 "cmd\">hg pull</command> or <command role=\"hg-cmd\">hg push</command> it "
8102 "across to your Windows or MacOS system, and <command role=\"hg-cmd\">hg "
8103 "update</command> to the revision with the non-conflicting names."
8104 msgstr ""
8106 #. type: Content of: <book><chapter><sect1><sect2><para>
8107 #: ../en/ch07-filenames.xml:386
8108 msgid ""
8109 "The changeset with case-conflicting names will remain in your project's "
8110 "history, and you still won't be able to <command role=\"hg-cmd\">hg update</"
8111 "command> your working directory to that changeset on a Windows or MacOS "
8112 "system, but you can continue development unimpeded."
8113 msgstr ""
8115 #. type: Content of: <book><chapter><sect1><sect2><note><para>
8116 #: ../en/ch07-filenames.xml:393
8117 msgid ""
8118 "Prior to version 0.9.3, Mercurial did not use a case safe repository storage "
8119 "mechanism, and did not detect case folding conflicts. If you are using an "
8120 "older version of Mercurial on Windows or MacOS, I strongly recommend that you "
8121 "upgrade."
8122 msgstr ""
8124 #. type: Content of: <book><chapter><title>
8125 #: ../en/ch08-branch.xml:5
8126 msgid "Managing releases and branchy development"
8127 msgstr "发布管理与分支开发"
8129 #. type: Content of: <book><chapter><para>
8130 #: ../en/ch08-branch.xml:7
8131 msgid ""
8132 "Mercurial provides several mechanisms for you to manage a project that is "
8133 "making progress on multiple fronts at once. To understand these mechanisms, "
8134 "let's first take a brief look at a fairly normal software project structure."
8135 msgstr ""
8137 #. type: Content of: <book><chapter><para>
8138 #: ../en/ch08-branch.xml:12
8139 msgid ""
8140 "Many software projects issue periodic <quote>major</quote> releases that "
8141 "contain substantial new features. In parallel, they may issue <quote>minor</"
8142 "quote> releases. These are usually identical to the major releases off which "
8143 "they're based, but with a few bugs fixed."
8144 msgstr ""
8146 #. type: Content of: <book><chapter><para>
8147 #: ../en/ch08-branch.xml:18
8148 msgid ""
8149 "In this chapter, we'll start by talking about how to keep records of project "
8150 "milestones such as releases. We'll then continue on to talk about the flow "
8151 "of work between different phases of a project, and how Mercurial can help you "
8152 "to isolate and manage this work."
8153 msgstr ""
8155 #. type: Content of: <book><chapter><sect1><title>
8156 #: ../en/ch08-branch.xml:25
8157 msgid "Giving a persistent name to a revision"
8158 msgstr "给版本指定一个永久的名称"
8160 #. type: Content of: <book><chapter><sect1><para>
8161 #: ../en/ch08-branch.xml:27
8162 msgid ""
8163 "Once you decide that you'd like to call a particular revision a "
8164 "<quote>release</quote>, it's a good idea to record the identity of that "
8165 "revision. This will let you reproduce that release at a later date, for "
8166 "whatever purpose you might need at the time (reproducing a bug, porting to a "
8167 "new platform, etc). &interaction.tag.init;"
8168 msgstr ""
8170 #
8171 #. type: Content of: <book><chapter><sect1><para>
8172 #: ../en/ch08-branch.xml:34
8173 msgid ""
8174 "Mercurial lets you give a permanent name to any revision using the <command "
8175 "role=\"hg-cmd\">hg tag</command> command. Not surprisingly, these names are "
8176 "called <quote>tags</quote>."
8177 msgstr ""
8179 #. type: Content of: <book><chapter><sect1><para>
8180 #: ../en/ch08-branch.xml:40
8181 msgid ""
8182 "A tag is nothing more than a <quote>symbolic name</quote> for a revision. "
8183 "Tags exist purely for your convenience, so that you have a handy permanent "
8184 "way to refer to a revision; Mercurial doesn't interpret the tag names you use "
8185 "in any way. Neither does Mercurial place any restrictions on the name of a "
8186 "tag, beyond a few that are necessary to ensure that a tag can be parsed "
8187 "unambiguously. A tag name cannot contain any of the following characters:"
8188 msgstr ""
8190 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
8191 #: ../en/ch08-branch.xml:49
8192 msgid "Colon (ASCII 58, <quote><literal>:</literal></quote>)"
8193 msgstr ""
8195 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
8196 #: ../en/ch08-branch.xml:52
8197 msgid "Carriage return (ASCII 13, <quote><literal>\\r</literal></quote>)"
8198 msgstr ""
8200 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
8201 #: ../en/ch08-branch.xml:55
8202 msgid "Newline (ASCII 10, <quote><literal>\\n</literal></quote>)"
8203 msgstr ""
8205 #. type: Content of: <book><chapter><sect1><para>
8206 #: ../en/ch08-branch.xml:59
8207 msgid ""
8208 "You can use the <command role=\"hg-cmd\">hg tags</command> command to display "
8209 "the tags present in your repository. In the output, each tagged revision is "
8210 "identified first by its name, then by revision number, and finally by the "
8211 "unique hash of the revision."
8212 msgstr ""
8214 #. type: Content of: <book><chapter><sect1><para>
8215 #: ../en/ch08-branch.xml:67
8216 msgid ""
8217 "Notice that <literal>tip</literal> is listed in the output of <command role="
8218 "\"hg-cmd\">hg tags</command>. The <literal>tip</literal> tag is a special "
8219 "<quote>floating</quote> tag, which always identifies the newest revision in "
8220 "the repository."
8221 msgstr ""
8223 #. type: Content of: <book><chapter><sect1><para>
8224 #: ../en/ch08-branch.xml:73
8225 msgid ""
8226 "In the output of the <command role=\"hg-cmd\">hg tags</command> command, tags "
8227 "are listed in reverse order, by revision number. This usually means that "
8228 "recent tags are listed before older tags. It also means that <literal>tip</"
8229 "literal> is always going to be the first tag listed in the output of <command "
8230 "role=\"hg-cmd\">hg tags</command>."
8231 msgstr ""
8233 #. type: Content of: <book><chapter><sect1><para>
8234 #: ../en/ch08-branch.xml:80
8235 msgid ""
8236 "When you run <command role=\"hg-cmd\">hg log</command>, if it displays a "
8237 "revision that has tags associated with it, it will print those tags."
8238 msgstr ""
8240 #
8241 #. type: Content of: <book><chapter><sect1><para>
8242 #: ../en/ch08-branch.xml:86
8243 msgid ""
8244 "Any time you need to provide a revision ID to a Mercurial command, the "
8245 "command will accept a tag name in its place. Internally, Mercurial will "
8246 "translate your tag name into the corresponding revision ID, then use that."
8247 msgstr ""
8249 #. type: Content of: <book><chapter><sect1><para>
8250 #: ../en/ch08-branch.xml:93
8251 msgid ""
8252 "There's no limit on the number of tags you can have in a repository, or on "
8253 "the number of tags that a single revision can have. As a practical matter, "
8254 "it's not a great idea to have <quote>too many</quote> (a number which will "
8255 "vary from project to project), simply because tags are supposed to help you "
8256 "to find revisions. If you have lots of tags, the ease of using them to "
8257 "identify revisions diminishes rapidly."
8258 msgstr ""
8260 #. type: Content of: <book><chapter><sect1><para>
8261 #: ../en/ch08-branch.xml:101
8262 msgid ""
8263 "For example, if your project has milestones as frequent as every few days, "
8264 "it's perfectly reasonable to tag each one of those. But if you have a "
8265 "continuous build system that makes sure every revision can be built cleanly, "
8266 "you'd be introducing a lot of noise if you were to tag every clean build. "
8267 "Instead, you could tag failed builds (on the assumption that they're rare!), "
8268 "or simply not use tags to track buildability."
8269 msgstr ""
8271 #. type: Content of: <book><chapter><sect1><para>
8272 #: ../en/ch08-branch.xml:109
8273 msgid ""
8274 "If you want to remove a tag that you no longer want, use <command role=\"hg-"
8275 "cmd\">hg tag --remove</command>."
8276 msgstr ""
8278 #. type: Content of: <book><chapter><sect1><para>
8279 #: ../en/ch08-branch.xml:114
8280 msgid ""
8281 "You can also modify a tag at any time, so that it identifies a different "
8282 "revision, by simply issuing a new <command role=\"hg-cmd\">hg tag</command> "
8283 "command. You'll have to use the <option role=\"hg-opt-tag\">-f</option> "
8284 "option to tell Mercurial that you <emphasis>really</emphasis> want to update "
8285 "the tag."
8286 msgstr ""
8288 #. type: Content of: <book><chapter><sect1><para>
8289 #: ../en/ch08-branch.xml:123
8290 msgid ""
8291 "There will still be a permanent record of the previous identity of the tag, "
8292 "but Mercurial will no longer use it. There's thus no penalty to tagging the "
8293 "wrong revision; all you have to do is turn around and tag the correct "
8294 "revision once you discover your error."
8295 msgstr ""
8297 #
8298 #. type: Content of: <book><chapter><sect1><para>
8299 #: ../en/ch08-branch.xml:129
8300 msgid ""
8301 "Mercurial stores tags in a normal revision-controlled file in your "
8302 "repository. If you've created any tags, you'll find them in a file named "
8303 "<filename role=\"special\">.hgtags</filename>. When you run the <command "
8304 "role=\"hg-cmd\">hg tag</command> command, Mercurial modifies this file, then "
8305 "automatically commits the change to it. This means that every time you run "
8306 "<command role=\"hg-cmd\">hg tag</command>, you'll see a corresponding "
8307 "changeset in the output of <command role=\"hg-cmd\">hg log</command>."
8308 msgstr ""
8310 #. type: Content of: <book><chapter><sect1><sect2><title>
8311 #: ../en/ch08-branch.xml:142
8312 msgid "Handling tag conflicts during a merge"
8313 msgstr "在合并期间处理标签冲突"
8315 #. type: Content of: <book><chapter><sect1><sect2><para>
8316 #: ../en/ch08-branch.xml:144
8317 msgid ""
8318 "You won't often need to care about the <filename role=\"special\">.hgtags</"
8319 "filename> file, but it sometimes makes its presence known during a merge. "
8320 "The format of the file is simple: it consists of a series of lines. Each "
8321 "line starts with a changeset hash, followed by a space, followed by the name "
8322 "of a tag."
8323 msgstr ""
8325 #. type: Content of: <book><chapter><sect1><sect2><para>
8326 #: ../en/ch08-branch.xml:151
8327 msgid ""
8328 "If you're resolving a conflict in the <filename role=\"special\">.hgtags</"
8329 "filename> file during a merge, there's one twist to modifying the <filename "
8330 "role=\"special\">.hgtags</filename> file: when Mercurial is parsing the tags "
8331 "in a repository, it <emphasis>never</emphasis> reads the working copy of the "
8332 "<filename role=\"special\">.hgtags</filename> file. Instead, it reads the "
8333 "<emphasis>most recently committed</emphasis> revision of the file."
8334 msgstr ""
8336 #. type: Content of: <book><chapter><sect1><sect2><para>
8337 #: ../en/ch08-branch.xml:161
8338 msgid ""
8339 "An unfortunate consequence of this design is that you can't actually verify "
8340 "that your merged <filename role=\"special\">.hgtags</filename> file is "
8341 "correct until <emphasis>after</emphasis> you've committed a change. So if "
8342 "you find yourself resolving a conflict on <filename role=\"special\">.hgtags</"
8343 "filename> during a merge, be sure to run <command role=\"hg-cmd\">hg tags</"
8344 "command> after you commit. If it finds an error in the <filename role="
8345 "\"special\">.hgtags</filename> file, it will report the location of the "
8346 "error, which you can then fix and commit. You should then run <command role="
8347 "\"hg-cmd\">hg tags</command> again, just to be sure that your fix is correct."
8348 msgstr ""
8350 #. type: Content of: <book><chapter><sect1><sect2><title>
8351 #: ../en/ch08-branch.xml:176
8352 msgid "Tags and cloning"
8353 msgstr "标签与克隆"
8355 #. type: Content of: <book><chapter><sect1><sect2><para>
8356 #: ../en/ch08-branch.xml:178
8357 msgid ""
8358 "You may have noticed that the <command role=\"hg-cmd\">hg clone</command> "
8359 "command has a <option role=\"hg-opt-clone\">-r</option> option that lets you "
8360 "clone an exact copy of the repository as of a particular changeset. The new "
8361 "clone will not contain any project history that comes after the revision you "
8362 "specified. This has an interaction with tags that can surprise the unwary."
8363 msgstr ""
8365 #. type: Content of: <book><chapter><sect1><sect2><para>
8366 #: ../en/ch08-branch.xml:186
8367 msgid ""
8368 "Recall that a tag is stored as a revision to the <filename role=\"special\">."
8369 "hgtags</filename> file, so that when you create a tag, the changeset in which "
8370 "it's recorded necessarily refers to an older changeset. When you run "
8371 "<command role=\"hg-cmd\">hg clone -r foo</command> to clone a repository as "
8372 "of tag <literal>foo</literal>, the new clone <emphasis>will not contain the "
8373 "history that created the tag</emphasis> that you used to clone the "
8374 "repository. The result is that you'll get exactly the right subset of the "
8375 "project's history in the new repository, but <emphasis>not</emphasis> the tag "
8376 "you might have expected."
8377 msgstr ""
8379 #. type: Content of: <book><chapter><sect1><sect2><title>
8380 #: ../en/ch08-branch.xml:201
8381 msgid "When permanent tags are too much"
8382 msgstr "当永久标签太多的时候"
8384 #. type: Content of: <book><chapter><sect1><sect2><para>
8385 #: ../en/ch08-branch.xml:203
8386 msgid ""
8387 "Since Mercurial's tags are revision controlled and carried around with a "
8388 "project's history, everyone you work with will see the tags you create. But "
8389 "giving names to revisions has uses beyond simply noting that revision "
8390 "<literal>4237e45506ee</literal> is really <literal>v2.0.2</literal>. If "
8391 "you're trying to track down a subtle bug, you might want a tag to remind you "
8392 "of something like <quote>Anne saw the symptoms with this revision</quote>."
8393 msgstr ""
8395 #. type: Content of: <book><chapter><sect1><sect2><para>
8396 #: ../en/ch08-branch.xml:213
8397 msgid ""
8398 "For cases like this, what you might want to use are <emphasis>local</"
8399 "emphasis> tags. You can create a local tag with the <option role=\"hg-opt-tag"
8400 "\">-l</option> option to the <command role=\"hg-cmd\">hg tag</command> "
8401 "command. This will store the tag in a file called <filename role=\"special"
8402 "\">.hg/localtags</filename>. Unlike <filename role=\"special\">.hgtags</"
8403 "filename>, <filename role=\"special\">.hg/localtags</filename> is not "
8404 "revision controlled. Any tags you create using <option role=\"hg-opt-tag\">-"
8405 "l</option> remain strictly local to the repository you're currently working "
8406 "in."
8407 msgstr ""
8409 #. type: Content of: <book><chapter><sect1><title>
8410 #: ../en/ch08-branch.xml:228
8411 msgid "The flow of changes&emdash;big picture vs. little"
8412 msgstr "修改流程&emdash;宏观与微观"
8414 #. type: Content of: <book><chapter><sect1><para>
8415 #: ../en/ch08-branch.xml:230
8416 msgid ""
8417 "To return to the outline I sketched at the beginning of a chapter, let's "
8418 "think about a project that has multiple concurrent pieces of work under "
8419 "development at once."
8420 msgstr ""
8422 #. type: Content of: <book><chapter><sect1><para>
8423 #: ../en/ch08-branch.xml:234
8424 msgid ""
8425 "There might be a push for a new <quote>main</quote> release; a new minor "
8426 "bugfix release to the last main release; and an unexpected <quote>hot fix</"
8427 "quote> to an old release that is now in maintenance mode."
8428 msgstr ""
8430 #. type: Content of: <book><chapter><sect1><para>
8431 #: ../en/ch08-branch.xml:239
8432 msgid ""
8433 "The usual way people refer to these different concurrent directions of "
8434 "development is as <quote>branches</quote>. However, we've already seen "
8435 "numerous times that Mercurial treats <emphasis>all of history</emphasis> as a "
8436 "series of branches and merges. Really, what we have here is two ideas that "
8437 "are peripherally related, but which happen to share a name."
8438 msgstr ""
8440 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
8441 #: ../en/ch08-branch.xml:246
8442 msgid ""
8443 "<quote>Big picture</quote> branches represent the sweep of a project's "
8444 "evolution; people give them names, and talk about them in conversation."
8445 msgstr ""
8447 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
8448 #: ../en/ch08-branch.xml:250
8449 msgid ""
8450 "<quote>Little picture</quote> branches are artefacts of the day-to-day "
8451 "activity of developing and merging changes. They expose the narrative of how "
8452 "the code was developed."
8453 msgstr ""
8455 #. type: Content of: <book><chapter><sect1><title>
8456 #: ../en/ch08-branch.xml:258
8457 msgid "Managing big-picture branches in repositories"
8458 msgstr "在版本库中管理分支"
8460 #. type: Content of: <book><chapter><sect1><para>
8461 #: ../en/ch08-branch.xml:260
8462 msgid ""
8463 "The easiest way to isolate a <quote>big picture</quote> branch in Mercurial "
8464 "is in a dedicated repository. If you have an existing shared "
8465 "repository&emdash;let's call it <literal>myproject</literal>&emdash;that "
8466 "reaches a <quote>1.0</quote> milestone, you can start to prepare for future "
8467 "maintenance releases on top of version 1.0 by tagging the revision from which "
8468 "you prepared the 1.0 release."
8469 msgstr ""
8471 #. type: Content of: <book><chapter><sect1><para>
8472 #: ../en/ch08-branch.xml:270
8473 msgid ""
8474 "You can then clone a new shared <literal>myproject-1.0.1</literal> repository "
8475 "as of that tag."
8476 msgstr ""
8478 #. type: Content of: <book><chapter><sect1><para>
8479 #: ../en/ch08-branch.xml:276
8480 msgid ""
8481 "Afterwards, if someone needs to work on a bug fix that ought to go into an "
8482 "upcoming 1.0.1 minor release, they clone the <literal>myproject-1.0.1</"
8483 "literal> repository, make their changes, and push them back."
8484 msgstr ""
8486 #. type: Content of: <book><chapter><sect1><para>
8487 #: ../en/ch08-branch.xml:283
8488 msgid ""
8489 "Meanwhile, development for the next major release can continue, isolated and "
8490 "unabated, in the <literal>myproject</literal> repository."
8491 msgstr ""
8493 #. type: Content of: <book><chapter><sect1><title>
8494 #: ../en/ch08-branch.xml:291
8495 msgid "Don't repeat yourself: merging across branches"
8496 msgstr "不要重复劳动：在分支间合并"
8498 #. type: Content of: <book><chapter><sect1><para>
8499 #: ../en/ch08-branch.xml:293
8500 msgid ""
8501 "In many cases, if you have a bug to fix on a maintenance branch, the chances "
8502 "are good that the bug exists on your project's main branch (and possibly "
8503 "other maintenance branches, too). It's a rare developer who wants to fix the "
8504 "same bug multiple times, so let's look at a few ways that Mercurial can help "
8505 "you to manage these bugfixes without duplicating your work."
8506 msgstr ""
8508 #. type: Content of: <book><chapter><sect1><para>
8509 #: ../en/ch08-branch.xml:301
8510 msgid ""
8511 "In the simplest instance, all you need to do is pull changes from your "
8512 "maintenance branch into your local clone of the target branch."
8513 msgstr ""
8515 #. type: Content of: <book><chapter><sect1><para>
8516 #: ../en/ch08-branch.xml:307
8517 msgid ""
8518 "You'll then need to merge the heads of the two branches, and push back to the "
8519 "main branch."
8520 msgstr ""
8522 #. type: Content of: <book><chapter><sect1><title>
8523 #: ../en/ch08-branch.xml:314
8524 msgid "Naming branches within one repository"
8525 msgstr "版本库中的命名分支"
8527 #. type: Content of: <book><chapter><sect1><para>
8528 #: ../en/ch08-branch.xml:316
8529 msgid ""
8530 "In most instances, isolating branches in repositories is the right approach. "
8531 "Its simplicity makes it easy to understand; and so it's hard to make "
8532 "mistakes. There's a one-to-one relationship between branches you're working "
8533 "in and directories on your system. This lets you use normal (non-Mercurial-"
8534 "aware) tools to work on files within a branch/repository."
8535 msgstr ""
8537 #. type: Content of: <book><chapter><sect1><para>
8538 #: ../en/ch08-branch.xml:323
8539 msgid ""
8540 "If you're more in the <quote>power user</quote> category (<emphasis>and</"
8541 "emphasis> your collaborators are too), there is an alternative way of "
8542 "handling branches that you can consider. I've already mentioned the human-"
8543 "level distinction between <quote>small picture</quote> and <quote>big "
8544 "picture</quote> branches. While Mercurial works with multiple <quote>small "
8545 "picture</quote> branches in a repository all the time (for example after you "
8546 "pull changes in, but before you merge them), it can <emphasis>also</emphasis> "
8547 "work with multiple <quote>big picture</quote> branches."
8548 msgstr ""
8550 #. type: Content of: <book><chapter><sect1><para>
8551 #: ../en/ch08-branch.xml:334
8552 msgid ""
8553 "The key to working this way is that Mercurial lets you assign a persistent "
8554 "<emphasis>name</emphasis> to a branch. There always exists a branch named "
8555 "<literal>default</literal>. Even before you start naming branches yourself, "
8556 "you can find traces of the <literal>default</literal> branch if you look for "
8557 "them."
8558 msgstr ""
8560 #. type: Content of: <book><chapter><sect1><para>
8561 #: ../en/ch08-branch.xml:341
8562 msgid ""
8563 "As an example, when you run the <command role=\"hg-cmd\">hg commit</command> "
8564 "command, and it pops up your editor so that you can enter a commit message, "
8565 "look for a line that contains the text <quote><literal>HG: branch default</"
8566 "literal></quote> at the bottom. This is telling you that your commit will "
8567 "occur on the branch named <literal>default</literal>."
8568 msgstr ""
8570 #. type: Content of: <book><chapter><sect1><para>
8571 #: ../en/ch08-branch.xml:348
8572 msgid ""
8573 "To start working with named branches, use the <command role=\"hg-cmd\">hg "
8574 "branches</command> command. This command lists the named branches already "
8575 "present in your repository, telling you which changeset is the tip of each."
8576 msgstr ""
8578 #. type: Content of: <book><chapter><sect1><para>
8579 #: ../en/ch08-branch.xml:355
8580 msgid ""
8581 "Since you haven't created any named branches yet, the only one that exists is "
8582 "<literal>default</literal>."
8583 msgstr ""
8585 #. type: Content of: <book><chapter><sect1><para>
8586 #: ../en/ch08-branch.xml:358
8587 msgid ""
8588 "To find out what the <quote>current</quote> branch is, run the <command role="
8589 "\"hg-cmd\">hg branch</command> command, giving it no arguments. This tells "
8590 "you what branch the parent of the current changeset is on."
8591 msgstr ""
8593 #
8594 #. type: Content of: <book><chapter><sect1><para>
8595 #: ../en/ch08-branch.xml:365
8596 msgid ""
8597 "To create a new branch, run the <command role=\"hg-cmd\">hg branch</command> "
8598 "command again. This time, give it one argument: the name of the branch you "
8599 "want to create."
8600 msgstr ""
8602 #. type: Content of: <book><chapter><sect1><para>
8603 #: ../en/ch08-branch.xml:371
8604 msgid ""
8605 "After you've created a branch, you might wonder what effect the <command role="
8606 "\"hg-cmd\">hg branch</command> command has had. What do the <command role="
8607 "\"hg-cmd\">hg status</command> and <command role=\"hg-cmd\">hg tip</command> "
8608 "commands report?"
8609 msgstr ""
8611 #. type: Content of: <book><chapter><sect1><para>
8612 #: ../en/ch08-branch.xml:378
8613 msgid ""
8614 "Nothing has changed in the working directory, and there's been no new history "
8615 "created. As this suggests, running the <command role=\"hg-cmd\">hg branch</"
8616 "command> command has no permanent effect; it only tells Mercurial what branch "
8617 "name to use the <emphasis>next</emphasis> time you commit a changeset."
8618 msgstr ""
8620 #. type: Content of: <book><chapter><sect1><para>
8621 #: ../en/ch08-branch.xml:385
8622 msgid ""
8623 "When you commit a change, Mercurial records the name of the branch on which "
8624 "you committed. Once you've switched from the <literal>default</literal> "
8625 "branch to another and committed, you'll see the name of the new branch show "
8626 "up in the output of <command role=\"hg-cmd\">hg log</command>, <command role="
8627 "\"hg-cmd\">hg tip</command>, and other commands that display the same kind of "
8628 "output."
8629 msgstr ""
8631 #. type: Content of: <book><chapter><sect1><para>
8632 #: ../en/ch08-branch.xml:395
8633 msgid ""
8634 "The <command role=\"hg-cmd\">hg log</command>-like commands will print the "
8635 "branch name of every changeset that's not on the <literal>default</literal> "
8636 "branch. As a result, if you never use named branches, you'll never see this "
8637 "information."
8638 msgstr ""
8640 #. type: Content of: <book><chapter><sect1><para>
8641 #: ../en/ch08-branch.xml:400
8642 msgid ""
8643 "Once you've named a branch and committed a change with that name, every "
8644 "subsequent commit that descends from that change will inherit the same branch "
8645 "name. You can change the name of a branch at any time, using the <command "
8646 "role=\"hg-cmd\">hg branch</command> command."
8647 msgstr ""
8649 #. type: Content of: <book><chapter><sect1><para>
8650 #: ../en/ch08-branch.xml:408
8651 msgid ""
8652 "In practice, this is something you won't do very often, as branch names tend "
8653 "to have fairly long lifetimes. (This isn't a rule, just an observation.)"
8654 msgstr ""
8656 #. type: Content of: <book><chapter><sect1><title>
8657 #: ../en/ch08-branch.xml:414
8658 msgid "Dealing with multiple named branches in a repository"
8659 msgstr "在版本库中处理多个命名分支"
8661 #. type: Content of: <book><chapter><sect1><para>
8662 #: ../en/ch08-branch.xml:417
8663 msgid ""
8664 "If you have more than one named branch in a repository, Mercurial will "
8665 "remember the branch that your working directory on when you start a command "
8666 "like <command role=\"hg-cmd\">hg update</command> or <command role=\"hg-cmd"
8667 "\">hg pull -u</command>. It will update the working directory to the tip of "
8668 "this branch, no matter what the <quote>repo-wide</quote> tip is. To update "
8669 "to a revision that's on a different named branch, you may need to use the "
8670 "<option role=\"hg-opt-update\">-C</option> option to <command role=\"hg-cmd"
8671 "\">hg update</command>."
8672 msgstr ""
8674 #. type: Content of: <book><chapter><sect1><para>
8675 #: ../en/ch08-branch.xml:427
8676 msgid ""
8677 "This behaviour is a little subtle, so let's see it in action. First, let's "
8678 "remind ourselves what branch we're currently on, and what branches are in our "
8679 "repository."
8680 msgstr ""
8682 #. type: Content of: <book><chapter><sect1><para>
8683 #: ../en/ch08-branch.xml:433
8684 msgid ""
8685 "We're on the <literal>bar</literal> branch, but there also exists an older "
8686 "<command role=\"hg-cmd\">hg foo</command> branch."
8687 msgstr ""
8689 #. type: Content of: <book><chapter><sect1><para>
8690 #: ../en/ch08-branch.xml:437
8691 msgid ""
8692 "We can <command role=\"hg-cmd\">hg update</command> back and forth between "
8693 "the tips of the <literal>foo</literal> and <literal>bar</literal> branches "
8694 "without needing to use the <option role=\"hg-opt-update\">-C</option> option, "
8695 "because this only involves going backwards and forwards linearly through our "
8696 "change history."
8697 msgstr ""
8699 #
8700 #. type: Content of: <book><chapter><sect1><para>
8701 #: ../en/ch08-branch.xml:446
8702 msgid ""
8703 "If we go back to the <literal>foo</literal> branch and then run <command role="
8704 "\"hg-cmd\">hg update</command>, it will keep us on <literal>foo</literal>, "
8705 "not move us to the tip of <literal>bar</literal>."
8706 msgstr ""
8708 #
8709 #. type: Content of: <book><chapter><sect1><para>
8710 #: ../en/ch08-branch.xml:453
8711 msgid ""
8712 "Committing a new change on the <literal>foo</literal> branch introduces a new "
8713 "head."
8714 msgstr ""
8716 #. type: Content of: <book><chapter><sect1><title>
8717 #: ../en/ch08-branch.xml:460
8718 msgid "Branch names and merging"
8719 msgstr "分支名称与合并"
8721 #. type: Content of: <book><chapter><sect1><para>
8722 #: ../en/ch08-branch.xml:462
8723 msgid ""
8724 "As you've probably noticed, merges in Mercurial are not symmetrical. Let's "
8725 "say our repository has two heads, 17 and 23. If I <command role=\"hg-cmd"
8726 "\">hg update</command> to 17 and then <command role=\"hg-cmd\">hg merge</"
8727 "command> with 23, Mercurial records 17 as the first parent of the merge, and "
8728 "23 as the second. Whereas if I <command role=\"hg-cmd\">hg update</command> "
8729 "to 23 and then <command role=\"hg-cmd\">hg merge</command> with 17, it "
8730 "records 23 as the first parent, and 17 as the second."
8731 msgstr ""
8733 #. type: Content of: <book><chapter><sect1><para>
8734 #: ../en/ch08-branch.xml:472
8735 msgid ""
8736 "This affects Mercurial's choice of branch name when you merge. After a "
8737 "merge, Mercurial will retain the branch name of the first parent when you "
8738 "commit the result of the merge. If your first parent's branch name is "
8739 "<literal>foo</literal>, and you merge with <literal>bar</literal>, the branch "
8740 "name will still be <literal>foo</literal> after you merge."
8741 msgstr ""
8743 #. type: Content of: <book><chapter><sect1><para>
8744 #: ../en/ch08-branch.xml:479
8745 msgid ""
8746 "It's not unusual for a repository to contain multiple heads, each with the "
8747 "same branch name. Let's say I'm working on the <literal>foo</literal> "
8748 "branch, and so are you. We commit different changes; I pull your changes; I "
8749 "now have two heads, each claiming to be on the <literal>foo</literal> "
8750 "branch. The result of a merge will be a single head on the <literal>foo</"
8751 "literal> branch, as you might hope."
8752 msgstr ""
8754 #
8755 #. type: Content of: <book><chapter><sect1><para>
8756 #: ../en/ch08-branch.xml:487
8757 msgid ""
8758 "But if I'm working on the <literal>bar</literal> branch, and I merge work "
8759 "from the <literal>foo</literal> branch, the result will remain on the "
8760 "<literal>bar</literal> branch."
8761 msgstr ""
8763 #. type: Content of: <book><chapter><sect1><para>
8764 #: ../en/ch08-branch.xml:493
8765 msgid ""
8766 "To give a more concrete example, if I'm working on the <literal>bleeding-"
8767 "edge</literal> branch, and I want to bring in the latest fixes from the "
8768 "<literal>stable</literal> branch, Mercurial will choose the <quote>right</"
8769 "quote> (<literal>bleeding-edge</literal>) branch name when I pull and merge "
8770 "from <literal>stable</literal>."
8771 msgstr ""
8773 #. type: Content of: <book><chapter><sect1><title>
8774 #: ../en/ch08-branch.xml:502
8775 msgid "Branch naming is generally useful"
8776 msgstr "分支名称通常都很有用"
8778 #. type: Content of: <book><chapter><sect1><para>
8779 #: ../en/ch08-branch.xml:504
8780 msgid ""
8781 "You shouldn't think of named branches as applicable only to situations where "
8782 "you have multiple long-lived branches cohabiting in a single repository. "
8783 "They're very useful even in the one-branch-per-repository case."
8784 msgstr ""
8786 #. type: Content of: <book><chapter><sect1><para>
8787 #: ../en/ch08-branch.xml:509
8788 msgid ""
8789 "In the simplest case, giving a name to each branch gives you a permanent "
8790 "record of which branch a changeset originated on. This gives you more "
8791 "context when you're trying to follow the history of a long-lived branchy "
8792 "project."
8793 msgstr ""
8795 #. type: Content of: <book><chapter><sect1><para>
8796 #: ../en/ch08-branch.xml:514
8797 msgid ""
8798 "If you're working with shared repositories, you can set up a <literal role="
8799 "\"hook\">pretxnchangegroup</literal> hook on each that will block incoming "
8800 "changes that have the <quote>wrong</quote> branch name. This provides a "
8801 "simple, but effective, defence against people accidentally pushing changes "
8802 "from a <quote>bleeding edge</quote> branch to a <quote>stable</quote> "
8803 "branch. Such a hook might look like this inside the shared repo's <filename "
8804 "role=\"special\"> /.hgrc</filename>."
8805 msgstr ""
8807 #. type: Content of: <book><chapter><title>
8808 #: ../en/ch09-undo.xml:5
8809 msgid "Finding and fixing mistakes"
8810 msgstr "查找和修改错误"
8812 #. type: Content of: <book><chapter><para>
8813 #: ../en/ch09-undo.xml:7
8814 msgid ""
8815 "To err might be human, but to really handle the consequences well takes a top-"
8816 "notch revision control system. In this chapter, we'll discuss some of the "
8817 "techniques you can use when you find that a problem has crept into your "
8818 "project. Mercurial has some highly capable features that will help you to "
8819 "isolate the sources of problems, and to handle them appropriately."
8820 msgstr ""
8822 #. type: Content of: <book><chapter><sect1><title>
8823 #: ../en/ch09-undo.xml:15
8824 msgid "Erasing local history"
8825 msgstr "销毁本地历史"
8827 #. type: Content of: <book><chapter><sect1><sect2><title>
8828 #: ../en/ch09-undo.xml:18
8829 msgid "The accidental commit"
8830 msgstr "意外的提交"
8832 #. type: Content of: <book><chapter><sect1><sect2><para>
8833 #: ../en/ch09-undo.xml:20
8834 msgid ""
8835 "I have the occasional but persistent problem of typing rather more quickly "
8836 "than I can think, which sometimes results in me committing a changeset that "
8837 "is either incomplete or plain wrong. In my case, the usual kind of "
8838 "incomplete changeset is one in which I've created a new source file, but "
8839 "forgotten to <command role=\"hg-cmd\">hg add</command> it. A <quote>plain "
8840 "wrong</quote> changeset is not as common, but no less annoying."
8841 msgstr ""
8843 #. type: Content of: <book><chapter><sect1><sect2><title>
8844 #: ../en/ch09-undo.xml:31
8845 msgid "Rolling back a transaction"
8846 msgstr "回滚一个事务"
8848 #. type: Content of: <book><chapter><sect1><sect2><para>
8849 #: ../en/ch09-undo.xml:33
8850 msgid ""
8851 "In section <xref linkend=\"sec.concepts.txn\"/>, I mentioned that Mercurial "
8852 "treats each modification of a repository as a <emphasis>transaction</"
8853 "emphasis>. Every time you commit a changeset or pull changes from another "
8854 "repository, Mercurial remembers what you did. You can undo, or "
8855 "<emphasis>roll back</emphasis>, exactly one of these actions using the "
8856 "<command role=\"hg-cmd\">hg rollback</command> command. (See section <xref "
8857 "linkend=\"sec.undo.rollback-after-push\"/> for an important caveat about the "
8858 "use of this command.)"
8859 msgstr ""
8861 #. type: Content of: <book><chapter><sect1><sect2><para>
8862 #: ../en/ch09-undo.xml:43
8863 msgid ""
8864 "Here's a mistake that I often find myself making: committing a change in "
8865 "which I've created a new file, but forgotten to <command role=\"hg-cmd\">hg "
8866 "add</command> it."
8867 msgstr ""
8869 #. type: Content of: <book><chapter><sect1><sect2><para>
8870 #: ../en/ch09-undo.xml:50
8871 msgid ""
8872 "Looking at the output of <command role=\"hg-cmd\">hg status</command> after "
8873 "the commit immediately confirms the error."
8874 msgstr ""
8876 #. type: Content of: <book><chapter><sect1><sect2><para>
8877 #: ../en/ch09-undo.xml:56
8878 msgid ""
8879 "The commit captured the changes to the file <filename>a</filename>, but not "
8880 "the new file <filename>b</filename>. If I were to push this changeset to a "
8881 "repository that I shared with a colleague, the chances are high that "
8882 "something in <filename>a</filename> would refer to <filename>b</filename>, "
8883 "which would not be present in their repository when they pulled my changes. "
8884 "I would thus become the object of some indignation."
8885 msgstr ""
8887 #. type: Content of: <book><chapter><sect1><sect2><para>
8888 #: ../en/ch09-undo.xml:65
8889 msgid ""
8890 "However, luck is with me&emdash;I've caught my error before I pushed the "
8891 "changeset. I use the <command role=\"hg-cmd\">hg rollback</command> command, "
8892 "and Mercurial makes that last changeset vanish."
8893 msgstr ""
8895 #. type: Content of: <book><chapter><sect1><sect2><para>
8896 #: ../en/ch09-undo.xml:72
8897 msgid ""
8898 "Notice that the changeset is no longer present in the repository's history, "
8899 "and the working directory once again thinks that the file <filename>a</"
8900 "filename> is modified. The commit and rollback have left the working "
8901 "directory exactly as it was prior to the commit; the changeset has been "
8902 "completely erased. I can now safely <command role=\"hg-cmd\">hg add</"
8903 "command> the file <filename>b</filename>, and rerun my commit."
8904 msgstr ""
8906 #. type: Content of: <book><chapter><sect1><sect2><title>
8907 #: ../en/ch09-undo.xml:85
8908 msgid "The erroneous pull"
8909 msgstr "错误的抓取"
8911 #. type: Content of: <book><chapter><sect1><sect2><para>
8912 #: ../en/ch09-undo.xml:87
8913 msgid ""
8914 "It's common practice with Mercurial to maintain separate development branches "
8915 "of a project in different repositories. Your development team might have one "
8916 "shared repository for your project's <quote>0.9</quote> release, and another, "
8917 "containing different changes, for the <quote>1.0</quote> release."
8918 msgstr ""
8920 #. type: Content of: <book><chapter><sect1><sect2><para>
8921 #: ../en/ch09-undo.xml:94
8922 msgid ""
8923 "Given this, you can imagine that the consequences could be messy if you had a "
8924 "local <quote>0.9</quote> repository, and accidentally pulled changes from the "
8925 "shared <quote>1.0</quote> repository into it. At worst, you could be paying "
8926 "insufficient attention, and push those changes into the shared <quote>0.9</"
8927 "quote> tree, confusing your entire team (but don't worry, we'll return to "
8928 "this horror scenario later). However, it's more likely that you'll notice "
8929 "immediately, because Mercurial will display the URL it's pulling from, or you "
8930 "will see it pull a suspiciously large number of changes into the repository."
8931 msgstr ""
8933 #. type: Content of: <book><chapter><sect1><sect2><para>
8934 #: ../en/ch09-undo.xml:106
8935 msgid ""
8936 "The <command role=\"hg-cmd\">hg rollback</command> command will work nicely "
8937 "to expunge all of the changesets that you just pulled. Mercurial groups all "
8938 "changes from one <command role=\"hg-cmd\">hg pull</command> into a single "
8939 "transaction, so one <command role=\"hg-cmd\">hg rollback</command> is all you "
8940 "need to undo this mistake."
8941 msgstr ""
8943 #. type: Content of: <book><chapter><sect1><sect2><title>
8944 #: ../en/ch09-undo.xml:115
8945 msgid "Rolling back is useless once you've pushed"
8946 msgstr "当完成推送后，回滚是无效的"
8948 #. type: Content of: <book><chapter><sect1><sect2><para>
8949 #: ../en/ch09-undo.xml:117
8950 msgid ""
8951 "The value of the <command role=\"hg-cmd\">hg rollback</command> command drops "
8952 "to zero once you've pushed your changes to another repository. Rolling back "
8953 "a change makes it disappear entirely, but <emphasis>only</emphasis> in the "
8954 "repository in which you perform the <command role=\"hg-cmd\">hg rollback</"
8955 "command>. Because a rollback eliminates history, there's no way for the "
8956 "disappearance of a change to propagate between repositories."
8957 msgstr ""
8959 #. type: Content of: <book><chapter><sect1><sect2><para>
8960 #: ../en/ch09-undo.xml:126
8961 msgid ""
8962 "If you've pushed a change to another repository&emdash;particularly if it's a "
8963 "shared repository&emdash;it has essentially <quote>escaped into the wild,</"
8964 "quote> and you'll have to recover from your mistake in a different way. What "
8965 "will happen if you push a changeset somewhere, then roll it back, then pull "
8966 "from the repository you pushed to, is that the changeset will reappear in "
8967 "your repository."
8968 msgstr ""
8970 #. type: Content of: <book><chapter><sect1><sect2><para>
8971 #: ../en/ch09-undo.xml:135
8972 msgid ""
8973 "(If you absolutely know for sure that the change you want to roll back is the "
8974 "most recent change in the repository that you pushed to, <emphasis>and</"
8975 "emphasis> you know that nobody else could have pulled it from that "
8976 "repository, you can roll back the changeset there, too, but you really should "
8977 "really not rely on this working reliably. If you do this, sooner or later a "
8978 "change really will make it into a repository that you don't directly control "
8979 "(or have forgotten about), and come back to bite you.)"
8980 msgstr ""
8982 #. type: Content of: <book><chapter><sect1><sect2><title>
8983 #: ../en/ch09-undo.xml:147
8984 msgid "You can only roll back once"
8985 msgstr "你只能回滚一次"
8987 #. type: Content of: <book><chapter><sect1><sect2><para>
8988 #: ../en/ch09-undo.xml:149
8989 msgid ""
8990 "Mercurial stores exactly one transaction in its transaction log; that "
8991 "transaction is the most recent one that occurred in the repository. This "
8992 "means that you can only roll back one transaction. If you expect to be able "
8993 "to roll back one transaction, then its predecessor, this is not the behaviour "
8994 "you will get."
8995 msgstr ""
8997 #. type: Content of: <book><chapter><sect1><sect2><para>
8998 #: ../en/ch09-undo.xml:158
8999 msgid ""
9000 "Once you've rolled back one transaction in a repository, you can't roll back "
9001 "again in that repository until you perform another commit or pull."
9002 msgstr ""
9004 #. type: Content of: <book><chapter><sect1><title>
9005 #: ../en/ch09-undo.xml:165
9006 msgid "Reverting the mistaken change"
9007 msgstr "撤销错误的修改"
9009 #. type: Content of: <book><chapter><sect1><para>
9010 #: ../en/ch09-undo.xml:167
9011 msgid ""
9012 "If you make a modification to a file, and decide that you really didn't want "
9013 "to change the file at all, and you haven't yet committed your changes, the "
9014 "<command role=\"hg-cmd\">hg revert</command> command is the one you'll need. "
9015 "It looks at the changeset that's the parent of the working directory, and "
9016 "restores the contents of the file to their state as of that changeset. "
9017 "(That's a long-winded way of saying that, in the normal case, it undoes your "
9018 "modifications.)"
9019 msgstr ""
9021 #. type: Content of: <book><chapter><sect1><para>
9022 #: ../en/ch09-undo.xml:176
9023 msgid ""
9024 "Let's illustrate how the <command role=\"hg-cmd\">hg revert</command> command "
9025 "works with yet another small example. We'll begin by modifying a file that "
9026 "Mercurial is already tracking."
9027 msgstr ""
9029 #. type: Content of: <book><chapter><sect1><para>
9030 #: ../en/ch09-undo.xml:183
9031 msgid ""
9032 "If we don't want that change, we can simply <command role=\"hg-cmd\">hg "
9033 "revert</command> the file."
9034 msgstr ""
9036 #. type: Content of: <book><chapter><sect1><para>
9037 #: ../en/ch09-undo.xml:189
9038 msgid ""
9039 "The <command role=\"hg-cmd\">hg revert</command> command provides us with an "
9040 "extra degree of safety by saving our modified file with a <filename>.orig</"
9041 "filename> extension."
9042 msgstr ""
9044 #. type: Content of: <book><chapter><sect1><para>
9045 #: ../en/ch09-undo.xml:196
9046 msgid ""
9047 "Here is a summary of the cases that the <command role=\"hg-cmd\">hg revert</"
9048 "command> command can deal with. We will describe each of these in more "
9049 "detail in the section that follows."
9050 msgstr ""
9052 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
9053 #: ../en/ch09-undo.xml:201
9054 msgid "If you modify a file, it will restore the file to its unmodified state."
9055 msgstr ""
9057 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
9058 #: ../en/ch09-undo.xml:204
9059 msgid ""
9060 "If you <command role=\"hg-cmd\">hg add</command> a file, it will undo the "
9061 "<quote>added</quote> state of the file, but leave the file itself untouched."
9062 msgstr ""
9064 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
9065 #: ../en/ch09-undo.xml:208
9066 msgid ""
9067 "If you delete a file without telling Mercurial, it will restore the file to "
9068 "its unmodified contents."
9069 msgstr ""
9071 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
9072 #: ../en/ch09-undo.xml:211
9073 msgid ""
9074 "If you use the <command role=\"hg-cmd\">hg remove</command> command to remove "
9075 "a file, it will undo the <quote>removed</quote> state of the file, and "
9076 "restore the file to its unmodified contents."
9077 msgstr ""
9079 #. type: Content of: <book><chapter><sect1><sect2><title>
9080 #: ../en/ch09-undo.xml:218
9081 msgid "File management errors"
9082 msgstr "文件管理错误"
9084 #. type: Content of: <book><chapter><sect1><sect2><para>
9085 #: ../en/ch09-undo.xml:220
9086 msgid ""
9087 "The <command role=\"hg-cmd\">hg revert</command> command is useful for more "
9088 "than just modified files. It lets you reverse the results of all of "
9089 "Mercurial's file management commands&emdash;<command role=\"hg-cmd\">hg add</"
9090 "command>, <command role=\"hg-cmd\">hg remove</command>, and so on."
9091 msgstr ""
9093 #
9094 #. type: Content of: <book><chapter><sect1><sect2><para>
9095 #: ../en/ch09-undo.xml:226
9096 msgid ""
9097 "If you <command role=\"hg-cmd\">hg add</command> a file, then decide that in "
9098 "fact you don't want Mercurial to track it, use <command role=\"hg-cmd\">hg "
9099 "revert</command> to undo the add. Don't worry; Mercurial will not modify the "
9100 "file in any way. It will just <quote>unmark</quote> the file."
9101 msgstr ""
9103 #. type: Content of: <book><chapter><sect1><sect2><para>
9104 #: ../en/ch09-undo.xml:234
9105 msgid ""
9106 "Similarly, if you ask Mercurial to <command role=\"hg-cmd\">hg remove</"
9107 "command> a file, you can use <command role=\"hg-cmd\">hg revert</command> to "
9108 "restore it to the contents it had as of the parent of the working directory. "
9109 "&interaction.daily.revert.remove; This works just as well for a file that you "
9110 "deleted by hand, without telling Mercurial (recall that in Mercurial "
9111 "terminology, this kind of file is called <quote>missing</quote>)."
9112 msgstr ""
9114 #
9115 #. type: Content of: <book><chapter><sect1><sect2><para>
9116 #: ../en/ch09-undo.xml:245
9117 msgid ""
9118 "If you revert a <command role=\"hg-cmd\">hg copy</command>, the copied-to "
9119 "file remains in your working directory afterwards, untracked. Since a copy "
9120 "doesn't affect the copied-from file in any way, Mercurial doesn't do anything "
9121 "with the copied-from file."
9122 msgstr ""
9124 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
9125 #: ../en/ch09-undo.xml:254
9126 msgid "A slightly special case: reverting a rename"
9127 msgstr "一个稍微特别的案例：撤销改名"
9129 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
9130 #: ../en/ch09-undo.xml:256
9131 msgid ""
9132 "If you <command role=\"hg-cmd\">hg rename</command> a file, there is one "
9133 "small detail that you should remember. When you <command role=\"hg-cmd\">hg "
9134 "revert</command> a rename, it's not enough to provide the name of the renamed-"
9135 "to file, as you can see here."
9136 msgstr ""
9138 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
9139 #: ../en/ch09-undo.xml:264
9140 msgid ""
9141 "As you can see from the output of <command role=\"hg-cmd\">hg status</"
9142 "command>, the renamed-to file is no longer identified as added, but the "
9143 "renamed-<emphasis>from</emphasis> file is still removed! This is counter-"
9144 "intuitive (at least to me), but at least it's easy to deal with."
9145 msgstr ""
9147 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
9148 #: ../en/ch09-undo.xml:273
9149 msgid ""
9150 "So remember, to revert a <command role=\"hg-cmd\">hg rename</command>, you "
9151 "must provide <emphasis>both</emphasis> the source and destination names."
9152 msgstr ""
9154 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
9155 #: ../en/ch09-undo.xml:278
9156 msgid "% TODO: the output doesn't look like it will be removed!"
9157 msgstr ""
9159 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
9160 #: ../en/ch09-undo.xml:281
9161 msgid ""
9162 "(By the way, if you rename a file, then modify the renamed-to file, then "
9163 "revert both components of the rename, when Mercurial restores the file that "
9164 "was removed as part of the rename, it will be unmodified. If you need the "
9165 "modifications in the renamed-to file to show up in the renamed-from file, "
9166 "don't forget to copy them over.)"
9167 msgstr ""
9169 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
9170 #: ../en/ch09-undo.xml:288
9171 msgid ""
9172 "These fiddly aspects of reverting a rename arguably constitute a small bug in "
9173 "Mercurial."
9174 msgstr ""
9176 #. type: Content of: <book><chapter><sect1><title>
9177 #: ../en/ch09-undo.xml:295
9178 msgid "Dealing with committed changes"
9179 msgstr "处理已经提交的修改"
9181 #. type: Content of: <book><chapter><sect1><para>
9182 #: ../en/ch09-undo.xml:297
9183 msgid ""
9184 "Consider a case where you have committed a change $a$, and another change $b$ "
9185 "on top of it; you then realise that change $a$ was incorrect. Mercurial lets "
9186 "you <quote>back out</quote> an entire changeset automatically, and building "
9187 "blocks that let you reverse part of a changeset by hand."
9188 msgstr ""
9190 #. type: Content of: <book><chapter><sect1><para>
9191 #: ../en/ch09-undo.xml:303
9192 msgid ""
9193 "Before you read this section, here's something to keep in mind: the <command "
9194 "role=\"hg-cmd\">hg backout</command> command undoes changes by "
9195 "<emphasis>adding</emphasis> history, not by modifying or erasing it. It's "
9196 "the right tool to use if you're fixing bugs, but not if you're trying to undo "
9197 "some change that has catastrophic consequences. To deal with those, see "
9198 "section <xref linkend=\"sec.undo.aaaiiieee\"/>."
9199 msgstr ""
9201 #. type: Content of: <book><chapter><sect1><sect2><title>
9202 #: ../en/ch09-undo.xml:312
9203 msgid "Backing out a changeset"
9204 msgstr "恢复一个修改集"
9206 #. type: Content of: <book><chapter><sect1><sect2><para>
9207 #: ../en/ch09-undo.xml:314
9208 msgid ""
9209 "The <command role=\"hg-cmd\">hg backout</command> command lets you "
9210 "<quote>undo</quote> the effects of an entire changeset in an automated "
9211 "fashion. Because Mercurial's history is immutable, this command "
9212 "<emphasis>does not</emphasis> get rid of the changeset you want to undo. "
9213 "Instead, it creates a new changeset that <emphasis>reverses</emphasis> the "
9214 "effect of the to-be-undone changeset."
9215 msgstr ""
9217 #
9218 #. type: Content of: <book><chapter><sect1><sect2><para>
9219 #: ../en/ch09-undo.xml:323
9220 msgid ""
9221 "The operation of the <command role=\"hg-cmd\">hg backout</command> command is "
9222 "a little intricate, so let's illustrate it with some examples. First, we'll "
9223 "create a repository with some simple changes."
9224 msgstr ""
9226 #. type: Content of: <book><chapter><sect1><sect2><para>
9227 #: ../en/ch09-undo.xml:330
9228 msgid ""
9229 "The <command role=\"hg-cmd\">hg backout</command> command takes a single "
9230 "changeset ID as its argument; this is the changeset to back out. Normally, "
9231 "<command role=\"hg-cmd\">hg backout</command> will drop you into a text "
9232 "editor to write a commit message, so you can record why you're backing the "
9233 "change out. In this example, we provide a commit message on the command line "
9234 "using the <option role=\"hg-opt-backout\">-m</option> option."
9235 msgstr ""
9237 #. type: Content of: <book><chapter><sect1><sect2><title>
9238 #: ../en/ch09-undo.xml:341
9239 msgid "Backing out the tip changeset"
9240 msgstr "恢复顶点修改集"
9242 #. type: Content of: <book><chapter><sect1><sect2><para>
9243 #: ../en/ch09-undo.xml:343
9244 msgid "We're going to start by backing out the last changeset we committed."
9245 msgstr ""
9247 #. type: Content of: <book><chapter><sect1><sect2><para>
9248 #: ../en/ch09-undo.xml:348
9249 msgid ""
9250 "You can see that the second line from <filename>myfile</filename> is no "
9251 "longer present. Taking a look at the output of <command role=\"hg-cmd\">hg "
9252 "log</command> gives us an idea of what the <command role=\"hg-cmd\">hg "
9253 "backout</command> command has done. &interaction.backout.simple.log; Notice "
9254 "that the new changeset that <command role=\"hg-cmd\">hg backout</command> has "
9255 "created is a child of the changeset we backed out. It's easier to see this "
9256 "in figure <xref endterm=\"fig.undo.backout.caption\" linkend=\"fig.undo."
9257 "backout\"/>, which presents a graphical view of the change history. As you "
9258 "can see, the history is nice and linear."
9259 msgstr ""
9261 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
9262 #: ../en/ch09-undo.xml:364
9263 msgid ""
9264 "<imageobject><imagedata fileref=\"images/undo-simple.png\"/> </imageobject>"
9265 msgstr ""
9267 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
9268 #: ../en/ch09-undo.xml:367 ../en/ch09-undo.xml:486
9269 msgid ""
9270 "Backing out a change using the <command role=\"hg-cmd\">hg backout</command> "
9271 "command"
9272 msgstr ""
9274 #. type: Content of: <book><chapter><sect1><sect2><title>
9275 #: ../en/ch09-undo.xml:376
9276 msgid "Backing out a non-tip change"
9277 msgstr "恢复非顶点的修改"
9279 #. type: Content of: <book><chapter><sect1><sect2><para>
9280 #: ../en/ch09-undo.xml:378
9281 msgid ""
9282 "If you want to back out a change other than the last one you committed, pass "
9283 "the <option role=\"hg-opt-backout\">--merge</option> option to the <command "
9284 "role=\"hg-cmd\">hg backout</command> command."
9285 msgstr ""
9287 #. type: Content of: <book><chapter><sect1><sect2><para>
9288 #: ../en/ch09-undo.xml:385
9289 msgid ""
9290 "This makes backing out any changeset a <quote>one-shot</quote> operation "
9291 "that's usually simple and fast."
9292 msgstr ""
9294 #. type: Content of: <book><chapter><sect1><sect2><para>
9295 #: ../en/ch09-undo.xml:391
9296 msgid ""
9297 "If you take a look at the contents of <filename>myfile</filename> after the "
9298 "backout finishes, you'll see that the first and third changes are present, "
9299 "but not the second."
9300 msgstr ""
9302 #. type: Content of: <book><chapter><sect1><sect2><para>
9303 #: ../en/ch09-undo.xml:398
9304 msgid ""
9305 "As the graphical history in figure <xref endterm=\"fig.undo.backout-non-tip."
9306 "caption\" linkend=\"fig.undo.backout-non-tip\"/> illustrates, Mercurial "
9307 "actually commits <emphasis>two</emphasis> changes in this kind of situation "
9308 "(the box-shaped nodes are the ones that Mercurial commits automatically). "
9309 "Before Mercurial begins the backout process, it first remembers what the "
9310 "current parent of the working directory is. It then backs out the target "
9311 "changeset, and commits that as a changeset. Finally, it merges back to the "
9312 "previous parent of the working directory, and commits the result of the merge."
9313 msgstr ""
9315 #. type: Content of: <book><chapter><sect1><sect2><para>
9316 #: ../en/ch09-undo.xml:410
9317 msgid ""
9318 "% TODO: to me it looks like mercurial doesn't commit the second merge "
9319 "automatically!"
9320 msgstr ""
9322 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
9323 #: ../en/ch09-undo.xml:415
9324 msgid ""
9325 "<imageobject><imagedata fileref=\"images/undo-non-tip.png\"/> </imageobject>"
9326 msgstr ""
9328 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
9329 #: ../en/ch09-undo.xml:418
9330 msgid ""
9331 "Automated backout of a non-tip change using the <command role=\"hg-cmd\">hg "
9332 "backout</command> command"
9333 msgstr ""
9335 #. type: Content of: <book><chapter><sect1><sect2><para>
9336 #: ../en/ch09-undo.xml:424
9337 msgid ""
9338 "The result is that you end up <quote>back where you were</quote>, only with "
9339 "some extra history that undoes the effect of the changeset you wanted to back "
9340 "out."
9341 msgstr ""
9343 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
9344 #: ../en/ch09-undo.xml:429
9345 msgid "Always use the <option role=\"hg-opt-backout\">--merge</option> option"
9346 msgstr "始终使用选项 <option role=\"hg-opt-backout\">--merge</option>"
9348 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
9349 #: ../en/ch09-undo.xml:432
9350 msgid ""
9351 "In fact, since the <option role=\"hg-opt-backout\">--merge</option> option "
9352 "will do the <quote>right thing</quote> whether or not the changeset you're "
9353 "backing out is the tip (i.e. it won't try to merge if it's backing out the "
9354 "tip, since there's no need), you should <emphasis>always</emphasis> use this "
9355 "option when you run the <command role=\"hg-cmd\">hg backout</command> command."
9356 msgstr ""
9358 #. type: Content of: <book><chapter><sect1><sect2><title>
9359 #: ../en/ch09-undo.xml:443
9360 msgid "Gaining more control of the backout process"
9361 msgstr "在恢复处理中获得更多控制"
9363 #. type: Content of: <book><chapter><sect1><sect2><para>
9364 #: ../en/ch09-undo.xml:445
9365 msgid ""
9366 "While I've recommended that you always use the <option role=\"hg-opt-backout"
9367 "\">--merge</option> option when backing out a change, the <command role=\"hg-"
9368 "cmd\">hg backout</command> command lets you decide how to merge a backout "
9369 "changeset. Taking control of the backout process by hand is something you "
9370 "will rarely need to do, but it can be useful to understand what the <command "
9371 "role=\"hg-cmd\">hg backout</command> command is doing for you automatically. "
9372 "To illustrate this, let's clone our first repository, but omit the backout "
9373 "change that it contains."
9374 msgstr ""
9376 #. type: Content of: <book><chapter><sect1><sect2><para>
9377 #: ../en/ch09-undo.xml:458
9378 msgid ""
9379 "As with our earlier example, We'll commit a third changeset, then back out "
9380 "its parent, and see what happens."
9381 msgstr ""
9383 #. type: Content of: <book><chapter><sect1><sect2><para>
9384 #: ../en/ch09-undo.xml:464
9385 msgid ""
9386 "Our new changeset is again a descendant of the changeset we backout out; it's "
9387 "thus a new head, <emphasis>not</emphasis> a descendant of the changeset that "
9388 "was the tip. The <command role=\"hg-cmd\">hg backout</command> command was "
9389 "quite explicit in telling us this."
9390 msgstr ""
9392 #. type: Content of: <book><chapter><sect1><sect2><para>
9393 #: ../en/ch09-undo.xml:472
9394 msgid ""
9395 "Again, it's easier to see what has happened by looking at a graph of the "
9396 "revision history, in figure <xref endterm=\"fig.undo.backout-manual.caption\" "
9397 "linkend=\"fig.undo.backout-manual\"/>. This makes it clear that when we use "
9398 "<command role=\"hg-cmd\">hg backout</command> to back out a change other than "
9399 "the tip, Mercurial adds a new head to the repository (the change it committed "
9400 "is box-shaped)."
9401 msgstr ""
9403 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
9404 #: ../en/ch09-undo.xml:483
9405 msgid ""
9406 "<imageobject><imagedata fileref=\"images/undo-manual.png\"/> </imageobject>"
9407 msgstr ""
9409 #. type: Content of: <book><chapter><sect1><sect2><para>
9410 #: ../en/ch09-undo.xml:492
9411 msgid ""
9412 "After the <command role=\"hg-cmd\">hg backout</command> command has "
9413 "completed, it leaves the new <quote>backout</quote> changeset as the parent "
9414 "of the working directory."
9415 msgstr ""
9417 #. type: Content of: <book><chapter><sect1><sect2><para>
9418 #: ../en/ch09-undo.xml:499
9419 msgid "Now we have two isolated sets of changes."
9420 msgstr ""
9422 #. type: Content of: <book><chapter><sect1><sect2><para>
9423 #: ../en/ch09-undo.xml:503
9424 msgid ""
9425 "Let's think about what we expect to see as the contents of <filename>myfile</"
9426 "filename> now. The first change should be present, because we've never "
9427 "backed it out. The second change should be missing, as that's the change we "
9428 "backed out. Since the history graph shows the third change as a separate "
9429 "head, we <emphasis>don't</emphasis> expect to see the third change present in "
9430 "<filename>myfile</filename>."
9431 msgstr ""
9433 #. type: Content of: <book><chapter><sect1><sect2><para>
9434 #: ../en/ch09-undo.xml:513
9435 msgid ""
9436 "To get the third change back into the file, we just do a normal merge of our "
9437 "two heads."
9438 msgstr ""
9440 #. type: Content of: <book><chapter><sect1><sect2><para>
9441 #: ../en/ch09-undo.xml:518
9442 msgid ""
9443 "Afterwards, the graphical history of our repository looks like figure <xref "
9444 "endterm=\"fig.undo.backout-manual-merge.caption\" linkend=\"fig.undo.backout-"
9445 "manual-merge\"/>."
9446 msgstr ""
9448 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
9449 #: ../en/ch09-undo.xml:525
9450 msgid ""
9451 "<imageobject><imagedata fileref=\"images/undo-manual-merge.png\"/> </"
9452 "imageobject>"
9453 msgstr ""
9455 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
9456 #: ../en/ch09-undo.xml:528
9457 msgid "Manually merging a backout change"
9458 msgstr ""
9460 #. type: Content of: <book><chapter><sect1><sect2><title>
9461 #: ../en/ch09-undo.xml:535
9462 msgid "Why <command role=\"hg-cmd\">hg backout</command> works as it does"
9463 msgstr "<command role=\"hg-cmd\">hg backout</command> 的内幕"
9465 #. type: Content of: <book><chapter><sect1><sect2><para>
9466 #: ../en/ch09-undo.xml:538
9467 msgid ""
9468 "Here's a brief description of how the <command role=\"hg-cmd\">hg backout</"
9469 "command> command works."
9470 msgstr ""
9472 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9473 #: ../en/ch09-undo.xml:541
9474 msgid ""
9475 "It ensures that the working directory is <quote>clean</quote>, i.e. that the "
9476 "output of <command role=\"hg-cmd\">hg status</command> would be empty."
9477 msgstr ""
9479 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9480 #: ../en/ch09-undo.xml:545
9481 msgid ""
9482 "It remembers the current parent of the working directory. Let's call this "
9483 "changeset <literal>orig</literal>"
9484 msgstr ""
9486 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9487 #: ../en/ch09-undo.xml:549
9488 msgid ""
9489 "It does the equivalent of a <command role=\"hg-cmd\">hg update</command> to "
9490 "sync the working directory to the changeset you want to back out. Let's call "
9491 "this changeset <literal>backout</literal>"
9492 msgstr ""
9494 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9495 #: ../en/ch09-undo.xml:554
9496 msgid ""
9497 "It finds the parent of that changeset. Let's call that changeset "
9498 "<literal>parent</literal>."
9499 msgstr ""
9501 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9502 #: ../en/ch09-undo.xml:557
9503 msgid ""
9504 "For each file that the <literal>backout</literal> changeset affected, it does "
9505 "the equivalent of a <command role=\"hg-cmd\">hg revert -r parent</command> on "
9506 "that file, to restore it to the contents it had before that changeset was "
9507 "committed."
9508 msgstr ""
9510 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9511 #: ../en/ch09-undo.xml:564
9512 msgid ""
9513 "It commits the result as a new changeset. This changeset has "
9514 "<literal>backout</literal> as its parent."
9515 msgstr ""
9517 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9518 #: ../en/ch09-undo.xml:568
9519 msgid ""
9520 "If you specify <option role=\"hg-opt-backout\">--merge</option> on the "
9521 "command line, it merges with <literal>orig</literal>, and commits the result "
9522 "of the merge."
9523 msgstr ""
9525 #. type: Content of: <book><chapter><sect1><sect2><para>
9526 #: ../en/ch09-undo.xml:574
9527 msgid ""
9528 "An alternative way to implement the <command role=\"hg-cmd\">hg backout</"
9529 "command> command would be to <command role=\"hg-cmd\">hg export</command> the "
9530 "to-be-backed-out changeset as a diff, then use the <option role=\"cmd-opt-"
9531 "patch\">--reverse</option> option to the <command>patch</command> command to "
9532 "reverse the effect of the change without fiddling with the working "
9533 "directory. This sounds much simpler, but it would not work nearly as well."
9534 msgstr ""
9536 #. type: Content of: <book><chapter><sect1><sect2><para>
9537 #: ../en/ch09-undo.xml:584
9538 msgid ""
9539 "The reason that <command role=\"hg-cmd\">hg backout</command> does an update, "
9540 "a commit, a merge, and another commit is to give the merge machinery the best "
9541 "chance to do a good job when dealing with all the changes <emphasis>between</"
9542 "emphasis> the change you're backing out and the current tip."
9543 msgstr ""
9545 #. type: Content of: <book><chapter><sect1><sect2><para>
9546 #: ../en/ch09-undo.xml:591
9547 msgid ""
9548 "If you're backing out a changeset that's 100 revisions back in your project's "
9549 "history, the chances that the <command>patch</command> command will be able "
9550 "to apply a reverse diff cleanly are not good, because intervening changes are "
9551 "likely to have <quote>broken the context</quote> that <command>patch</"
9552 "command> uses to determine whether it can apply a patch (if this sounds like "
9553 "gibberish, see <xref linkend=\"sec.mq.patch\"/> for a discussion of the "
9554 "<command>patch</command> command). Also, Mercurial's merge machinery will "
9555 "handle files and directories being renamed, permission changes, and "
9556 "modifications to binary files, none of which <command>patch</command> can "
9557 "deal with."
9558 msgstr ""
9560 #. type: Content of: <book><chapter><sect1><title>
9561 #: ../en/ch09-undo.xml:608
9562 msgid "Changes that should never have been"
9563 msgstr "不该发生的修改"
9565 #. type: Content of: <book><chapter><sect1><para>
9566 #: ../en/ch09-undo.xml:610
9567 msgid ""
9568 "Most of the time, the <command role=\"hg-cmd\">hg backout</command> command "
9569 "is exactly what you need if you want to undo the effects of a change. It "
9570 "leaves a permanent record of exactly what you did, both when committing the "
9571 "original changeset and when you cleaned up after it."
9572 msgstr ""
9574 #. type: Content of: <book><chapter><sect1><para>
9575 #: ../en/ch09-undo.xml:616
9576 msgid ""
9577 "On rare occasions, though, you may find that you've committed a change that "
9578 "really should not be present in the repository at all. For example, it would "
9579 "be very unusual, and usually considered a mistake, to commit a software "
9580 "project's object files as well as its source files. Object files have almost "
9581 "no intrinsic value, and they're <emphasis>big</emphasis>, so they increase "
9582 "the size of the repository and the amount of time it takes to clone or pull "
9583 "changes."
9584 msgstr ""
9586 #. type: Content of: <book><chapter><sect1><para>
9587 #: ../en/ch09-undo.xml:625
9588 msgid ""
9589 "Before I discuss the options that you have if you commit a <quote>brown paper "
9590 "bag</quote> change (the kind that's so bad that you want to pull a brown "
9591 "paper bag over your head), let me first discuss some approaches that probably "
9592 "won't work."
9593 msgstr ""
9595 #. type: Content of: <book><chapter><sect1><para>
9596 #: ../en/ch09-undo.xml:630
9597 msgid ""
9598 "Since Mercurial treats history as accumulative&emdash;every change builds on "
9599 "top of all changes that preceded it&emdash;you generally can't just make "
9600 "disastrous changes disappear. The one exception is when you've just "
9601 "committed a change, and it hasn't been pushed or pulled into another "
9602 "repository. That's when you can safely use the <command role=\"hg-cmd\">hg "
9603 "rollback</command> command, as I detailed in section <xref linkend=\"sec.undo."
9604 "rollback\"/>."
9605 msgstr ""
9607 #. type: Content of: <book><chapter><sect1><para>
9608 #: ../en/ch09-undo.xml:639
9609 msgid ""
9610 "After you've pushed a bad change to another repository, you <emphasis>could</"
9611 "emphasis> still use <command role=\"hg-cmd\">hg rollback</command> to make "
9612 "your local copy of the change disappear, but it won't have the consequences "
9613 "you want. The change will still be present in the remote repository, so it "
9614 "will reappear in your local repository the next time you pull."
9615 msgstr ""
9617 #. type: Content of: <book><chapter><sect1><para>
9618 #: ../en/ch09-undo.xml:647
9619 msgid ""
9620 "If a situation like this arises, and you know which repositories your bad "
9621 "change has propagated into, you can <emphasis>try</emphasis> to get rid of "
9622 "the changeefrom <emphasis>every</emphasis> one of those repositories. This "
9623 "is, of course, not a satisfactory solution: if you miss even a single "
9624 "repository while you're expunging, the change is still <quote>in the wild</"
9625 "quote>, and could propagate further."
9626 msgstr ""
9628 #. type: Content of: <book><chapter><sect1><para>
9629 #: ../en/ch09-undo.xml:655
9630 msgid ""
9631 "If you've committed one or more changes <emphasis>after</emphasis> the change "
9632 "that you'd like to see disappear, your options are further reduced. Mercurial "
9633 "doesn't provide a way to <quote>punch a hole</quote> in history, leaving "
9634 "changesets intact."
9635 msgstr ""
9637 #. type: Content of: <book><chapter><sect1><para>
9638 #: ../en/ch09-undo.xml:661
9639 msgid ""
9640 "XXX This needs filling out. The <literal>hg-replay</literal> script in the "
9641 "<literal>examples</literal> directory works, but doesn't handle merge "
9642 "changesets. Kind of an important omission."
9643 msgstr ""
9645 #. type: Content of: <book><chapter><sect1><sect2><title>
9646 #: ../en/ch09-undo.xml:667
9647 msgid "Protect yourself from <quote>escaped</quote> changes"
9648 msgstr "使用<quote>校验</quote>修改来保护你自己"
9650 #. type: Content of: <book><chapter><sect1><sect2><para>
9651 #: ../en/ch09-undo.xml:670
9652 msgid ""
9653 "If you've committed some changes to your local repository and they've been "
9654 "pushed or pulled somewhere else, this isn't necessarily a disaster. You can "
9655 "protect yourself ahead of time against some classes of bad changeset. This "
9656 "is particularly easy if your team usually pulls changes from a central "
9657 "repository."
9658 msgstr ""
9660 #. type: Content of: <book><chapter><sect1><sect2><para>
9661 #: ../en/ch09-undo.xml:677
9662 msgid ""
9663 "By configuring some hooks on that repository to validate incoming changesets "
9664 "(see chapter <xref linkend=\"chap.hook\"/>), you can automatically prevent "
9665 "some kinds of bad changeset from being pushed to the central repository at "
9666 "all. With such a configuration in place, some kinds of bad changeset will "
9667 "naturally tend to <quote>die out</quote> because they can't propagate into "
9668 "the central repository. Better yet, this happens without any need for "
9669 "explicit intervention."
9670 msgstr ""
9672 #. type: Content of: <book><chapter><sect1><sect2><para>
9673 #: ../en/ch09-undo.xml:687
9674 msgid ""
9675 "For instance, an incoming change hook that verifies that a changeset will "
9676 "actually compile can prevent people from inadvertantly <quote>breaking the "
9677 "build</quote>."
9678 msgstr ""
9680 #. type: Content of: <book><chapter><sect1><title>
9681 #: ../en/ch09-undo.xml:694
9682 msgid "Finding the source of a bug"
9683 msgstr "查找问题的根源"
9685 #. type: Content of: <book><chapter><sect1><para>
9686 #: ../en/ch09-undo.xml:696
9687 msgid ""
9688 "While it's all very well to be able to back out a changeset that introduced a "
9689 "bug, this requires that you know which changeset to back out. Mercurial "
9690 "provides an invaluable command, called <command role=\"hg-cmd\">hg bisect</"
9691 "command>, that helps you to automate this process and accomplish it very "
9692 "efficiently."
9693 msgstr ""
9695 #. type: Content of: <book><chapter><sect1><para>
9696 #: ../en/ch09-undo.xml:703
9697 msgid ""
9698 "The idea behind the <command role=\"hg-cmd\">hg bisect</command> command is "
9699 "that a changeset has introduced some change of behaviour that you can "
9700 "identify with a simple binary test. You don't know which piece of code "
9701 "introduced the change, but you know how to test for the presence of the bug. "
9702 "The <command role=\"hg-cmd\">hg bisect</command> command uses your test to "
9703 "direct its search for the changeset that introduced the code that caused the "
9704 "bug."
9705 msgstr ""
9707 #. type: Content of: <book><chapter><sect1><para>
9708 #: ../en/ch09-undo.xml:712
9709 msgid ""
9710 "Here are a few scenarios to help you understand how you might apply this "
9711 "command."
9712 msgstr ""
9714 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
9715 #: ../en/ch09-undo.xml:715
9716 msgid ""
9717 "The most recent version of your software has a bug that you remember wasn't "
9718 "present a few weeks ago, but you don't know when it was introduced. Here, "
9719 "your binary test checks for the presence of that bug."
9720 msgstr ""
9722 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
9723 #: ../en/ch09-undo.xml:720
9724 msgid ""
9725 "You fixed a bug in a rush, and now it's time to close the entry in your "
9726 "team's bug database. The bug database requires a changeset ID when you close "
9727 "an entry, but you don't remember which changeset you fixed the bug in. Once "
9728 "again, your binary test checks for the presence of the bug."
9729 msgstr ""
9731 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
9732 #: ../en/ch09-undo.xml:727
9733 msgid ""
9734 "Your software works correctly, but runs 15% slower than the last time you "
9735 "measured it. You want to know which changeset introduced the performance "
9736 "regression. In this case, your binary test measures the performance of your "
9737 "software, to see whether it's <quote>fast</quote> or <quote>slow</quote>."
9738 msgstr ""
9740 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
9741 #: ../en/ch09-undo.xml:734
9742 msgid ""
9743 "The sizes of the components of your project that you ship exploded recently, "
9744 "and you suspect that something changed in the way you build your project."
9745 msgstr ""
9747 #. type: Content of: <book><chapter><sect1><para>
9748 #: ../en/ch09-undo.xml:739
9749 msgid ""
9750 "From these examples, it should be clear that the <command role=\"hg-cmd\">hg "
9751 "bisect</command> command is not useful only for finding the sources of bugs. "
9752 "You can use it to find any <quote>emergent property</quote> of a repository "
9753 "(anything that you can't find from a simple text search of the files in the "
9754 "tree) for which you can write a binary test."
9755 msgstr ""
9757 #. type: Content of: <book><chapter><sect1><para>
9758 #: ../en/ch09-undo.xml:746
9759 msgid ""
9760 "We'll introduce a little bit of terminology here, just to make it clear which "
9761 "parts of the search process are your responsibility, and which are "
9762 "Mercurial's. A <emphasis>test</emphasis> is something that <emphasis>you</"
9763 "emphasis> run when <command role=\"hg-cmd\">hg bisect</command> chooses a "
9764 "changeset. A <emphasis>probe</emphasis> is what <command role=\"hg-cmd\">hg "
9765 "bisect</command> runs to tell whether a revision is good. Finally, we'll use "
9766 "the word <quote>bisect</quote>, as both a noun and a verb, to stand in for "
9767 "the phrase <quote>search using the <command role=\"hg-cmd\">hg bisect</"
9768 "command> command</quote>."
9769 msgstr ""
9771 #. type: Content of: <book><chapter><sect1><para>
9772 #: ../en/ch09-undo.xml:759
9773 msgid ""
9774 "One simple way to automate the searching process would be simply to probe "
9775 "every changeset. However, this scales poorly. If it took ten minutes to "
9776 "test a single changeset, and you had 10,000 changesets in your repository, "
9777 "the exhaustive approach would take on average 35 <emphasis>days</emphasis> to "
9778 "find the changeset that introduced a bug. Even if you knew that the bug was "
9779 "introduced by one of the last 500 changesets, and limited your search to "
9780 "those, you'd still be looking at over 40 hours to find the changeset that "
9781 "introduced your bug."
9782 msgstr ""
9784 #. type: Content of: <book><chapter><sect1><para>
9785 #: ../en/ch09-undo.xml:769
9786 msgid ""
9787 "What the <command role=\"hg-cmd\">hg bisect</command> command does is use its "
9788 "knowledge of the <quote>shape</quote> of your project's revision history to "
9789 "perform a search in time proportional to the <emphasis>logarithm</emphasis> "
9790 "of the number of changesets to check (the kind of search it performs is "
9791 "called a dichotomic search). With this approach, searching through 10,000 "
9792 "changesets will take less than three hours, even at ten minutes per test (the "
9793 "search will require about 14 tests). Limit your search to the last hundred "
9794 "changesets, and it will take only about an hour (roughly seven tests)."
9795 msgstr ""
9797 #. type: Content of: <book><chapter><sect1><para>
9798 #: ../en/ch09-undo.xml:780
9799 msgid ""
9800 "The <command role=\"hg-cmd\">hg bisect</command> command is aware of the "
9801 "<quote>branchy</quote> nature of a Mercurial project's revision history, so "
9802 "it has no problems dealing with branches, merges, or multiple heads in a "
9803 "repository. It can prune entire branches of history with a single probe, "
9804 "which is how it operates so efficiently."
9805 msgstr ""
9807 #. type: Content of: <book><chapter><sect1><sect2><title>
9808 #: ../en/ch09-undo.xml:788
9809 msgid "Using the <command role=\"hg-cmd\">hg bisect</command> command"
9810 msgstr "使用命令 <command role=\"hg-cmd\">hg bisect</command>"
9812 #. type: Content of: <book><chapter><sect1><sect2><para>
9813 #: ../en/ch09-undo.xml:791
9814 msgid ""
9815 "Here's an example of <command role=\"hg-cmd\">hg bisect</command> in action."
9816 msgstr ""
9818 #. type: Content of: <book><chapter><sect1><sect2><note><para>
9819 #: ../en/ch09-undo.xml:795
9820 msgid ""
9821 "In versions 0.9.5 and earlier of Mercurial, <command role=\"hg-cmd\">hg "
9822 "bisect</command> was not a core command: it was distributed with Mercurial as "
9823 "an extension. This section describes the built-in command, not the old "
9824 "extension."
9825 msgstr ""
9827 #. type: Content of: <book><chapter><sect1><sect2><para>
9828 #: ../en/ch09-undo.xml:802
9829 msgid ""
9830 "Now let's create a repository, so that we can try out the <command role=\"hg-"
9831 "cmd\">hg bisect</command> command in isolation."
9832 msgstr ""
9834 #. type: Content of: <book><chapter><sect1><sect2><para>
9835 #: ../en/ch09-undo.xml:808
9836 msgid ""
9837 "We'll simulate a project that has a bug in it in a simple-minded way: create "
9838 "trivial changes in a loop, and nominate one specific change that will have "
9839 "the <quote>bug</quote>. This loop creates 35 changesets, each adding a "
9840 "single file to the repository. We'll represent our <quote>bug</quote> with a "
9841 "file that contains the text <quote>i have a gub</quote>."
9842 msgstr ""
9844 #. type: Content of: <book><chapter><sect1><sect2><para>
9845 #: ../en/ch09-undo.xml:818
9846 msgid ""
9847 "The next thing that we'd like to do is figure out how to use the <command "
9848 "role=\"hg-cmd\">hg bisect</command> command. We can use Mercurial's normal "
9849 "built-in help mechanism for this."
9850 msgstr ""
9852 #. type: Content of: <book><chapter><sect1><sect2><para>
9853 #: ../en/ch09-undo.xml:825
9854 msgid ""
9855 "The <command role=\"hg-cmd\">hg bisect</command> command works in steps. "
9856 "Each step proceeds as follows."
9857 msgstr ""
9859 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9860 #: ../en/ch09-undo.xml:828
9861 msgid "You run your binary test."
9862 msgstr ""
9864 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><itemizedlist><listitem><para>
9865 #: ../en/ch09-undo.xml:830
9866 msgid ""
9867 "If the test succeeded, you tell <command role=\"hg-cmd\">hg bisect</command> "
9868 "by running the <command role=\"hg-cmd\">hg bisect good</command> command."
9869 msgstr ""
9871 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><itemizedlist><listitem><para>
9872 #: ../en/ch09-undo.xml:835
9873 msgid ""
9874 "If it failed, run the <command role=\"hg-cmd\">hg bisect bad</command> "
9875 "command."
9876 msgstr ""
9878 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9879 #: ../en/ch09-undo.xml:839
9880 msgid ""
9881 "The command uses your information to decide which changeset to test next."
9882 msgstr ""
9884 #. type: Content of: <book><chapter><sect1><sect2><orderedlist><listitem><para>
9885 #: ../en/ch09-undo.xml:842
9886 msgid ""
9887 "It updates the working directory to that changeset, and the process begins "
9888 "again."
9889 msgstr ""
9891 #. type: Content of: <book><chapter><sect1><sect2><para>
9892 #: ../en/ch09-undo.xml:845
9893 msgid ""
9894 "The process ends when <command role=\"hg-cmd\">hg bisect</command> identifies "
9895 "a unique changeset that marks the point where your test transitioned from "
9896 "<quote>succeeding</quote> to <quote>failing</quote>."
9897 msgstr ""
9899 #
9900 #. type: Content of: <book><chapter><sect1><sect2><para>
9901 #: ../en/ch09-undo.xml:850
9902 msgid ""
9903 "To start the search, we must run the <command role=\"hg-cmd\">hg bisect --"
9904 "reset</command> command."
9905 msgstr ""
9907 #. type: Content of: <book><chapter><sect1><sect2><para>
9908 #: ../en/ch09-undo.xml:855
9909 msgid ""
9910 "In our case, the binary test we use is simple: we check to see if any file in "
9911 "the repository contains the string <quote>i have a gub</quote>. If it does, "
9912 "this changeset contains the change that <quote>caused the bug</quote>. By "
9913 "convention, a changeset that has the property we're searching for is "
9914 "<quote>bad</quote>, while one that doesn't is <quote>good</quote>."
9915 msgstr ""
9917 #. type: Content of: <book><chapter><sect1><sect2><para>
9918 #: ../en/ch09-undo.xml:863
9919 msgid ""
9920 "Most of the time, the revision to which the working directory is synced "
9921 "(usually the tip) already exhibits the problem introduced by the buggy "
9922 "change, so we'll mark it as <quote>bad</quote>."
9923 msgstr ""
9925 #
9926 #. type: Content of: <book><chapter><sect1><sect2><para>
9927 #: ../en/ch09-undo.xml:870
9928 msgid ""
9929 "Our next task is to nominate a changeset that we know <emphasis>doesn't</"
9930 "emphasis> have the bug; the <command role=\"hg-cmd\">hg bisect</command> "
9931 "command will <quote>bracket</quote> its search between the first pair of good "
9932 "and bad changesets. In our case, we know that revision 10 didn't have the "
9933 "bug. (I'll have more words about choosing the first <quote>good</quote> "
9934 "changeset later.)"
9935 msgstr ""
9937 #. type: Content of: <book><chapter><sect1><sect2><para>
9938 #: ../en/ch09-undo.xml:880
9939 msgid "Notice that this command printed some output."
9940 msgstr ""
9942 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
9943 #: ../en/ch09-undo.xml:882
9944 msgid ""
9945 "It told us how many changesets it must consider before it can identify the "
9946 "one that introduced the bug, and how many tests that will require."
9947 msgstr ""
9949 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
9950 #: ../en/ch09-undo.xml:886
9951 msgid ""
9952 "It updated the working directory to the next changeset to test, and told us "
9953 "which changeset it's testing."
9954 msgstr ""
9956 #. type: Content of: <book><chapter><sect1><sect2><para>
9957 #: ../en/ch09-undo.xml:891
9958 msgid ""
9959 "We now run our test in the working directory. We use the <command>grep</"
9960 "command> command to see if our <quote>bad</quote> file is present in the "
9961 "working directory. If it is, this revision is bad; if not, this revision is "
9962 "good. &interaction.bisect.search.step1;"
9963 msgstr ""
9965 #. type: Content of: <book><chapter><sect1><sect2><para>
9966 #: ../en/ch09-undo.xml:897
9967 msgid ""
9968 "This test looks like a perfect candidate for automation, so let's turn it "
9969 "into a shell function."
9970 msgstr ""
9972 #. type: Content of: <book><chapter><sect1><sect2><para>
9973 #: ../en/ch09-undo.xml:901
9974 msgid ""
9975 "We can now run an entire test step with a single command, <literal>mytest</"
9976 "literal>."
9977 msgstr ""
9979 #. type: Content of: <book><chapter><sect1><sect2><para>
9980 #: ../en/ch09-undo.xml:906
9981 msgid "A few more invocations of our canned test step command, and we're done."
9982 msgstr ""
9984 #. type: Content of: <book><chapter><sect1><sect2><para>
9985 #: ../en/ch09-undo.xml:911
9986 msgid ""
9987 "Even though we had 40 changesets to search through, the <command role=\"hg-cmd"
9988 "\">hg bisect</command> command let us find the changeset that introduced our "
9989 "<quote>bug</quote> with only five tests. Because the number of tests that "
9990 "the <command role=\"hg-cmd\">hg bisect</command> command performs grows "
9991 "logarithmically with the number of changesets to search, the advantage that "
9992 "it has over the <quote>brute force</quote> search approach increases with "
9993 "every changeset you add."
9994 msgstr ""
9996 #. type: Content of: <book><chapter><sect1><sect2><title>
9997 #: ../en/ch09-undo.xml:922
9998 msgid "Cleaning up after your search"
9999 msgstr "搜索后的清理"
10001 #
10002 #. type: Content of: <book><chapter><sect1><sect2><para>
10003 #: ../en/ch09-undo.xml:924
10004 msgid ""
10005 "When you're finished using the <command role=\"hg-cmd\">hg bisect</command> "
10006 "command in a repository, you can use the <command role=\"hg-cmd\">hg bisect "
10007 "reset</command> command to drop the information it was using to drive your "
10008 "search. The command doesn't use much space, so it doesn't matter if you "
10009 "forget to run this command. However, <command role=\"hg-cmd\">hg bisect</"
10010 "command> won't let you start a new search in that repository until you do a "
10011 "<command role=\"hg-cmd\">hg bisect reset</command>."
10012 msgstr ""
10014 #. type: Content of: <book><chapter><sect1><title>
10015 #: ../en/ch09-undo.xml:939
10016 msgid "Tips for finding bugs effectively"
10017 msgstr "有效查找问题的技巧"
10019 #. type: Content of: <book><chapter><sect1><sect2><title>
10020 #: ../en/ch09-undo.xml:942
10021 msgid "Give consistent input"
10022 msgstr "给出一致的输入"
10024 #. type: Content of: <book><chapter><sect1><sect2><para>
10025 #: ../en/ch09-undo.xml:944
10026 msgid ""
10027 "The <command role=\"hg-cmd\">hg bisect</command> command requires that you "
10028 "correctly report the result of every test you perform. If you tell it that a "
10029 "test failed when it really succeeded, it <emphasis>might</emphasis> be able "
10030 "to detect the inconsistency. If it can identify an inconsistency in your "
10031 "reports, it will tell you that a particular changeset is both good and bad. "
10032 "However, it can't do this perfectly; it's about as likely to report the wrong "
10033 "changeset as the source of the bug."
10034 msgstr ""
10036 #. type: Content of: <book><chapter><sect1><sect2><title>
10037 #: ../en/ch09-undo.xml:956
10038 msgid "Automate as much as possible"
10039 msgstr "尽量自动"
10041 #. type: Content of: <book><chapter><sect1><sect2><para>
10042 #: ../en/ch09-undo.xml:958
10043 msgid ""
10044 "When I started using the <command role=\"hg-cmd\">hg bisect</command> "
10045 "command, I tried a few times to run my tests by hand, on the command line. "
10046 "This is an approach that I, at least, am not suited to. After a few tries, I "
10047 "found that I was making enough mistakes that I was having to restart my "
10048 "searches several times before finally getting correct results."
10049 msgstr ""
10051 #. type: Content of: <book><chapter><sect1><sect2><para>
10052 #: ../en/ch09-undo.xml:966
10053 msgid ""
10054 "My initial problems with driving the <command role=\"hg-cmd\">hg bisect</"
10055 "command> command by hand occurred even with simple searches on small "
10056 "repositories; if the problem you're looking for is more subtle, or the number "
10057 "of tests that <command role=\"hg-cmd\">hg bisect</command> must perform "
10058 "increases, the likelihood of operator error ruining the search is much "
10059 "higher. Once I started automating my tests, I had much better results."
10060 msgstr ""
10062 #. type: Content of: <book><chapter><sect1><sect2><para>
10063 #: ../en/ch09-undo.xml:975
10064 msgid "The key to automated testing is twofold:"
10065 msgstr ""
10067 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
10068 #: ../en/ch09-undo.xml:977
10069 msgid "always test for the same symptom, and"
10070 msgstr ""
10072 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
10073 #: ../en/ch09-undo.xml:979
10074 msgid ""
10075 "always feed consistent input to the <command role=\"hg-cmd\">hg bisect</"
10076 "command> command."
10077 msgstr ""
10079 #. type: Content of: <book><chapter><sect1><sect2><para>
10080 #: ../en/ch09-undo.xml:982
10081 msgid ""
10082 "In my tutorial example above, the <command>grep</command> command tests for "
10083 "the symptom, and the <literal>if</literal> statement takes the result of this "
10084 "check and ensures that we always feed the same input to the <command role="
10085 "\"hg-cmd\">hg bisect</command> command. The <literal>mytest</literal> "
10086 "function marries these together in a reproducible way, so that every test is "
10087 "uniform and consistent."
10088 msgstr ""
10090 #. type: Content of: <book><chapter><sect1><sect2><title>
10091 #: ../en/ch09-undo.xml:992
10092 msgid "Check your results"
10093 msgstr "检查你的结果"
10095 #. type: Content of: <book><chapter><sect1><sect2><para>
10096 #: ../en/ch09-undo.xml:994
10097 msgid ""
10098 "Because the output of a <command role=\"hg-cmd\">hg bisect</command> search "
10099 "is only as good as the input you give it, don't take the changeset it reports "
10100 "as the absolute truth. A simple way to cross-check its report is to manually "
10101 "run your test at each of the following changesets:"
10102 msgstr ""
10104 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
10105 #: ../en/ch09-undo.xml:1000
10106 msgid ""
10107 "The changeset that it reports as the first bad revision. Your test should "
10108 "still report this as bad."
10109 msgstr ""
10111 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
10112 #: ../en/ch09-undo.xml:1004
10113 msgid ""
10114 "The parent of that changeset (either parent, if it's a merge). Your test "
10115 "should report this changeset as good."
10116 msgstr ""
10118 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
10119 #: ../en/ch09-undo.xml:1008
10120 msgid ""
10121 "A child of that changeset. Your test should report this changeset as bad."
10122 msgstr ""
10124 #. type: Content of: <book><chapter><sect1><sect2><title>
10125 #: ../en/ch09-undo.xml:1014
10126 msgid "Beware interference between bugs"
10127 msgstr "谨防问题之间的冲突"
10129 #. type: Content of: <book><chapter><sect1><sect2><para>
10130 #: ../en/ch09-undo.xml:1016
10131 msgid ""
10132 "It's possible that your search for one bug could be disrupted by the presence "
10133 "of another. For example, let's say your software crashes at revision 100, "
10134 "and worked correctly at revision 50. Unknown to you, someone else introduced "
10135 "a different crashing bug at revision 60, and fixed it at revision 80. This "
10136 "could distort your results in one of several ways."
10137 msgstr ""
10139 #. type: Content of: <book><chapter><sect1><sect2><para>
10140 #: ../en/ch09-undo.xml:1024
10141 msgid ""
10142 "It is possible that this other bug completely <quote>masks</quote> yours, "
10143 "which is to say that it occurs before your bug has a chance to manifest "
10144 "itself. If you can't avoid that other bug (for example, it prevents your "
10145 "project from building), and so can't tell whether your bug is present in a "
10146 "particular changeset, the <command role=\"hg-cmd\">hg bisect</command> "
10147 "command cannot help you directly. Instead, you can mark a changeset as "
10148 "untested by running <command role=\"hg-cmd\">hg bisect --skip</command>."
10149 msgstr ""
10151 #. type: Content of: <book><chapter><sect1><sect2><para>
10152 #: ../en/ch09-undo.xml:1034
10153 msgid ""
10154 "A different problem could arise if your test for a bug's presence is not "
10155 "specific enough. If you check for <quote>my program crashes</quote>, then "
10156 "both your crashing bug and an unrelated crashing bug that masks it will look "
10157 "like the same thing, and mislead <command role=\"hg-cmd\">hg bisect</command>."
10158 msgstr ""
10160 #. type: Content of: <book><chapter><sect1><sect2><para>
10161 #: ../en/ch09-undo.xml:1041
10162 msgid ""
10163 "Another useful situation in which to use <command role=\"hg-cmd\">hg bisect --"
10164 "skip</command> is if you can't test a revision because your project was in a "
10165 "broken and hence untestable state at that revision, perhaps because someone "
10166 "checked in a change that prevented the project from building."
10167 msgstr ""
10169 #. type: Content of: <book><chapter><sect1><sect2><title>
10170 #: ../en/ch09-undo.xml:1050
10171 msgid "Bracket your search lazily"
10172 msgstr "减少你的查找工作"
10174 #. type: Content of: <book><chapter><sect1><sect2><para>
10175 #: ../en/ch09-undo.xml:1052
10176 msgid ""
10177 "Choosing the first <quote>good</quote> and <quote>bad</quote> changesets that "
10178 "will mark the end points of your search is often easy, but it bears a little "
10179 "discussion nevertheless. From the perspective of <command role=\"hg-cmd\">hg "
10180 "bisect</command>, the <quote>newest</quote> changeset is conventionally "
10181 "<quote>bad</quote>, and the older changeset is <quote>good</quote>."
10182 msgstr ""
10184 #. type: Content of: <book><chapter><sect1><sect2><para>
10185 #: ../en/ch09-undo.xml:1060
10186 msgid ""
10187 "If you're having trouble remembering when a suitable <quote>good</quote> "
10188 "change was, so that you can tell <command role=\"hg-cmd\">hg bisect</"
10189 "command>, you could do worse than testing changesets at random. Just "
10190 "remember to eliminate contenders that can't possibly exhibit the bug (perhaps "
10191 "because the feature with the bug isn't present yet) and those where another "
10192 "problem masks the bug (as I discussed above)."
10193 msgstr ""
10195 #. type: Content of: <book><chapter><sect1><sect2><para>
10196 #: ../en/ch09-undo.xml:1069
10197 msgid ""
10198 "Even if you end up <quote>early</quote> by thousands of changesets or months "
10199 "of history, you will only add a handful of tests to the total number that "
10200 "<command role=\"hg-cmd\">hg bisect</command> must perform, thanks to its "
10201 "logarithmic behaviour."
10202 msgstr ""
10204 #. type: Content of: <book><chapter><title>
10205 #: ../en/ch10-hook.xml:5
10206 msgid "Handling repository events with hooks"
10207 msgstr "使用钩子处理版本库事件"
10209 #. type: Content of: <book><chapter><para>
10210 #: ../en/ch10-hook.xml:7
10211 msgid ""
10212 "Mercurial offers a powerful mechanism to let you perform automated actions in "
10213 "response to events that occur in a repository. In some cases, you can even "
10214 "control Mercurial's response to those events."
10215 msgstr ""
10217 #. type: Content of: <book><chapter><para>
10218 #: ../en/ch10-hook.xml:12
10219 msgid ""
10220 "The name Mercurial uses for one of these actions is a <emphasis>hook</"
10221 "emphasis>. Hooks are called <quote>triggers</quote> in some revision control "
10222 "systems, but the two names refer to the same idea."
10223 msgstr ""
10225 #. type: Content of: <book><chapter><sect1><title>
10226 #: ../en/ch10-hook.xml:18
10227 msgid "An overview of hooks in Mercurial"
10228 msgstr "Mercurial 钩子概述"
10230 #. type: Content of: <book><chapter><sect1><para>
10231 #: ../en/ch10-hook.xml:20
10232 msgid ""
10233 "Here is a brief list of the hooks that Mercurial supports. We will revisit "
10234 "each of these hooks in more detail later, in section <xref linkend=\"sec.hook."
10235 "ref\"/>."
10236 msgstr ""
10238 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10239 #: ../en/ch10-hook.xml:25
10240 msgid ""
10241 "<literal role=\"hook\">changegroup</literal>: This is run after a group of "
10242 "changesets has been brought into the repository from elsewhere."
10243 msgstr ""
10245 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10246 #: ../en/ch10-hook.xml:29
10247 msgid ""
10248 "<literal role=\"hook\">commit</literal>: This is run after a new changeset "
10249 "has been created in the local repository."
10250 msgstr ""
10252 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10253 #: ../en/ch10-hook.xml:33
10254 msgid ""
10255 "<literal role=\"hook\">incoming</literal>: This is run once for each new "
10256 "changeset that is brought into the repository from elsewhere. Notice the "
10257 "difference from <literal role=\"hook\">changegroup</literal>, which is run "
10258 "once per <emphasis>group</emphasis> of changesets brought in."
10259 msgstr ""
10261 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10262 #: ../en/ch10-hook.xml:40
10263 msgid ""
10264 "<literal role=\"hook\">outgoing</literal>: This is run after a group of "
10265 "changesets has been transmitted from this repository."
10266 msgstr ""
10268 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10269 #: ../en/ch10-hook.xml:44
10270 msgid ""
10271 "<literal role=\"hook\">prechangegroup</literal>: This is run before starting "
10272 "to bring a group of changesets into the repository."
10273 msgstr ""
10275 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10276 #: ../en/ch10-hook.xml:49
10277 msgid ""
10278 "<literal role=\"hook\">precommit</literal>: Controlling. This is run before "
10279 "starting a commit."
10280 msgstr ""
10282 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10283 #: ../en/ch10-hook.xml:53
10284 msgid ""
10285 "<literal role=\"hook\">preoutgoing</literal>: Controlling. This is run before "
10286 "starting to transmit a group of changesets from this repository."
10287 msgstr ""
10289 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10290 #: ../en/ch10-hook.xml:58
10291 msgid ""
10292 "<literal role=\"hook\">pretag</literal>: Controlling. This is run before "
10293 "creating a tag."
10294 msgstr ""
10296 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10297 #: ../en/ch10-hook.xml:62
10298 msgid ""
10299 "<literal role=\"hook\">pretxnchangegroup</literal>: Controlling. This is run "
10300 "after a group of changesets has been brought into the local repository from "
10301 "another, but before the transaction completes that will make the changes "
10302 "permanent in the repository."
10303 msgstr ""
10305 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10306 #: ../en/ch10-hook.xml:70
10307 msgid ""
10308 "<literal role=\"hook\">pretxncommit</literal>: Controlling. This is run after "
10309 "a new changeset has been created in the local repository, but before the "
10310 "transaction completes that will make it permanent."
10311 msgstr ""
10313 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10314 #: ../en/ch10-hook.xml:76
10315 msgid ""
10316 "<literal role=\"hook\">preupdate</literal>: Controlling. This is run before "
10317 "starting an update or merge of the working directory."
10318 msgstr ""
10320 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10321 #: ../en/ch10-hook.xml:81
10322 msgid ""
10323 "<literal role=\"hook\">tag</literal>: This is run after a tag is created."
10324 msgstr ""
10326 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
10327 #: ../en/ch10-hook.xml:85
10328 msgid ""
10329 "<literal role=\"hook\">update</literal>: This is run after an update or merge "
10330 "of the working directory has finished."
10331 msgstr ""
10333 #. type: Content of: <book><chapter><sect1><para>
10334 #: ../en/ch10-hook.xml:90
10335 msgid ""
10336 "Each of the hooks whose description begins with the word <quote>Controlling</"
10337 "quote> has the ability to determine whether an activity can proceed. If the "
10338 "hook succeeds, the activity may proceed; if it fails, the activity is either "
10339 "not permitted or undone, depending on the hook."
10340 msgstr ""
10342 #. type: Content of: <book><chapter><sect1><title>
10343 #: ../en/ch10-hook.xml:99
10344 msgid "Hooks and security"
10345 msgstr "钩子与安全性"
10347 #. type: Content of: <book><chapter><sect1><sect2><title>
10348 #: ../en/ch10-hook.xml:102
10349 msgid "Hooks are run with your privileges"
10350 msgstr "钩子以你的特权执行"
10352 #. type: Content of: <book><chapter><sect1><sect2><para>
10353 #: ../en/ch10-hook.xml:104
10354 msgid ""
10355 "When you run a Mercurial command in a repository, and the command causes a "
10356 "hook to run, that hook runs on <emphasis>your</emphasis> system, under "
10357 "<emphasis>your</emphasis> user account, with <emphasis>your</emphasis> "
10358 "privilege level. Since hooks are arbitrary pieces of executable code, you "
10359 "should treat them with an appropriate level of suspicion. Do not install a "
10360 "hook unless you are confident that you know who created it and what it does."
10361 msgstr ""
10363 #. type: Content of: <book><chapter><sect1><sect2><para>
10364 #: ../en/ch10-hook.xml:115
10365 msgid ""
10366 "In some cases, you may be exposed to hooks that you did not install "
10367 "yourself. If you work with Mercurial on an unfamiliar system, Mercurial will "
10368 "run hooks defined in that system's global <filename role=\"special\"> /.hgrc</"
10369 "filename>\\ file."
10370 msgstr ""
10372 #. type: Content of: <book><chapter><sect1><sect2><para>
10373 #: ../en/ch10-hook.xml:122
10374 msgid ""
10375 "If you are working with a repository owned by another user, Mercurial can run "
10376 "hooks defined in that user's repository, but it will still run them as "
10377 "<quote>you</quote>. For example, if you <command role=\"hg-cmd\">hg pull</"
10378 "command> from that repository, and its <filename role=\"special\">.hg/hgrc</"
10379 "filename> defines a local <literal role=\"hook\">outgoing</literal> hook, "
10380 "that hook will run under your user account, even though you don't own that "
10381 "repository."
10382 msgstr ""
10384 #. type: Content of: <book><chapter><sect1><sect2><note><para>
10385 #: ../en/ch10-hook.xml:134
10386 msgid ""
10387 "This only applies if you are pulling from a repository on a local or network "
10388 "filesystem. If you're pulling over http or ssh, any <literal role=\"hook"
10389 "\">outgoing</literal> hook will run under whatever account is executing the "
10390 "server process, on the server."
10391 msgstr ""
10393 #. type: Content of: <book><chapter><sect1><sect2><para>
10394 #: ../en/ch10-hook.xml:142
10395 msgid ""
10396 "XXX To see what hooks are defined in a repository, use the <command role=\"hg-"
10397 "cmd\">hg config hooks</command> command. If you are working in one "
10398 "repository, but talking to another that you do not own (e.g. using <command "
10399 "role=\"hg-cmd\">hg pull</command> or <command role=\"hg-cmd\">hg incoming</"
10400 "command>), remember that it is the other repository's hooks you should be "
10401 "checking, not your own."
10402 msgstr ""
10404 #. type: Content of: <book><chapter><sect1><sect2><title>
10405 #: ../en/ch10-hook.xml:153
10406 msgid "Hooks do not propagate"
10407 msgstr "钩子不会传播"
10409 #. type: Content of: <book><chapter><sect1><sect2><para>
10410 #: ../en/ch10-hook.xml:155
10411 msgid ""
10412 "In Mercurial, hooks are not revision controlled, and do not propagate when "
10413 "you clone, or pull from, a repository. The reason for this is simple: a hook "
10414 "is a completely arbitrary piece of executable code. It runs under your user "
10415 "identity, with your privilege level, on your machine."
10416 msgstr ""
10418 #. type: Content of: <book><chapter><sect1><sect2><para>
10419 #: ../en/ch10-hook.xml:162
10420 msgid ""
10421 "It would be extremely reckless for any distributed revision control system to "
10422 "implement revision-controlled hooks, as this would offer an easily "
10423 "exploitable way to subvert the accounts of users of the revision control "
10424 "system."
10425 msgstr ""
10427 #. type: Content of: <book><chapter><sect1><sect2><para>
10428 #: ../en/ch10-hook.xml:168
10429 msgid ""
10430 "Since Mercurial does not propagate hooks, if you are collaborating with other "
10431 "people on a common project, you should not assume that they are using the "
10432 "same Mercurial hooks as you are, or that theirs are correctly configured. "
10433 "You should document the hooks you expect people to use."
10434 msgstr ""
10436 #. type: Content of: <book><chapter><sect1><sect2><para>
10437 #: ../en/ch10-hook.xml:175
10438 msgid ""
10439 "In a corporate intranet, this is somewhat easier to control, as you can for "
10440 "example provide a <quote>standard</quote> installation of Mercurial on an NFS "
10441 "filesystem, and use a site-wide <filename role=\"special\"> /.hgrc</filename>"
10442 "\\ file to define hooks that all users will see. However, this too has its "
10443 "limits; see below."
10444 msgstr ""
10446 #. type: Content of: <book><chapter><sect1><sect2><title>
10447 #: ../en/ch10-hook.xml:185
10448 msgid "Hooks can be overridden"
10449 msgstr "钩子可以被覆盖"
10451 #. type: Content of: <book><chapter><sect1><sect2><para>
10452 #: ../en/ch10-hook.xml:187
10453 msgid ""
10454 "Mercurial allows you to override a hook definition by redefining the hook. "
10455 "You can disable it by setting its value to the empty string, or change its "
10456 "behaviour as you wish."
10457 msgstr ""
10459 #. type: Content of: <book><chapter><sect1><sect2><para>
10460 #: ../en/ch10-hook.xml:192
10461 msgid ""
10462 "If you deploy a system- or site-wide <filename role=\"special\"> /.hgrc</"
10463 "filename>\\ file that defines some hooks, you should thus understand that "
10464 "your users can disable or override those hooks."
10465 msgstr ""
10467 #. type: Content of: <book><chapter><sect1><sect2><title>
10468 #: ../en/ch10-hook.xml:200
10469 msgid "Ensuring that critical hooks are run"
10470 msgstr "确保关键钩子的执行"
10472 #. type: Content of: <book><chapter><sect1><sect2><para>
10473 #: ../en/ch10-hook.xml:202
10474 msgid ""
10475 "Sometimes you may want to enforce a policy that you do not want others to be "
10476 "able to work around. For example, you may have a requirement that every "
10477 "changeset must pass a rigorous set of tests. Defining this requirement via a "
10478 "hook in a site-wide <filename role=\"special\"> /.hgrc</filename>\\ won't "
10479 "work for remote users on laptops, and of course local users can subvert it at "
10480 "will by overriding the hook."
10481 msgstr ""
10483 #. type: Content of: <book><chapter><sect1><sect2><para>
10484 #: ../en/ch10-hook.xml:211
10485 msgid ""
10486 "Instead, you can set up your policies for use of Mercurial so that people are "
10487 "expected to propagate changes through a well-known <quote>canonical</quote> "
10488 "server that you have locked down and configured appropriately."
10489 msgstr ""
10491 #. type: Content of: <book><chapter><sect1><sect2><para>
10492 #: ../en/ch10-hook.xml:217
10493 msgid ""
10494 "One way to do this is via a combination of social engineering and "
10495 "technology. Set up a restricted-access account; users can push changes over "
10496 "the network to repositories managed by this account, but they cannot log into "
10497 "the account and run normal shell commands. In this scenario, a user can "
10498 "commit a changeset that contains any old garbage they want."
10499 msgstr ""
10501 #. type: Content of: <book><chapter><sect1><sect2><para>
10502 #: ../en/ch10-hook.xml:226
10503 msgid ""
10504 "When someone pushes a changeset to the server that everyone pulls from, the "
10505 "server will test the changeset before it accepts it as permanent, and reject "
10506 "it if it fails to pass the test suite. If people only pull changes from this "
10507 "filtering server, it will serve to ensure that all changes that people pull "
10508 "have been automatically vetted."
10509 msgstr ""
10511 #. type: Content of: <book><chapter><sect1><title>
10512 #: ../en/ch10-hook.xml:237
10513 msgid "Care with <literal>pretxn</literal> hooks in a shared-access repository"
10514 msgstr "在共享版本库中注意 <literal>pretxn</literal> 钩子"
10516 #. type: Content of: <book><chapter><sect1><para>
10517 #: ../en/ch10-hook.xml:240
10518 msgid ""
10519 "If you want to use hooks to do some automated work in a repository that a "
10520 "number of people have shared access to, you need to be careful in how you do "
10521 "this."
10522 msgstr ""
10524 #. type: Content of: <book><chapter><sect1><para>
10525 #: ../en/ch10-hook.xml:245
10526 msgid ""
10527 "Mercurial only locks a repository when it is writing to the repository, and "
10528 "only the parts of Mercurial that write to the repository pay attention to "
10529 "locks. Write locks are necessary to prevent multiple simultaneous writers "
10530 "from scribbling on each other's work, corrupting the repository."
10531 msgstr ""
10533 #. type: Content of: <book><chapter><sect1><para>
10534 #: ../en/ch10-hook.xml:252
10535 msgid ""
10536 "Because Mercurial is careful with the order in which it reads and writes "
10537 "data, it does not need to acquire a lock when it wants to read data from the "
10538 "repository. The parts of Mercurial that read from the repository never pay "
10539 "attention to locks. This lockless reading scheme greatly increases "
10540 "performance and concurrency."
10541 msgstr ""
10543 #. type: Content of: <book><chapter><sect1><para>
10544 #: ../en/ch10-hook.xml:260
10545 msgid ""
10546 "With great performance comes a trade-off, though, one which has the potential "
10547 "to cause you trouble unless you're aware of it. To describe this requires a "
10548 "little detail about how Mercurial adds changesets to a repository and reads "
10549 "those changes."
10550 msgstr ""
10552 #. type: Content of: <book><chapter><sect1><para>
10553 #: ../en/ch10-hook.xml:267
10554 msgid ""
10555 "When Mercurial <emphasis>writes</emphasis> metadata, it writes it straight "
10556 "into the destination file. It writes file data first, then manifest data "
10557 "(which contains pointers to the new file data), then changelog data (which "
10558 "contains pointers to the new manifest data). Before the first write to each "
10559 "file, it stores a record of where the end of the file was in its transaction "
10560 "log. If the transaction must be rolled back, Mercurial simply truncates each "
10561 "file back to the size it was before the transaction began."
10562 msgstr ""
10564 #. type: Content of: <book><chapter><sect1><para>
10565 #: ../en/ch10-hook.xml:278
10566 msgid ""
10567 "When Mercurial <emphasis>reads</emphasis> metadata, it reads the changelog "
10568 "first, then everything else. Since a reader will only access parts of the "
10569 "manifest or file metadata that it can see in the changelog, it can never see "
10570 "partially written data."
10571 msgstr ""
10573 #. type: Content of: <book><chapter><sect1><para>
10574 #: ../en/ch10-hook.xml:284
10575 msgid ""
10576 "Some controlling hooks (<literal role=\"hook\">pretxncommit</literal> and "
10577 "<literal role=\"hook\">pretxnchangegroup</literal>) run when a transaction is "
10578 "almost complete. All of the metadata has been written, but Mercurial can "
10579 "still roll the transaction back and cause the newly-written data to disappear."
10580 msgstr ""
10582 #. type: Content of: <book><chapter><sect1><para>
10583 #: ../en/ch10-hook.xml:292
10584 msgid ""
10585 "If one of these hooks runs for long, it opens a window of time during which a "
10586 "reader can see the metadata for changesets that are not yet permanent, and "
10587 "should not be thought of as <quote>really there</quote>. The longer the hook "
10588 "runs, the longer that window is open."
10589 msgstr ""
10591 #. type: Content of: <book><chapter><sect1><sect2><title>
10592 #: ../en/ch10-hook.xml:300
10593 msgid "The problem illustrated"
10594 msgstr "问题的演示"
10596 #. type: Content of: <book><chapter><sect1><sect2><para>
10597 #: ../en/ch10-hook.xml:302
10598 msgid ""
10599 "In principle, a good use for the <literal role=\"hook\">pretxnchangegroup</"
10600 "literal> hook would be to automatically build and test incoming changes "
10601 "before they are accepted into a central repository. This could let you "
10602 "guarantee that nobody can push changes to this repository that <quote>break "
10603 "the build</quote>. But if a client can pull changes while they're being "
10604 "tested, the usefulness of the test is zero; an unsuspecting someone can pull "
10605 "untested changes, potentially breaking their build."
10606 msgstr ""
10608 #. type: Content of: <book><chapter><sect1><sect2><para>
10609 #: ../en/ch10-hook.xml:313
10610 msgid ""
10611 "The safest technological answer to this challenge is to set up such a "
10612 "<quote>gatekeeper</quote> repository as <emphasis>unidirectional</emphasis>. "
10613 "Let it take changes pushed in from the outside, but do not allow anyone to "
10614 "pull changes from it (use the <literal role=\"hook\">preoutgoing</literal> "
10615 "hook to lock it down). Configure a <literal role=\"hook\">changegroup</"
10616 "literal> hook so that if a build or test succeeds, the hook will push the new "
10617 "changes out to another repository that people <emphasis>can</emphasis> pull "
10618 "from."
10619 msgstr ""
10621 #. type: Content of: <book><chapter><sect1><sect2><para>
10622 #: ../en/ch10-hook.xml:325
10623 msgid ""
10624 "In practice, putting a centralised bottleneck like this in place is not often "
10625 "a good idea, and transaction visibility has nothing to do with the problem. "
10626 "As the size of a project&emdash;and the time it takes to build and "
10627 "test&emdash;grows, you rapidly run into a wall with this <quote>try before "
10628 "you buy</quote> approach, where you have more changesets to test than time in "
10629 "which to deal with them. The inevitable result is frustration on the part of "
10630 "all involved."
10631 msgstr ""
10633 #. type: Content of: <book><chapter><sect1><sect2><para>
10634 #: ../en/ch10-hook.xml:336
10635 msgid ""
10636 "An approach that scales better is to get people to build and test before they "
10637 "push, then run automated builds and tests centrally <emphasis>after</"
10638 "emphasis> a push, to be sure all is well. The advantage of this approach is "
10639 "that it does not impose a limit on the rate at which the repository can "
10640 "accept changes."
10641 msgstr ""
10643 #. type: Content of: <book><chapter><sect1><title>
10644 #: ../en/ch10-hook.xml:347
10645 msgid "A short tutorial on using hooks"
10646 msgstr "使用钩子的简短指南"
10648 #. type: Content of: <book><chapter><sect1><para>
10649 #: ../en/ch10-hook.xml:349
10650 msgid ""
10651 "It is easy to write a Mercurial hook. Let's start with a hook that runs when "
10652 "you finish a <command role=\"hg-cmd\">hg commit</command>, and simply prints "
10653 "the hash of the changeset you just created. The hook is called <literal role="
10654 "\"hook\">commit</literal>."
10655 msgstr ""
10657 #. type: Content of: <book><chapter><sect1><para>
10658 #: ../en/ch10-hook.xml:356
10659 msgid "All hooks follow the pattern in this example."
10660 msgstr ""
10662 #. type: Content of: <book><chapter><sect1><para>
10663 #: ../en/ch10-hook.xml:360
10664 msgid ""
10665 "You add an entry to the <literal role=\"rc-hooks\">hooks</literal> section of "
10666 "your <filename role=\"special\"> /.hgrc</filename>. On the left is the name "
10667 "of the event to trigger on; on the right is the action to take. As you can "
10668 "see, you can run an arbitrary shell command in a hook. Mercurial passes "
10669 "extra information to the hook using environment variables (look for "
10670 "<envar>HG_NODE</envar> in the example)."
10671 msgstr ""
10673 #. type: Content of: <book><chapter><sect1><sect2><title>
10674 #: ../en/ch10-hook.xml:370
10675 msgid "Performing multiple actions per event"
10676 msgstr "每个事件执行多个操作"
10678 #. type: Content of: <book><chapter><sect1><sect2><para>
10679 #: ../en/ch10-hook.xml:372
10680 msgid ""
10681 "Quite often, you will want to define more than one hook for a particular kind "
10682 "of event, as shown below."
10683 msgstr ""
10685 #. type: Content of: <book><chapter><sect1><sect2><para>
10686 #: ../en/ch10-hook.xml:377
10687 msgid ""
10688 "Mercurial lets you do this by adding an <emphasis>extension</emphasis> to the "
10689 "end of a hook's name. You extend a hook's name by giving the name of the "
10690 "hook, followed by a full stop (the <quote><literal>.</literal></quote> "
10691 "character), followed by some more text of your choosing. For example, "
10692 "Mercurial will run both <literal>commit.foo</literal> and <literal>commit."
10693 "bar</literal> when the <literal>commit</literal> event occurs."
10694 msgstr ""
10696 #. type: Content of: <book><chapter><sect1><sect2><para>
10697 #: ../en/ch10-hook.xml:388
10698 msgid ""
10699 "To give a well-defined order of execution when there are multiple hooks "
10700 "defined for an event, Mercurial sorts hooks by extension, and executes the "
10701 "hook commands in this sorted order. In the above example, it will execute "
10702 "<literal>commit.bar</literal> before <literal>commit.foo</literal>, and "
10703 "<literal>commit</literal> before both."
10704 msgstr ""
10706 #. type: Content of: <book><chapter><sect1><sect2><para>
10707 #: ../en/ch10-hook.xml:397
10708 msgid ""
10709 "It is a good idea to use a somewhat descriptive extension when you define a "
10710 "new hook. This will help you to remember what the hook was for. If the hook "
10711 "fails, you'll get an error message that contains the hook name and extension, "
10712 "so using a descriptive extension could give you an immediate hint as to why "
10713 "the hook failed (see section <xref linkend=\"sec.hook.perm\"/> for an "
10714 "example)."
10715 msgstr ""
10717 #. type: Content of: <book><chapter><sect1><sect2><title>
10718 #: ../en/ch10-hook.xml:408
10719 msgid "Controlling whether an activity can proceed"
10720 msgstr "控制处理的活动"
10722 #. type: Content of: <book><chapter><sect1><sect2><para>
10723 #: ../en/ch10-hook.xml:410
10724 msgid ""
10725 "In our earlier examples, we used the <literal role=\"hook\">commit</literal> "
10726 "hook, which is run after a commit has completed. This is one of several "
10727 "Mercurial hooks that run after an activity finishes. Such hooks have no way "
10728 "of influencing the activity itself."
10729 msgstr ""
10731 #. type: Content of: <book><chapter><sect1><sect2><para>
10732 #: ../en/ch10-hook.xml:417
10733 msgid ""
10734 "Mercurial defines a number of events that occur before an activity starts; or "
10735 "after it starts, but before it finishes. Hooks that trigger on these events "
10736 "have the added ability to choose whether the activity can continue, or will "
10737 "abort."
10738 msgstr ""
10740 #. type: Content of: <book><chapter><sect1><sect2><para>
10741 #: ../en/ch10-hook.xml:423
10742 msgid ""
10743 "The <literal role=\"hook\">pretxncommit</literal> hook runs after a commit "
10744 "has all but completed. In other words, the metadata representing the "
10745 "changeset has been written out to disk, but the transaction has not yet been "
10746 "allowed to complete. The <literal role=\"hook\">pretxncommit</literal> hook "
10747 "has the ability to decide whether the transaction can complete, or must be "
10748 "rolled back."
10749 msgstr ""
10751 #. type: Content of: <book><chapter><sect1><sect2><para>
10752 #: ../en/ch10-hook.xml:432
10753 msgid ""
10754 "If the <literal role=\"hook\">pretxncommit</literal> hook exits with a status "
10755 "code of zero, the transaction is allowed to complete; the commit finishes; "
10756 "and the <literal role=\"hook\">commit</literal> hook is run. If the <literal "
10757 "role=\"hook\">pretxncommit</literal> hook exits with a non-zero status code, "
10758 "the transaction is rolled back; the metadata representing the changeset is "
10759 "erased; and the <literal role=\"hook\">commit</literal> hook is not run."
10760 msgstr ""
10762 #. type: Content of: <book><chapter><sect1><sect2><para>
10763 #: ../en/ch10-hook.xml:444
10764 msgid ""
10765 "The hook in the example above checks that a commit comment contains a bug "
10766 "ID. If it does, the commit can complete. If not, the commit is rolled back."
10767 msgstr ""
10769 #. type: Content of: <book><chapter><sect1><title>
10770 #: ../en/ch10-hook.xml:452
10771 msgid "Writing your own hooks"
10772 msgstr "编写钩子"
10774 #. type: Content of: <book><chapter><sect1><para>
10775 #: ../en/ch10-hook.xml:454
10776 msgid ""
10777 "When you are writing a hook, you might find it useful to run Mercurial either "
10778 "with the <option role=\"hg-opt-global\">-v</option> option, or the <envar "
10779 "role=\"rc-item-ui\">verbose</envar> config item set to <quote>true</quote>. "
10780 "When you do so, Mercurial will print a message before it calls each hook."
10781 msgstr ""
10783 #. type: Content of: <book><chapter><sect1><sect2><title>
10784 #: ../en/ch10-hook.xml:463
10785 msgid "Choosing how your hook should run"
10786 msgstr "选择钩子的执行方式"
10788 #. type: Content of: <book><chapter><sect1><sect2><para>
10789 #: ../en/ch10-hook.xml:465
10790 msgid ""
10791 "You can write a hook either as a normal program&emdash;typically a shell "
10792 "script&emdash;or as a Python function that is executed within the Mercurial "
10793 "process."
10794 msgstr ""
10796 #. type: Content of: <book><chapter><sect1><sect2><para>
10797 #: ../en/ch10-hook.xml:470
10798 msgid ""
10799 "Writing a hook as an external program has the advantage that it requires no "
10800 "knowledge of Mercurial's internals. You can call normal Mercurial commands "
10801 "to get any added information you need. The trade-off is that external hooks "
10802 "are slower than in-process hooks."
10803 msgstr ""
10805 #. type: Content of: <book><chapter><sect1><sect2><para>
10806 #: ../en/ch10-hook.xml:477
10807 msgid ""
10808 "An in-process Python hook has complete access to the Mercurial API, and does "
10809 "not <quote>shell out</quote> to another process, so it is inherently faster "
10810 "than an external hook. It is also easier to obtain much of the information "
10811 "that a hook requires by using the Mercurial API than by running Mercurial "
10812 "commands."
10813 msgstr ""
10815 #. type: Content of: <book><chapter><sect1><sect2><para>
10816 #: ../en/ch10-hook.xml:485
10817 msgid ""
10818 "If you are comfortable with Python, or require high performance, writing your "
10819 "hooks in Python may be a good choice. However, when you have a "
10820 "straightforward hook to write and you don't need to care about performance "
10821 "(probably the majority of hooks), a shell script is perfectly fine."
10822 msgstr ""
10824 #. type: Content of: <book><chapter><sect1><sect2><title>
10825 #: ../en/ch10-hook.xml:494
10826 msgid "Hook parameters"
10827 msgstr "钩子的参数"
10829 #. type: Content of: <book><chapter><sect1><sect2><para>
10830 #: ../en/ch10-hook.xml:496
10831 msgid ""
10832 "Mercurial calls each hook with a set of well-defined parameters. In Python, "
10833 "a parameter is passed as a keyword argument to your hook function. For an "
10834 "external program, a parameter is passed as an environment variable."
10835 msgstr ""
10837 #. type: Content of: <book><chapter><sect1><sect2><para>
10838 #: ../en/ch10-hook.xml:502
10839 msgid ""
10840 "Whether your hook is written in Python or as a shell script, the hook-"
10841 "specific parameter names and values will be the same. A boolean parameter "
10842 "will be represented as a boolean value in Python, but as the number 1 (for "
10843 "<quote>true</quote>) or 0 (for <quote>false</quote>) as an environment "
10844 "variable for an external hook. If a hook parameter is named <literal>foo</"
10845 "literal>, the keyword argument for a Python hook will also be named "
10846 "<literal>foo</literal>, while the environment variable for an external hook "
10847 "will be named <literal>HG_FOO</literal>."
10848 msgstr ""
10850 #. type: Content of: <book><chapter><sect1><sect2><title>
10851 #: ../en/ch10-hook.xml:516
10852 msgid "Hook return values and activity control"
10853 msgstr "钩子的返回值与活动控制"
10855 #. type: Content of: <book><chapter><sect1><sect2><para>
10856 #: ../en/ch10-hook.xml:518
10857 msgid ""
10858 "A hook that executes successfully must exit with a status of zero if "
10859 "external, or return boolean <quote>false</quote> if in-process. Failure is "
10860 "indicated with a non-zero exit status from an external hook, or an in-process "
10861 "hook returning boolean <quote>true</quote>. If an in-process hook raises an "
10862 "exception, the hook is considered to have failed."
10863 msgstr ""
10865 #. type: Content of: <book><chapter><sect1><sect2><para>
10866 #: ../en/ch10-hook.xml:526
10867 msgid ""
10868 "For a hook that controls whether an activity can proceed, zero/false means "
10869 "<quote>allow</quote>, while non-zero/true/exception means <quote>deny</quote>."
10870 msgstr ""
10872 #. type: Content of: <book><chapter><sect1><sect2><title>
10873 #: ../en/ch10-hook.xml:533
10874 msgid "Writing an external hook"
10875 msgstr "编写外部钩子"
10877 #. type: Content of: <book><chapter><sect1><sect2><para>
10878 #: ../en/ch10-hook.xml:535
10879 msgid ""
10880 "When you define an external hook in your <filename role=\"special\"> /.hgrc</"
10881 "filename>\\ and the hook is run, its value is passed to your shell, which "
10882 "interprets it. This means that you can use normal shell constructs in the "
10883 "body of the hook."
10884 msgstr ""
10886 #. type: Content of: <book><chapter><sect1><sect2><para>
10887 #: ../en/ch10-hook.xml:542
10888 msgid ""
10889 "An executable hook is always run with its current directory set to a "
10890 "repository's root directory."
10891 msgstr ""
10893 #. type: Content of: <book><chapter><sect1><sect2><para>
10894 #: ../en/ch10-hook.xml:546
10895 msgid ""
10896 "Each hook parameter is passed in as an environment variable; the name is "
10897 "upper-cased, and prefixed with the string <quote><literal>HG_</literal></"
10898 "quote>."
10899 msgstr ""
10901 #. type: Content of: <book><chapter><sect1><sect2><para>
10902 #: ../en/ch10-hook.xml:551
10903 msgid ""
10904 "With the exception of hook parameters, Mercurial does not set or modify any "
10905 "environment variables when running a hook. This is useful to remember if you "
10906 "are writing a site-wide hook that may be run by a number of different users "
10907 "with differing environment variables set. In multi-user situations, you "
10908 "should not rely on environment variables being set to the values you have in "
10909 "your environment when testing the hook."
10910 msgstr ""
10912 #. type: Content of: <book><chapter><sect1><sect2><title>
10913 #: ../en/ch10-hook.xml:562
10914 msgid "Telling Mercurial to use an in-process hook"
10915 msgstr "让 Mercurial 使用进程内钩子"
10917 #. type: Content of: <book><chapter><sect1><sect2><para>
10918 #: ../en/ch10-hook.xml:564
10919 msgid ""
10920 "The <filename role=\"special\"> /.hgrc</filename>\\ syntax for defining an in-"
10921 "process hook is slightly different than for an executable hook. The value of "
10922 "the hook must start with the text <quote><literal>python:</literal></quote>, "
10923 "and continue with the fully-qualified name of a callable object to use as the "
10924 "hook's value."
10925 msgstr ""
10927 #. type: Content of: <book><chapter><sect1><sect2><para>
10928 #: ../en/ch10-hook.xml:572
10929 msgid ""
10930 "The module in which a hook lives is automatically imported when a hook is "
10931 "run. So long as you have the module name and <envar>PYTHONPATH</envar> "
10932 "right, it should <quote>just work</quote>."
10933 msgstr ""
10935 #. type: Content of: <book><chapter><sect1><sect2><para>
10936 #: ../en/ch10-hook.xml:578
10937 msgid ""
10938 "The following <filename role=\"special\"> /.hgrc</filename>\\ example snippet "
10939 "illustrates the syntax and meaning of the notions we just described."
10940 msgstr ""
10942 #. type: Content of: <book><chapter><sect1><sect2><para>
10943 #: ../en/ch10-hook.xml:584
10944 msgid ""
10945 "When Mercurial runs the <literal>commit.example</literal> hook, it imports "
10946 "<literal>mymodule.submodule</literal>, looks for the callable object named "
10947 "<literal>myhook</literal>, and calls it."
10948 msgstr ""
10950 #. type: Content of: <book><chapter><sect1><sect2><title>
10951 #: ../en/ch10-hook.xml:592
10952 msgid "Writing an in-process hook"
10953 msgstr "编写进程内钩子"
10955 #. type: Content of: <book><chapter><sect1><sect2><para>
10956 #: ../en/ch10-hook.xml:594
10957 msgid ""
10958 "The simplest in-process hook does nothing, but illustrates the basic shape of "
10959 "the hook API:"
10960 msgstr ""
10962 #. type: Content of: <book><chapter><sect1><sect2><para>
10963 #: ../en/ch10-hook.xml:599
10964 msgid ""
10965 "The first argument to a Python hook is always a <literal role=\"py-mod-"
10966 "mercurial.ui\">ui</literal> object. The second is a repository object; at "
10967 "the moment, it is always an instance of <literal role=\"py-mod-mercurial."
10968 "localrepo\">localrepository</literal>. Following these two arguments are "
10969 "other keyword arguments. Which ones are passed in depends on the hook being "
10970 "called, but a hook can ignore arguments it doesn't care about by dropping "
10971 "them into a keyword argument dict, as with <literal>**kwargs</literal> above."
10972 msgstr ""
10974 #. type: Content of: <book><chapter><sect1><title>
10975 #: ../en/ch10-hook.xml:614
10976 msgid "Some hook examples"
10977 msgstr "钩子样例"
10979 #. type: Content of: <book><chapter><sect1><sect2><title>
10980 #: ../en/ch10-hook.xml:617
10981 msgid "Writing meaningful commit messages"
10982 msgstr "编写有意义的提交日志"
10984 #. type: Content of: <book><chapter><sect1><sect2><para>
10985 #: ../en/ch10-hook.xml:619
10986 msgid ""
10987 "It's hard to imagine a useful commit message being very short. The simple "
10988 "<literal role=\"hook\">pretxncommit</literal> hook of the example below will "
10989 "prevent you from committing a changeset with a message that is less than ten "
10990 "bytes long."
10991 msgstr ""
10993 #. type: Content of: <book><chapter><sect1><sect2><title>
10994 #: ../en/ch10-hook.xml:629
10995 msgid "Checking for trailing whitespace"
10996 msgstr "检查行尾空格"
10998 #. type: Content of: <book><chapter><sect1><sect2><para>
10999 #: ../en/ch10-hook.xml:631
11000 msgid ""
11001 "An interesting use of a commit-related hook is to help you to write cleaner "
11002 "code. A simple example of <quote>cleaner code</quote> is the dictum that a "
11003 "change should not add any new lines of text that contain <quote>trailing "
11004 "whitespace</quote>. Trailing whitespace is a series of space and tab "
11005 "characters at the end of a line of text. In most cases, trailing whitespace "
11006 "is unnecessary, invisible noise, but it is occasionally problematic, and "
11007 "people often prefer to get rid of it."
11008 msgstr ""
11010 #. type: Content of: <book><chapter><sect1><sect2><para>
11011 #: ../en/ch10-hook.xml:642
11012 msgid ""
11013 "You can use either the <literal role=\"hook\">precommit</literal> or <literal "
11014 "role=\"hook\">pretxncommit</literal> hook to tell whether you have a trailing "
11015 "whitespace problem. If you use the <literal role=\"hook\">precommit</"
11016 "literal> hook, the hook will not know which files you are committing, so it "
11017 "will have to check every modified file in the repository for trailing white "
11018 "space. If you want to commit a change to just the file <filename>foo</"
11019 "filename>, but the file <filename>bar</filename> contains trailing "
11020 "whitespace, doing a check in the <literal role=\"hook\">precommit</literal> "
11021 "hook will prevent you from committing <filename>foo</filename> due to the "
11022 "problem with <filename>bar</filename>. This doesn't seem right."
11023 msgstr ""
11025 #. type: Content of: <book><chapter><sect1><sect2><para>
11026 #: ../en/ch10-hook.xml:658
11027 msgid ""
11028 "Should you choose the <literal role=\"hook\">pretxncommit</literal> hook, the "
11029 "check won't occur until just before the transaction for the commit "
11030 "completes. This will allow you to check for problems only the exact files "
11031 "that are being committed. However, if you entered the commit message "
11032 "interactively and the hook fails, the transaction will roll back; you'll have "
11033 "to re-enter the commit message after you fix the trailing whitespace and run "
11034 "<command role=\"hg-cmd\">hg commit</command> again."
11035 msgstr ""
11037 #. type: Content of: <book><chapter><sect1><sect2><para>
11038 #: ../en/ch10-hook.xml:671
11039 msgid ""
11040 "In this example, we introduce a simple <literal role=\"hook\">pretxncommit</"
11041 "literal> hook that checks for trailing whitespace. This hook is short, but "
11042 "not very helpful. It exits with an error status if a change adds a line with "
11043 "trailing whitespace to any file, but does not print any information that "
11044 "might help us to identify the offending file or line. It also has the nice "
11045 "property of not paying attention to unmodified lines; only lines that "
11046 "introduce new trailing whitespace cause problems."
11047 msgstr ""
11049 #. type: Content of: <book><chapter><sect1><sect2><para>
11050 #: ../en/ch10-hook.xml:682
11051 msgid ""
11052 "The above version is much more complex, but also more useful. It parses a "
11053 "unified diff to see if any lines add trailing whitespace, and prints the name "
11054 "of the file and the line number of each such occurrence. Even better, if the "
11055 "change adds trailing whitespace, this hook saves the commit comment and "
11056 "prints the name of the save file before exiting and telling Mercurial to roll "
11057 "the transaction back, so you can use the <option role=\"hg-opt-commit\">-l "
11058 "filename</option> option to <command role=\"hg-cmd\">hg commit</command> to "
11059 "reuse the saved commit message once you've corrected the problem."
11060 msgstr ""
11062 #. type: Content of: <book><chapter><sect1><sect2><para>
11063 #: ../en/ch10-hook.xml:696
11064 msgid ""
11065 "As a final aside, note in the example above the use of <command>perl</"
11066 "command>'s in-place editing feature to get rid of trailing whitespace from a "
11067 "file. This is concise and useful enough that I will reproduce it here."
11068 msgstr ""
11070 #. type: Content of: <book><chapter><sect1><title>
11071 #: ../en/ch10-hook.xml:706
11072 msgid "Bundled hooks"
11073 msgstr "内置的钩子"
11075 #. type: Content of: <book><chapter><sect1><para>
11076 #: ../en/ch10-hook.xml:708
11077 msgid ""
11078 "Mercurial ships with several bundled hooks. You can find them in the "
11079 "<filename class=\"directory\">hgext</filename> directory of a Mercurial "
11080 "source tree. If you are using a Mercurial binary package, the hooks will be "
11081 "located in the <filename class=\"directory\">hgext</filename> directory of "
11082 "wherever your package installer put Mercurial."
11083 msgstr ""
11085 #. type: Content of: <book><chapter><sect1><sect2><title>
11086 #: ../en/ch10-hook.xml:717
11087 msgid ""
11088 "<literal role=\"hg-ext\">acl</literal>&emdash;access control for parts of a "
11089 "repository"
11090 msgstr "<literal role=\"hg-ext\">acl</literal>&emdash;版本库的访问控制"
11092 #. type: Content of: <book><chapter><sect1><sect2><para>
11093 #: ../en/ch10-hook.xml:720
11094 msgid ""
11095 "The <literal role=\"hg-ext\">acl</literal> extension lets you control which "
11096 "remote users are allowed to push changesets to a networked server. You can "
11097 "protect any portion of a repository (including the entire repo), so that a "
11098 "specific remote user can push changes that do not affect the protected "
11099 "portion."
11100 msgstr ""
11102 #. type: Content of: <book><chapter><sect1><sect2><para>
11103 #: ../en/ch10-hook.xml:728
11104 msgid ""
11105 "This extension implements access control based on the identity of the user "
11106 "performing a push, <emphasis>not</emphasis> on who committed the changesets "
11107 "they're pushing. It makes sense to use this hook only if you have a locked-"
11108 "down server environment that authenticates remote users, and you want to be "
11109 "sure that only specific users are allowed to push changes to that server."
11110 msgstr ""
11112 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
11113 #: ../en/ch10-hook.xml:738
11114 msgid "Configuring the <literal role=\"hook\">acl</literal> hook"
11115 msgstr "配置 <literal role=\"hook\">acl</literal> 钩子"
11117 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11118 #: ../en/ch10-hook.xml:741
11119 msgid ""
11120 "In order to manage incoming changesets, the <literal role=\"hg-ext\">acl</"
11121 "literal> hook must be used as a <literal role=\"hook\">pretxnchangegroup</"
11122 "literal> hook. This lets it see which files are modified by each incoming "
11123 "changeset, and roll back a group of changesets if they modify "
11124 "<quote>forbidden</quote> files. Example:"
11125 msgstr ""
11127 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11128 #: ../en/ch10-hook.xml:751
11129 msgid ""
11130 "The <literal role=\"hg-ext\">acl</literal> extension is configured using "
11131 "three sections."
11132 msgstr ""
11134 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11135 #: ../en/ch10-hook.xml:755
11136 msgid ""
11137 "The <literal role=\"rc-acl\">acl</literal> section has only one entry, <envar "
11138 "role=\"rc-item-acl\">sources</envar>, which lists the sources of incoming "
11139 "changesets that the hook should pay attention to. You don't normally need to "
11140 "configure this section."
11141 msgstr ""
11143 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11144 #: ../en/ch10-hook.xml:762
11145 msgid ""
11146 "<envar role=\"rc-item-acl\">serve</envar>: Control incoming changesets that "
11147 "are arriving from a remote repository over http or ssh. This is the default "
11148 "value of <envar role=\"rc-item-acl\">sources</envar>, and usually the only "
11149 "setting you'll need for this configuration item."
11150 msgstr ""
11152 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11153 #: ../en/ch10-hook.xml:770
11154 msgid ""
11155 "<envar role=\"rc-item-acl\">pull</envar>: Control incoming changesets that "
11156 "are arriving via a pull from a local repository."
11157 msgstr ""
11159 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11160 #: ../en/ch10-hook.xml:775
11161 msgid ""
11162 "<envar role=\"rc-item-acl\">push</envar>: Control incoming changesets that "
11163 "are arriving via a push from a local repository."
11164 msgstr ""
11166 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11167 #: ../en/ch10-hook.xml:780
11168 msgid ""
11169 "<envar role=\"rc-item-acl\">bundle</envar>: Control incoming changesets that "
11170 "are arriving from another repository via a bundle."
11171 msgstr ""
11173 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11174 #: ../en/ch10-hook.xml:786
11175 msgid ""
11176 "The <literal role=\"rc-acl.allow\">acl.allow</literal> section controls the "
11177 "users that are allowed to add changesets to the repository. If this section "
11178 "is not present, all users that are not explicitly denied are allowed. If "
11179 "this section is present, all users that are not explicitly allowed are denied "
11180 "(so an empty section means that all users are denied)."
11181 msgstr ""
11183 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11184 #: ../en/ch10-hook.xml:795
11185 msgid ""
11186 "The <literal role=\"rc-acl.deny\">acl.deny</literal> section determines which "
11187 "users are denied from adding changesets to the repository. If this section "
11188 "is not present or is empty, no users are denied."
11189 msgstr ""
11191 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11192 #: ../en/ch10-hook.xml:801
11193 msgid ""
11194 "The syntaxes for the <literal role=\"rc-acl.allow\">acl.allow</literal> and "
11195 "<literal role=\"rc-acl.deny\">acl.deny</literal> sections are identical. On "
11196 "the left of each entry is a glob pattern that matches files or directories, "
11197 "relative to the root of the repository; on the right, a user name."
11198 msgstr ""
11200 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11201 #: ../en/ch10-hook.xml:809
11202 msgid ""
11203 "In the following example, the user <literal>docwriter</literal> can only push "
11204 "changes to the <filename class=\"directory\">docs</filename> subtree of the "
11205 "repository, while <literal>intern</literal> can push changes to any file or "
11206 "directory except <filename class=\"directory\">source/sensitive</filename>."
11207 msgstr ""
11209 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
11210 #: ../en/ch10-hook.xml:821 ../en/ch10-hook.xml:1095 ../en/ch10-hook.xml:1308
11211 msgid "Testing and troubleshooting"
11212 msgstr "测试与问题处理"
11214 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11215 #: ../en/ch10-hook.xml:823
11216 msgid ""
11217 "If you want to test the <literal role=\"hg-ext\">acl</literal> hook, run it "
11218 "with Mercurial's debugging output enabled. Since you'll probably be running "
11219 "it on a server where it's not convenient (or sometimes possible) to pass in "
11220 "the <option role=\"hg-opt-global\">--debug</option> option, don't forget that "
11221 "you can enable debugging output in your <filename role=\"special\"> /.hgrc</"
11222 "filename>:"
11223 msgstr ""
11225 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11226 #: ../en/ch10-hook.xml:833
11227 msgid ""
11228 "With this enabled, the <literal role=\"hg-ext\">acl</literal> hook will print "
11229 "enough information to let you figure out why it is allowing or forbidding "
11230 "pushes from specific users."
11231 msgstr ""
11233 #. type: Content of: <book><chapter><sect1><sect2><title>
11234 #: ../en/ch10-hook.xml:842
11235 msgid ""
11236 "<literal role=\"hg-ext\">bugzilla</literal>&emdash;integration with Bugzilla"
11237 msgstr "<literal role=\"hg-ext\">bugzilla</literal>&emdash;与 Bugzilla 的集成"
11239 #. type: Content of: <book><chapter><sect1><sect2><para>
11240 #: ../en/ch10-hook.xml:846
11241 msgid ""
11242 "The <literal role=\"hg-ext\">bugzilla</literal> extension adds a comment to a "
11243 "Bugzilla bug whenever it finds a reference to that bug ID in a commit "
11244 "comment. You can install this hook on a shared server, so that any time a "
11245 "remote user pushes changes to this server, the hook gets run."
11246 msgstr ""
11248 #. type: Content of: <book><chapter><sect1><sect2><para>
11249 #: ../en/ch10-hook.xml:853
11250 msgid ""
11251 "It adds a comment to the bug that looks like this (you can configure the "
11252 "contents of the comment&emdash;see below):"
11253 msgstr ""
11255 #. type: Content of: <book><chapter><sect1><sect2><para>
11256 #: ../en/ch10-hook.xml:862
11257 msgid ""
11258 "The value of this hook is that it automates the process of updating a bug any "
11259 "time a changeset refers to it. If you configure the hook properly, it makes "
11260 "it easy for people to browse straight from a Bugzilla bug to a changeset that "
11261 "refers to that bug."
11262 msgstr ""
11264 #. type: Content of: <book><chapter><sect1><sect2><para>
11265 #: ../en/ch10-hook.xml:869
11266 msgid ""
11267 "You can use the code in this hook as a starting point for some more exotic "
11268 "Bugzilla integration recipes. Here are a few possibilities:"
11269 msgstr ""
11271 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
11272 #: ../en/ch10-hook.xml:874
11273 msgid ""
11274 "Require that every changeset pushed to the server have a valid bug ID in its "
11275 "commit comment. In this case, you'd want to configure the hook as a <literal "
11276 "role=\"hook\">pretxncommit</literal> hook. This would allow the hook to "
11277 "reject changes that didn't contain bug IDs."
11278 msgstr ""
11280 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
11281 #: ../en/ch10-hook.xml:882
11282 msgid ""
11283 "Allow incoming changesets to automatically modify the <emphasis>state</"
11284 "emphasis> of a bug, as well as simply adding a comment. For example, the "
11285 "hook could recognise the string <quote>fixed bug 31337</quote> as indicating "
11286 "that it should update the state of bug 31337 to <quote>requires testing</"
11287 "quote>."
11288 msgstr ""
11290 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
11291 #: ../en/ch10-hook.xml:892
11292 msgid "Configuring the <literal role=\"hook\">bugzilla</literal> hook"
11293 msgstr "配置 <literal role=\"hook\">bugzilla</literal> 钩子"
11295 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11296 #: ../en/ch10-hook.xml:895
11297 msgid ""
11298 "You should configure this hook in your server's <filename role=\"special\"> /."
11299 "hgrc</filename>\\ as an <literal role=\"hook\">incoming</literal> hook, for "
11300 "example as follows:"
11301 msgstr ""
11303 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11304 #: ../en/ch10-hook.xml:903
11305 msgid ""
11306 "Because of the specialised nature of this hook, and because Bugzilla was not "
11307 "written with this kind of integration in mind, configuring this hook is a "
11308 "somewhat involved process."
11309 msgstr ""
11311 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11312 #: ../en/ch10-hook.xml:909
11313 msgid ""
11314 "Before you begin, you must install the MySQL bindings for Python on the host"
11315 "(s) where you'll be running the hook. If this is not available as a binary "
11316 "package for your system, you can download it from <citation>web:mysql-python</"
11317 "citation>."
11318 msgstr ""
11320 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11321 #: ../en/ch10-hook.xml:916
11322 msgid ""
11323 "Configuration information for this hook lives in the <literal role=\"rc-"
11324 "bugzilla\">bugzilla</literal> section of your <filename role=\"special\"> /."
11325 "hgrc</filename>."
11326 msgstr ""
11328 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11329 #: ../en/ch10-hook.xml:921
11330 msgid ""
11331 "<envar role=\"rc-item-bugzilla\">version</envar>: The version of Bugzilla "
11332 "installed on the server. The database schema that Bugzilla uses changes "
11333 "occasionally, so this hook has to know exactly which schema to use. At the "
11334 "moment, the only version supported is <literal>2.16</literal>."
11335 msgstr ""
11337 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11338 #: ../en/ch10-hook.xml:930
11339 msgid ""
11340 "<envar role=\"rc-item-bugzilla\">host</envar>: The hostname of the MySQL "
11341 "server that stores your Bugzilla data. The database must be configured to "
11342 "allow connections from whatever host you are running the <literal role=\"hook"
11343 "\">bugzilla</literal> hook on."
11344 msgstr ""
11346 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11347 #: ../en/ch10-hook.xml:937
11348 msgid ""
11349 "<envar role=\"rc-item-bugzilla\">user</envar>: The username with which to "
11350 "connect to the MySQL server. The database must be configured to allow this "
11351 "user to connect from whatever host you are running the <literal role=\"hook"
11352 "\">bugzilla</literal> hook on. This user must be able to access and modify "
11353 "Bugzilla tables. The default value of this item is <literal>bugs</literal>, "
11354 "which is the standard name of the Bugzilla user in a MySQL database."
11355 msgstr ""
11357 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11358 #: ../en/ch10-hook.xml:948
11359 msgid ""
11360 "<envar role=\"rc-item-bugzilla\">password</envar>: The MySQL password for the "
11361 "user you configured above. This is stored as plain text, so you should make "
11362 "sure that unauthorised users cannot read the <filename role=\"special\"> /."
11363 "hgrc</filename>\\ file where you store this information."
11364 msgstr ""
11366 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11367 #: ../en/ch10-hook.xml:957
11368 msgid ""
11369 "<envar role=\"rc-item-bugzilla\">db</envar>: The name of the Bugzilla "
11370 "database on the MySQL server. The default value of this item is "
11371 "<literal>bugs</literal>, which is the standard name of the MySQL database "
11372 "where Bugzilla stores its data."
11373 msgstr ""
11375 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11376 #: ../en/ch10-hook.xml:964
11377 msgid ""
11378 "<envar role=\"rc-item-bugzilla\">notify</envar>: If you want Bugzilla to send "
11379 "out a notification email to subscribers after this hook has added a comment "
11380 "to a bug, you will need this hook to run a command whenever it updates the "
11381 "database. The command to run depends on where you have installed Bugzilla, "
11382 "but it will typically look something like this, if you have Bugzilla "
11383 "installed in <filename class=\"directory\">/var/www/html/bugzilla</filename>:"
11384 msgstr ""
11386 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11387 #: ../en/ch10-hook.xml:977
11388 msgid ""
11389 "The Bugzilla <literal>processmail</literal> program expects to be given a bug "
11390 "ID (the hook replaces <quote><literal>%s</literal></quote> with the bug ID) "
11391 "and an email address. It also expects to be able to write to some files in "
11392 "the directory that it runs in. If Bugzilla and this hook are not installed "
11393 "on the same machine, you will need to find a way to run <literal>processmail</"
11394 "literal> on the server where Bugzilla is installed."
11395 msgstr ""
11397 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
11398 #: ../en/ch10-hook.xml:992
11399 msgid "Mapping committer names to Bugzilla user names"
11400 msgstr "提交者的名称与 Bugzilla 用户名称的映射"
11402 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11403 #: ../en/ch10-hook.xml:994
11404 msgid ""
11405 "By default, the <literal role=\"hg-ext\">bugzilla</literal> hook tries to use "
11406 "the email address of a changeset's committer as the Bugzilla user name with "
11407 "which to update a bug. If this does not suit your needs, you can map "
11408 "committer email addresses to Bugzilla user names using a <literal role=\"rc-"
11409 "usermap\">usermap</literal> section."
11410 msgstr ""
11412 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11413 #: ../en/ch10-hook.xml:1003
11414 msgid ""
11415 "Each item in the <literal role=\"rc-usermap\">usermap</literal> section "
11416 "contains an email address on the left, and a Bugzilla user name on the right."
11417 msgstr ""
11419 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11420 #: ../en/ch10-hook.xml:1010
11421 msgid ""
11422 "You can either keep the <literal role=\"rc-usermap\">usermap</literal> data "
11423 "in a normal <filename role=\"special\">~/.hgrc</filename>, or tell the "
11424 "<literal role=\"hg-ext\">bugzilla</literal> hook to read the information from "
11425 "an external <filename>usermap</filename> file. In the latter case, you can "
11426 "store <filename>usermap</filename> data by itself in (for example) a user-"
11427 "modifiable repository. This makes it possible to let your users maintain "
11428 "their own <envar role=\"rc-item-bugzilla\">usermap</envar> entries. The main "
11429 "<filename role=\"special\"> /.hgrc</filename>\\ file might look like this:"
11430 msgstr ""
11432 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11433 #: ../en/ch10-hook.xml:1026
11434 msgid ""
11435 "While the <filename>usermap</filename> file that it refers to might look like "
11436 "this:"
11437 msgstr ""
11439 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
11440 #: ../en/ch10-hook.xml:1035
11441 msgid "Configuring the text that gets added to a bug"
11442 msgstr "配置增加到问题中的正文"
11444 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11445 #: ../en/ch10-hook.xml:1037
11446 msgid ""
11447 "You can configure the text that this hook adds as a comment; you specify it "
11448 "in the form of a Mercurial template. Several <filename role=\"special\"> /."
11449 "hgrc</filename>\\ entries (still in the <literal role=\"rc-bugzilla"
11450 "\">bugzilla</literal> section) control this behaviour."
11451 msgstr ""
11453 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11454 #: ../en/ch10-hook.xml:1044
11455 msgid ""
11456 "<literal>strip</literal>: The number of leading path elements to strip from a "
11457 "repository's path name to construct a partial path for a URL. For example, if "
11458 "the repositories on your server live under <filename class=\"directory\">/"
11459 "home/hg/repos</filename>, and you have a repository whose path is <filename "
11460 "class=\"directory\">/home/hg/repos/app/tests</filename>, then setting "
11461 "<literal>strip</literal> to <literal>4</literal> will give a partial path of "
11462 "<filename class=\"directory\">app/tests</filename>. The hook will make this "
11463 "partial path available when expanding a template, as <literal>webroot</"
11464 "literal>."
11465 msgstr ""
11467 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11468 #: ../en/ch10-hook.xml:1058
11469 msgid ""
11470 "<literal>template</literal>: The text of the template to use. In addition to "
11471 "the usual changeset-related variables, this template can use <literal>hgweb</"
11472 "literal> (the value of the <literal>hgweb</literal> configuration item above) "
11473 "and <literal>webroot</literal> (the path constructed using <literal>strip</"
11474 "literal> above)."
11475 msgstr ""
11477 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11478 #: ../en/ch10-hook.xml:1068
11479 msgid ""
11480 "In addition, you can add a <envar role=\"rc-item-web\">baseurl</envar> item "
11481 "to the <literal role=\"rc-web\">web</literal> section of your <filename role="
11482 "\"special\"> /.hgrc</filename>. The <literal role=\"hg-ext\">bugzilla</"
11483 "literal> hook will make this available when expanding a template, as the base "
11484 "string to use when constructing a URL that will let users browse from a "
11485 "Bugzilla comment to view a changeset. Example:"
11486 msgstr ""
11488 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11489 #: ../en/ch10-hook.xml:1080
11490 msgid ""
11491 "Here is an example set of <literal role=\"hg-ext\">bugzilla</literal> hook "
11492 "config information."
11493 msgstr ""
11495 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11496 #: ../en/ch10-hook.xml:1097
11497 msgid ""
11498 "The most common problems with configuring the <literal role=\"hg-ext"
11499 "\">bugzilla</literal> hook relate to running Bugzilla's "
11500 "<filename>processmail</filename> script and mapping committer names to user "
11501 "names."
11502 msgstr ""
11504 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11505 #: ../en/ch10-hook.xml:1103
11506 msgid ""
11507 "Recall from section <xref linkend=\"sec.hook.bugzilla.config\"/> above that "
11508 "the user that runs the Mercurial process on the server is also the one that "
11509 "will run the <filename>processmail</filename> script. The "
11510 "<filename>processmail</filename> script sometimes causes Bugzilla to write to "
11511 "files in its configuration directory, and Bugzilla's configuration files are "
11512 "usually owned by the user that your web server runs under."
11513 msgstr ""
11515 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11516 #: ../en/ch10-hook.xml:1114
11517 msgid ""
11518 "You can cause <filename>processmail</filename> to be run with the suitable "
11519 "user's identity using the <command>sudo</command> command. Here is an "
11520 "example entry for a <filename>sudoers</filename> file."
11521 msgstr ""
11523 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11524 #: ../en/ch10-hook.xml:1122
11525 msgid ""
11526 "This allows the <literal>hg_user</literal> user to run a "
11527 "<filename>processmail-wrapper</filename> program under the identity of "
11528 "<literal>httpd_user</literal>."
11529 msgstr ""
11531 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11532 #: ../en/ch10-hook.xml:1127
11533 msgid ""
11534 "This indirection through a wrapper script is necessary, because "
11535 "<filename>processmail</filename> expects to be run with its current directory "
11536 "set to wherever you installed Bugzilla; you can't specify that kind of "
11537 "constraint in a <filename>sudoers</filename> file. The contents of the "
11538 "wrapper script are simple:"
11539 msgstr ""
11541 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11542 #: ../en/ch10-hook.xml:1136
11543 msgid ""
11544 "It doesn't seem to matter what email address you pass to "
11545 "<filename>processmail</filename>."
11546 msgstr ""
11548 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11549 #: ../en/ch10-hook.xml:1140
11550 msgid ""
11551 "If your <literal role=\"rc-usermap\">usermap</literal> is not set up "
11552 "correctly, users will see an error message from the <literal role=\"hg-ext"
11553 "\">bugzilla</literal> hook when they push changes to the server. The error "
11554 "message will look like this:"
11555 msgstr ""
11557 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11558 #: ../en/ch10-hook.xml:1148
11559 msgid ""
11560 "What this means is that the committer's address, <literal>john.q."
11561 "public@example.com</literal>, is not a valid Bugzilla user name, nor does it "
11562 "have an entry in your <literal role=\"rc-usermap\">usermap</literal> that "
11563 "maps it to a valid Bugzilla user name."
11564 msgstr ""
11566 #. type: Content of: <book><chapter><sect1><sect2><title>
11567 #: ../en/ch10-hook.xml:1158
11568 msgid ""
11569 "<literal role=\"hg-ext\">notify</literal>&emdash;send email notifications"
11570 msgstr "<literal role=\"hg-ext\">notify</literal>&emdash;邮件通知"
11572 #. type: Content of: <book><chapter><sect1><sect2><para>
11573 #: ../en/ch10-hook.xml:1161
11574 msgid ""
11575 "Although Mercurial's built-in web server provides RSS feeds of changes in "
11576 "every repository, many people prefer to receive change notifications via "
11577 "email. The <literal role=\"hg-ext\">notify</literal> hook lets you send out "
11578 "notifications to a set of email addresses whenever changesets arrive that "
11579 "those subscribers are interested in."
11580 msgstr ""
11582 #. type: Content of: <book><chapter><sect1><sect2><para>
11583 #: ../en/ch10-hook.xml:1169
11584 msgid ""
11585 "As with the <literal role=\"hg-ext\">bugzilla</literal> hook, the <literal "
11586 "role=\"hg-ext\">notify</literal> hook is template-driven, so you can "
11587 "customise the contents of the notification messages that it sends."
11588 msgstr ""
11590 #. type: Content of: <book><chapter><sect1><sect2><para>
11591 #: ../en/ch10-hook.xml:1175
11592 msgid ""
11593 "By default, the <literal role=\"hg-ext\">notify</literal> hook includes a "
11594 "diff of every changeset that it sends out; you can limit the size of the "
11595 "diff, or turn this feature off entirely. It is useful for letting "
11596 "subscribers review changes immediately, rather than clicking to follow a URL."
11597 msgstr ""
11599 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
11600 #: ../en/ch10-hook.xml:1183
11601 msgid "Configuring the <literal role=\"hg-ext\">notify</literal> hook"
11602 msgstr "配置 <literal role=\"hg-ext\">notify</literal> 钩子"
11604 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11605 #: ../en/ch10-hook.xml:1186
11606 msgid ""
11607 "You can set up the <literal role=\"hg-ext\">notify</literal> hook to send one "
11608 "email message per incoming changeset, or one per incoming group of changesets "
11609 "(all those that arrived in a single pull or push)."
11610 msgstr ""
11612 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11613 #: ../en/ch10-hook.xml:1197
11614 msgid ""
11615 "Configuration information for this hook lives in the <literal role=\"rc-notify"
11616 "\">notify</literal> section of a <filename role=\"special\"> /.hgrc</filename>"
11617 "\\ file."
11618 msgstr ""
11620 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11621 #: ../en/ch10-hook.xml:1202
11622 msgid ""
11623 "<envar role=\"rc-item-notify\">test</envar>: By default, this hook does not "
11624 "send out email at all; instead, it prints the message that it "
11625 "<emphasis>would</emphasis> send. Set this item to <literal>false</literal> "
11626 "to allow email to be sent. The reason that sending of email is turned off by "
11627 "default is that it takes several tries to configure this extension exactly as "
11628 "you would like, and it would be bad form to spam subscribers with a number of "
11629 "<quote>broken</quote> notifications while you debug your configuration."
11630 msgstr ""
11632 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11633 #: ../en/ch10-hook.xml:1214
11634 msgid ""
11635 "<envar role=\"rc-item-notify\">config</envar>: The path to a configuration "
11636 "file that contains subscription information. This is kept separate from the "
11637 "main <filename role=\"special\"> /.hgrc</filename>\\ so that you can maintain "
11638 "it in a repository of its own. People can then clone that repository, update "
11639 "their subscriptions, and push the changes back to your server."
11640 msgstr ""
11642 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11643 #: ../en/ch10-hook.xml:1223
11644 msgid ""
11645 "<envar role=\"rc-item-notify\">strip</envar>: The number of leading path "
11646 "separator characters to strip from a repository's path, when deciding whether "
11647 "a repository has subscribers. For example, if the repositories on your "
11648 "server live in <filename class=\"directory\">/home/hg/repos</filename>, and "
11649 "<literal role=\"hg-ext\">notify</literal> is considering a repository named "
11650 "<filename class=\"directory\">/home/hg/repos/shared/test</filename>, setting "
11651 "<envar role=\"rc-item-notify\">strip</envar> to <literal>4</literal> will "
11652 "cause <literal role=\"hg-ext\">notify</literal> to trim the path it considers "
11653 "down to <filename class=\"directory\">shared/test</filename>, and it will "
11654 "match subscribers against that."
11655 msgstr ""
11657 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11658 #: ../en/ch10-hook.xml:1240
11659 msgid ""
11660 "<envar role=\"rc-item-notify\">template</envar>: The template text to use "
11661 "when sending messages. This specifies both the contents of the message "
11662 "header and its body."
11663 msgstr ""
11665 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11666 #: ../en/ch10-hook.xml:1246
11667 msgid ""
11668 "<envar role=\"rc-item-notify\">maxdiff</envar>: The maximum number of lines "
11669 "of diff data to append to the end of a message. If a diff is longer than "
11670 "this, it is truncated. By default, this is set to 300. Set this to "
11671 "<literal>0</literal> to omit diffs from notification emails."
11672 msgstr ""
11674 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11675 #: ../en/ch10-hook.xml:1255
11676 msgid ""
11677 "<envar role=\"rc-item-notify\">sources</envar>: A list of sources of "
11678 "changesets to consider. This lets you limit <literal role=\"hg-ext\">notify</"
11679 "literal> to only sending out email about changes that remote users pushed "
11680 "into this repository via a server, for example. See section <xref linkend="
11681 "\"sec.hook.sources\"/> for the sources you can specify here."
11682 msgstr ""
11684 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11685 #: ../en/ch10-hook.xml:1267
11686 msgid ""
11687 "If you set the <envar role=\"rc-item-web\">baseurl</envar> item in the "
11688 "<literal role=\"rc-web\">web</literal> section, you can use it in a template; "
11689 "it will be available as <literal>webroot</literal>."
11690 msgstr ""
11692 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11693 #: ../en/ch10-hook.xml:1273
11694 msgid ""
11695 "Here is an example set of <literal role=\"hg-ext\">notify</literal> "
11696 "configuration information."
11697 msgstr ""
11699 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11700 #: ../en/ch10-hook.xml:1289
11701 msgid "This will produce a message that looks like the following:"
11702 msgstr ""
11704 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11705 #: ../en/ch10-hook.xml:1310
11706 msgid ""
11707 "Do not forget that by default, the <literal role=\"hg-ext\">notify</literal> "
11708 "extension <emphasis>will not send any mail</emphasis> until you explicitly "
11709 "configure it to do so, by setting <envar role=\"rc-item-notify\">test</envar> "
11710 "to <literal>false</literal>. Until you do that, it simply prints the message "
11711 "it <emphasis>would</emphasis> send."
11712 msgstr ""
11714 #. type: Content of: <book><chapter><sect1><title>
11715 #: ../en/ch10-hook.xml:1322
11716 msgid "Information for writers of hooks"
11717 msgstr "编写钩子的信息"
11719 #. type: Content of: <book><chapter><sect1><sect2><title>
11720 #: ../en/ch10-hook.xml:1325
11721 msgid "In-process hook execution"
11722 msgstr "进程内钩子的执行"
11724 #. type: Content of: <book><chapter><sect1><sect2><para>
11725 #: ../en/ch10-hook.xml:1327
11726 msgid "An in-process hook is called with arguments of the following form:"
11727 msgstr ""
11729 #. type: Content of: <book><chapter><sect1><sect2><para>
11730 #: ../en/ch10-hook.xml:1333
11731 msgid ""
11732 "The <literal>ui</literal> parameter is a <literal role=\"py-mod-mercurial.ui"
11733 "\">ui</literal> object. The <literal>repo</literal> parameter is a <literal "
11734 "role=\"py-mod-mercurial.localrepo\">localrepository</literal> object. The "
11735 "names and values of the <literal>**kwargs</literal> parameters depend on the "
11736 "hook being invoked, with the following common features:"
11737 msgstr ""
11739 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
11740 #: ../en/ch10-hook.xml:1342
11741 msgid ""
11742 "If a parameter is named <literal>node</literal> or <literal>parentN</"
11743 "literal>, it will contain a hexadecimal changeset ID. The empty string is "
11744 "used to represent <quote>null changeset ID</quote> instead of a string of "
11745 "zeroes."
11746 msgstr ""
11748 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
11749 #: ../en/ch10-hook.xml:1349
11750 msgid ""
11751 "If a parameter is named <literal>url</literal>, it will contain the URL of a "
11752 "remote repository, if that can be determined."
11753 msgstr ""
11755 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
11756 #: ../en/ch10-hook.xml:1354
11757 msgid ""
11758 "Boolean-valued parameters are represented as Python <literal>bool</literal> "
11759 "objects."
11760 msgstr ""
11762 #. type: Content of: <book><chapter><sect1><sect2><para>
11763 #: ../en/ch10-hook.xml:1359
11764 msgid ""
11765 "An in-process hook is called without a change to the process's working "
11766 "directory (unlike external hooks, which are run in the root of the "
11767 "repository). It must not change the process's working directory, or it will "
11768 "cause any calls it makes into the Mercurial API to fail."
11769 msgstr ""
11771 #. type: Content of: <book><chapter><sect1><sect2><para>
11772 #: ../en/ch10-hook.xml:1366
11773 msgid ""
11774 "If a hook returns a boolean <quote>false</quote> value, it is considered to "
11775 "have succeeded. If it returns a boolean <quote>true</quote> value or raises "
11776 "an exception, it is considered to have failed. A useful way to think of the "
11777 "calling convention is <quote>tell me if you fail</quote>."
11778 msgstr ""
11780 #. type: Content of: <book><chapter><sect1><sect2><para>
11781 #: ../en/ch10-hook.xml:1373
11782 msgid ""
11783 "Note that changeset IDs are passed into Python hooks as hexadecimal strings, "
11784 "not the binary hashes that Mercurial's APIs normally use. To convert a hash "
11785 "from hex to binary, use the \\pymodfunc{mercurial.node}{bin} function."
11786 msgstr ""
11788 #. type: Content of: <book><chapter><sect1><sect2><title>
11789 #: ../en/ch10-hook.xml:1381
11790 msgid "External hook execution"
11791 msgstr "外部钩子的执行"
11793 #. type: Content of: <book><chapter><sect1><sect2><para>
11794 #: ../en/ch10-hook.xml:1383
11795 msgid ""
11796 "An external hook is passed to the shell of the user running Mercurial. "
11797 "Features of that shell, such as variable substitution and command "
11798 "redirection, are available. The hook is run in the root directory of the "
11799 "repository (unlike in-process hooks, which are run in the same directory that "
11800 "Mercurial was run in)."
11801 msgstr ""
11803 #. type: Content of: <book><chapter><sect1><sect2><para>
11804 #: ../en/ch10-hook.xml:1391
11805 msgid ""
11806 "Hook parameters are passed to the hook as environment variables. Each "
11807 "environment variable's name is converted in upper case and prefixed with the "
11808 "string <quote><literal>HG_</literal></quote>. For example, if the name of a "
11809 "parameter is <quote><literal>node</literal></quote>, the name of the "
11810 "environment variable representing that parameter will be "
11811 "<quote><literal>HG_NODE</literal></quote>."
11812 msgstr ""
11814 #. type: Content of: <book><chapter><sect1><sect2><para>
11815 #: ../en/ch10-hook.xml:1400
11816 msgid ""
11817 "A boolean parameter is represented as the string <quote><literal>1</literal></"
11818 "quote> for <quote>true</quote>, <quote><literal>0</literal></quote> for "
11819 "<quote>false</quote>. If an environment variable is named <envar>HG_NODE</"
11820 "envar>, <envar>HG_PARENT1</envar> or <envar>HG_PARENT2</envar>, it contains a "
11821 "changeset ID represented as a hexadecimal string. The empty string is used "
11822 "to represent <quote>null changeset ID</quote> instead of a string of zeroes. "
11823 "If an environment variable is named <envar>HG_URL</envar>, it will contain "
11824 "the URL of a remote repository, if that can be determined."
11825 msgstr ""
11827 #. type: Content of: <book><chapter><sect1><sect2><para>
11828 #: ../en/ch10-hook.xml:1412
11829 msgid ""
11830 "If a hook exits with a status of zero, it is considered to have succeeded. "
11831 "If it exits with a non-zero status, it is considered to have failed."
11832 msgstr ""
11834 #. type: Content of: <book><chapter><sect1><sect2><title>
11835 #: ../en/ch10-hook.xml:1419
11836 msgid "Finding out where changesets come from"
11837 msgstr "检查修改集来自何处"
11839 #. type: Content of: <book><chapter><sect1><sect2><para>
11840 #: ../en/ch10-hook.xml:1421
11841 msgid ""
11842 "A hook that involves the transfer of changesets between a local repository "
11843 "and another may be able to find out information about the <quote>far side</"
11844 "quote>. Mercurial knows <emphasis>how</emphasis> changes are being "
11845 "transferred, and in many cases <emphasis>where</emphasis> they are being "
11846 "transferred to or from."
11847 msgstr ""
11849 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
11850 #: ../en/ch10-hook.xml:1430
11851 msgid "Sources of changesets"
11852 msgstr "修改集的来源"
11854 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11855 #: ../en/ch10-hook.xml:1432
11856 msgid ""
11857 "Mercurial will tell a hook what means are, or were, used to transfer "
11858 "changesets between repositories. This is provided by Mercurial in a Python "
11859 "parameter named <literal>source</literal>, or an environment variable named "
11860 "<envar>HG_SOURCE</envar>."
11861 msgstr ""
11863 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11864 #: ../en/ch10-hook.xml:1440
11865 msgid ""
11866 "<literal>serve</literal>: Changesets are transferred to or from a remote "
11867 "repository over http or ssh."
11868 msgstr ""
11870 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11871 #: ../en/ch10-hook.xml:1445
11872 msgid ""
11873 "<literal>pull</literal>: Changesets are being transferred via a pull from one "
11874 "repository into another."
11875 msgstr ""
11877 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11878 #: ../en/ch10-hook.xml:1450
11879 msgid ""
11880 "<literal>push</literal>: Changesets are being transferred via a push from one "
11881 "repository into another."
11882 msgstr ""
11884 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11885 #: ../en/ch10-hook.xml:1455
11886 msgid ""
11887 "<literal>bundle</literal>: Changesets are being transferred to or from a "
11888 "bundle."
11889 msgstr ""
11891 #. type: Content of: <book><chapter><sect1><sect2><sect3><title>
11892 #: ../en/ch10-hook.xml:1462
11893 msgid "Where changes are going&emdash;remote repository URLs"
11894 msgstr "修改集要到哪里&emdash;远程版本库的地址"
11896 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11897 #: ../en/ch10-hook.xml:1465
11898 msgid ""
11899 "When possible, Mercurial will tell a hook the location of the <quote>far "
11900 "side</quote> of an activity that transfers changeset data between "
11901 "repositories. This is provided by Mercurial in a Python parameter named "
11902 "<literal>url</literal>, or an environment variable named <envar>HG_URL</"
11903 "envar>."
11904 msgstr ""
11906 #. type: Content of: <book><chapter><sect1><sect2><sect3><para>
11907 #: ../en/ch10-hook.xml:1473
11908 msgid ""
11909 "This information is not always known. If a hook is invoked in a repository "
11910 "that is being served via http or ssh, Mercurial cannot tell where the remote "
11911 "repository is, but it may know where the client is connecting from. In such "
11912 "cases, the URL will take one of the following forms:"
11913 msgstr ""
11915 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11916 #: ../en/ch10-hook.xml:1480
11917 msgid ""
11918 "<literal>remote:ssh:1.2.3.4</literal>&emdash;remote ssh client, at the IP "
11919 "address <literal>1.2.3.4</literal>."
11920 msgstr ""
11922 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11923 #: ../en/ch10-hook.xml:1485
11924 msgid ""
11925 "<literal>remote:http:1.2.3.4</literal>&emdash;remote http client, at the IP "
11926 "address <literal>1.2.3.4</literal>. If the client is using SSL, this will be "
11927 "of the form <literal>remote:https:1.2.3.4</literal>."
11928 msgstr ""
11930 #. type: Content of: <book><chapter><sect1><sect2><sect3><itemizedlist><listitem><para>
11931 #: ../en/ch10-hook.xml:1492
11932 msgid "Empty&emdash;no information could be discovered about the remote client."
11933 msgstr ""
11935 #. type: Content of: <book><chapter><sect1><title>
11936 #: ../en/ch10-hook.xml:1501
11937 msgid "Hook reference"
11938 msgstr "钩子参考"
11940 #. type: Content of: <book><chapter><sect1><sect2><title>
11941 #: ../en/ch10-hook.xml:1504
11942 msgid ""
11943 "<literal role=\"hook\">changegroup</literal>&emdash;after remote changesets "
11944 "added"
11945 msgstr "<literal role=\"hook\">changegroup</literal>&emdash;增加远程修改集之后"
11947 #. type: Content of: <book><chapter><sect1><sect2><para>
11948 #: ../en/ch10-hook.xml:1507
11949 msgid ""
11950 "This hook is run after a group of pre-existing changesets has been added to "
11951 "the repository, for example via a <command role=\"hg-cmd\">hg pull</command> "
11952 "or <command role=\"hg-cmd\">hg unbundle</command>. This hook is run once per "
11953 "operation that added one or more changesets. This is in contrast to the "
11954 "<literal role=\"hook\">incoming</literal> hook, which is run once per "
11955 "changeset, regardless of whether the changesets arrive in a group."
11956 msgstr ""
11958 #. type: Content of: <book><chapter><sect1><sect2><para>
11959 #: ../en/ch10-hook.xml:1517
11960 msgid ""
11961 "Some possible uses for this hook include kicking off an automated build or "
11962 "test of the added changesets, updating a bug database, or notifying "
11963 "subscribers that a repository contains new changes."
11964 msgstr ""
11966 #. type: Content of: <book><chapter><sect1><sect2><para>
11967 #: ../en/ch10-hook.xml:1523 ../en/ch10-hook.xml:1564 ../en/ch10-hook.xml:1607
11968 #: ../en/ch10-hook.xml:1649 ../en/ch10-hook.xml:1704 ../en/ch10-hook.xml:1744
11969 #: ../en/ch10-hook.xml:1780 ../en/ch10-hook.xml:1815 ../en/ch10-hook.xml:1877
11970 #: ../en/ch10-hook.xml:1935 ../en/ch10-hook.xml:1969 ../en/ch10-hook.xml:1997
11971 msgid "Parameters to this hook:"
11972 msgstr ""
11974 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
11975 #: ../en/ch10-hook.xml:1526 ../en/ch10-hook.xml:1880
11976 msgid ""
11977 "<literal>node</literal>: A changeset ID. The changeset ID of the first "
11978 "changeset in the group that was added. All changesets between this and "
11979 "\\index{tags!<literal>tip</literal>}<literal>tip</literal>, inclusive, were "
11980 "added by a single <command role=\"hg-cmd\">hg pull</command>, <command role="
11981 "\"hg-cmd\">hg push</command> or <command role=\"hg-cmd\">hg unbundle</"
11982 "command>."
11983 msgstr ""
11985 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
11986 #: ../en/ch10-hook.xml:1536 ../en/ch10-hook.xml:1614 ../en/ch10-hook.xml:1707
11987 #: ../en/ch10-hook.xml:1890
11988 msgid ""
11989 "<literal>source</literal>: A string. The source of these changes. See "
11990 "section <xref linkend=\"sec.hook.sources\"/> for details."
11991 msgstr ""
11993 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
11994 #: ../en/ch10-hook.xml:1541 ../en/ch10-hook.xml:1619 ../en/ch10-hook.xml:1670
11995 #: ../en/ch10-hook.xml:1712 ../en/ch10-hook.xml:1794 ../en/ch10-hook.xml:1895
11996 msgid ""
11997 "<literal>url</literal>: A URL. The location of the remote repository, if "
11998 "known. See section <xref linkend=\"sec.hook.url\"/> for more information."
11999 msgstr ""
12001 #. type: Content of: <book><chapter><sect1><sect2><para>
12002 #: ../en/ch10-hook.xml:1548
12003 msgid ""
12004 "See also: <literal role=\"hook\">incoming</literal> (section <xref linkend="
12005 "\"sec.hook.incoming\"/>), <literal role=\"hook\">prechangegroup</literal> "
12006 "(section <xref linkend=\"sec.hook.prechangegroup\"/>), <literal role=\"hook"
12007 "\">pretxnchangegroup</literal> (section <xref linkend=\"sec.hook."
12008 "pretxnchangegroup\"/>)"
12009 msgstr ""
12011 #. type: Content of: <book><chapter><sect1><sect2><title>
12012 #: ../en/ch10-hook.xml:1558
12013 msgid ""
12014 "<literal role=\"hook\">commit</literal>&emdash;after a new changeset is "
12015 "created"
12016 msgstr "<literal role=\"hook\">commit</literal>&emdash;创建新修改集之后"
12018 #. type: Content of: <book><chapter><sect1><sect2><para>
12019 #: ../en/ch10-hook.xml:1561
12020 msgid "This hook is run after a new changeset has been created."
12021 msgstr ""
12023 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12024 #: ../en/ch10-hook.xml:1567 ../en/ch10-hook.xml:1938
12025 msgid ""
12026 "<literal>node</literal>: A changeset ID. The changeset ID of the newly "
12027 "committed changeset."
12028 msgstr ""
12030 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12031 #: ../en/ch10-hook.xml:1571 ../en/ch10-hook.xml:1942
12032 msgid ""
12033 "<literal>parent1</literal>: A changeset ID. The changeset ID of the first "
12034 "parent of the newly committed changeset."
12035 msgstr ""
12037 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12038 #: ../en/ch10-hook.xml:1576 ../en/ch10-hook.xml:1947
12039 msgid ""
12040 "<literal>parent2</literal>: A changeset ID. The changeset ID of the second "
12041 "parent of the newly committed changeset."
12042 msgstr ""
12044 #. type: Content of: <book><chapter><sect1><sect2><para>
12045 #: ../en/ch10-hook.xml:1582
12046 msgid ""
12047 "See also: <literal role=\"hook\">precommit</literal> (section <xref linkend="
12048 "\"sec.hook.precommit\"/>), <literal role=\"hook\">pretxncommit</literal> "
12049 "(section <xref linkend=\"sec.hook.pretxncommit\"/>)"
12050 msgstr ""
12052 #. type: Content of: <book><chapter><sect1><sect2><title>
12053 #: ../en/ch10-hook.xml:1590
12054 msgid ""
12055 "<literal role=\"hook\">incoming</literal>&emdash;after one remote changeset "
12056 "is added"
12057 msgstr "<literal role=\"hook\">incoming</literal>&emdash;增加远程修改集之后"
12059 #. type: Content of: <book><chapter><sect1><sect2><para>
12060 #: ../en/ch10-hook.xml:1593
12061 msgid ""
12062 "This hook is run after a pre-existing changeset has been added to the "
12063 "repository, for example via a <command role=\"hg-cmd\">hg push</command>. If "
12064 "a group of changesets was added in a single operation, this hook is called "
12065 "once for each added changeset."
12066 msgstr ""
12068 #. type: Content of: <book><chapter><sect1><sect2><para>
12069 #: ../en/ch10-hook.xml:1600
12070 msgid ""
12071 "You can use this hook for the same purposes as the <literal role=\"hook"
12072 "\">changegroup</literal> hook (section <xref linkend=\"sec.hook.changegroup\"/"
12073 ">); it's simply more convenient sometimes to run a hook once per group of "
12074 "changesets, while other times it's handier once per changeset."
12075 msgstr ""
12077 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12078 #: ../en/ch10-hook.xml:1610
12079 msgid ""
12080 "<literal>node</literal>: A changeset ID. The ID of the newly added changeset."
12081 msgstr ""
12083 #. type: Content of: <book><chapter><sect1><sect2><para>
12084 #: ../en/ch10-hook.xml:1626
12085 msgid ""
12086 "See also: <literal role=\"hook\">changegroup</literal> (section <xref linkend="
12087 "\"sec.hook.changegroup\"/>) <literal role=\"hook\">prechangegroup</literal> "
12088 "(section <xref linkend=\"sec.hook.prechangegroup\"/>), <literal role=\"hook"
12089 "\">pretxnchangegroup</literal> (section <xref linkend=\"sec.hook."
12090 "pretxnchangegroup\"/>)"
12091 msgstr ""
12093 #. type: Content of: <book><chapter><sect1><sect2><title>
12094 #: ../en/ch10-hook.xml:1636
12095 msgid ""
12096 "<literal role=\"hook\">outgoing</literal>&emdash;after changesets are "
12097 "propagated"
12098 msgstr "<literal role=\"hook\">outgoing</literal>&emdash;传播修改集之后"
12100 #. type: Content of: <book><chapter><sect1><sect2><para>
12101 #: ../en/ch10-hook.xml:1639
12102 msgid ""
12103 "This hook is run after a group of changesets has been propagated out of this "
12104 "repository, for example by a <command role=\"hg-cmd\">hg push</command> or "
12105 "<command role=\"hg-cmd\">hg bundle</command> command."
12106 msgstr ""
12108 #. type: Content of: <book><chapter><sect1><sect2><para>
12109 #: ../en/ch10-hook.xml:1645
12110 msgid ""
12111 "One possible use for this hook is to notify administrators that changes have "
12112 "been pulled."
12113 msgstr ""
12115 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12116 #: ../en/ch10-hook.xml:1652
12117 msgid ""
12118 "<literal>node</literal>: A changeset ID. The changeset ID of the first "
12119 "changeset of the group that was sent."
12120 msgstr ""
12122 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12123 #: ../en/ch10-hook.xml:1657
12124 msgid ""
12125 "<literal>source</literal>: A string. The source of the of the operation (see "
12126 "section <xref linkend=\"sec.hook.sources\"/>). If a remote client pulled "
12127 "changes from this repository, <literal>source</literal> will be "
12128 "<literal>serve</literal>. If the client that obtained changes from this "
12129 "repository was local, <literal>source</literal> will be <literal>bundle</"
12130 "literal>, <literal>pull</literal>, or <literal>push</literal>, depending on "
12131 "the operation the client performed."
12132 msgstr ""
12134 #. type: Content of: <book><chapter><sect1><sect2><para>
12135 #: ../en/ch10-hook.xml:1677
12136 msgid ""
12137 "See also: <literal role=\"hook\">preoutgoing</literal> (section <xref linkend="
12138 "\"sec.hook.preoutgoing\"/>)"
12139 msgstr ""
12141 #. type: Content of: <book><chapter><sect1><sect2><title>
12142 #: ../en/ch10-hook.xml:1683
12143 msgid ""
12144 "<literal role=\"hook\">prechangegroup</literal>&emdash;before starting to add "
12145 "remote changesets"
12146 msgstr ""
12147 "<literal role=\"hook\">prechangegroup</literal>&emdash;增加远程修改集之前"
12149 #. type: Content of: <book><chapter><sect1><sect2><para>
12150 #: ../en/ch10-hook.xml:1687
12151 msgid ""
12152 "This controlling hook is run before Mercurial begins to add a group of "
12153 "changesets from another repository."
12154 msgstr ""
12156 #. type: Content of: <book><chapter><sect1><sect2><para>
12157 #: ../en/ch10-hook.xml:1691
12158 msgid ""
12159 "This hook does not have any information about the changesets to be added, "
12160 "because it is run before transmission of those changesets is allowed to "
12161 "begin. If this hook fails, the changesets will not be transmitted."
12162 msgstr ""
12164 #. type: Content of: <book><chapter><sect1><sect2><para>
12165 #: ../en/ch10-hook.xml:1697
12166 msgid ""
12167 "One use for this hook is to prevent external changes from being added to a "
12168 "repository. For example, you could use this to <quote>freeze</quote> a "
12169 "server-hosted branch temporarily or permanently so that users cannot push to "
12170 "it, while still allowing a local administrator to modify the repository."
12171 msgstr ""
12173 #. type: Content of: <book><chapter><sect1><sect2><para>
12174 #: ../en/ch10-hook.xml:1719
12175 msgid ""
12176 "See also: <literal role=\"hook\">changegroup</literal> (section <xref linkend="
12177 "\"sec.hook.changegroup\"/>), <literal role=\"hook\">incoming</literal> "
12178 "(section <xref linkend=\"sec.hook.incoming\"/>), , <literal role=\"hook"
12179 "\">pretxnchangegroup</literal> (section <xref linkend=\"sec.hook."
12180 "pretxnchangegroup\"/>)"
12181 msgstr ""
12183 #. type: Content of: <book><chapter><sect1><sect2><title>
12184 #: ../en/ch10-hook.xml:1729
12185 msgid ""
12186 "<literal role=\"hook\">precommit</literal>&emdash;before starting to commit a "
12187 "changeset"
12188 msgstr "<literal role=\"hook\">precommit</literal>&emdash;提交修改集之前"
12190 #. type: Content of: <book><chapter><sect1><sect2><para>
12191 #: ../en/ch10-hook.xml:1732
12192 msgid ""
12193 "This hook is run before Mercurial begins to commit a new changeset. It is run "
12194 "before Mercurial has any of the metadata for the commit, such as the files to "
12195 "be committed, the commit message, or the commit date."
12196 msgstr ""
12198 #. type: Content of: <book><chapter><sect1><sect2><para>
12199 #: ../en/ch10-hook.xml:1738
12200 msgid ""
12201 "One use for this hook is to disable the ability to commit new changesets, "
12202 "while still allowing incoming changesets. Another is to run a build or test, "
12203 "and only allow the commit to begin if the build or test succeeds."
12204 msgstr ""
12206 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12207 #: ../en/ch10-hook.xml:1747
12208 msgid ""
12209 "<literal>parent1</literal>: A changeset ID. The changeset ID of the first "
12210 "parent of the working directory."
12211 msgstr ""
12213 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12214 #: ../en/ch10-hook.xml:1752
12215 msgid ""
12216 "<literal>parent2</literal>: A changeset ID. The changeset ID of the second "
12217 "parent of the working directory."
12218 msgstr ""
12220 #. type: Content of: <book><chapter><sect1><sect2><para>
12221 #: ../en/ch10-hook.xml:1757
12222 msgid ""
12223 "If the commit proceeds, the parents of the working directory will become the "
12224 "parents of the new changeset."
12225 msgstr ""
12227 #. type: Content of: <book><chapter><sect1><sect2><para>
12228 #: ../en/ch10-hook.xml:1761
12229 msgid ""
12230 "See also: <literal role=\"hook\">commit</literal> (section <xref linkend="
12231 "\"sec.hook.commit\"/>), <literal role=\"hook\">pretxncommit</literal> "
12232 "(section <xref linkend=\"sec.hook.pretxncommit\"/>)"
12233 msgstr ""
12235 #. type: Content of: <book><chapter><sect1><sect2><title>
12236 #: ../en/ch10-hook.xml:1769
12237 msgid ""
12238 "<literal role=\"hook\">preoutgoing</literal>&emdash;before starting to "
12239 "propagate changesets"
12240 msgstr "<literal role=\"hook\">preoutgoing</literal>&emdash;传播修改集之前"
12242 #. type: Content of: <book><chapter><sect1><sect2><para>
12243 #: ../en/ch10-hook.xml:1772
12244 msgid ""
12245 "This hook is invoked before Mercurial knows the identities of the changesets "
12246 "to be transmitted."
12247 msgstr ""
12249 #. type: Content of: <book><chapter><sect1><sect2><para>
12250 #: ../en/ch10-hook.xml:1776
12251 msgid ""
12252 "One use for this hook is to prevent changes from being transmitted to another "
12253 "repository."
12254 msgstr ""
12256 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12257 #: ../en/ch10-hook.xml:1783
12258 msgid ""
12259 "<literal>source</literal>: A string. The source of the operation that is "
12260 "attempting to obtain changes from this repository (see section <xref linkend="
12261 "\"sec.hook.sources\"/>). See the documentation for the <literal>source</"
12262 "literal> parameter to the <literal role=\"hook\">outgoing</literal> hook, in "
12263 "section <xref linkend=\"sec.hook.outgoing\"/>, for possible values of this "
12264 "parameter."
12265 msgstr ""
12267 #. type: Content of: <book><chapter><sect1><sect2><para>
12268 #: ../en/ch10-hook.xml:1801
12269 msgid ""
12270 "See also: <literal role=\"hook\">outgoing</literal> (section <xref linkend="
12271 "\"sec.hook.outgoing\"/>)"
12272 msgstr ""
12274 #. type: Content of: <book><chapter><sect1><sect2><title>
12275 #: ../en/ch10-hook.xml:1807
12276 msgid ""
12277 "<literal role=\"hook\">pretag</literal>&emdash;before tagging a changeset"
12278 msgstr "<literal role=\"hook\">pretag</literal>&emdash;创建标签之前"
12280 #. type: Content of: <book><chapter><sect1><sect2><para>
12281 #: ../en/ch10-hook.xml:1810
12282 msgid ""
12283 "This controlling hook is run before a tag is created. If the hook succeeds, "
12284 "creation of the tag proceeds. If the hook fails, the tag is not created."
12285 msgstr ""
12287 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12288 #: ../en/ch10-hook.xml:1818
12289 msgid ""
12290 "<literal>local</literal>: A boolean. Whether the tag is local to this "
12291 "repository instance (i.e. stored in <filename role=\"special\">.hg/localtags</"
12292 "filename>) or managed by Mercurial (stored in <filename role=\"special\">."
12293 "hgtags</filename>)."
12294 msgstr ""
12296 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12297 #: ../en/ch10-hook.xml:1825
12298 msgid ""
12299 "<literal>node</literal>: A changeset ID. The ID of the changeset to be "
12300 "tagged."
12301 msgstr ""
12303 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12304 #: ../en/ch10-hook.xml:1829
12305 msgid "<literal>tag</literal>: A string. The name of the tag to be created."
12306 msgstr ""
12308 #. type: Content of: <book><chapter><sect1><sect2><para>
12309 #: ../en/ch10-hook.xml:1834
12310 msgid ""
12311 "If the tag to be created is revision-controlled, the <literal role=\"hook"
12312 "\">precommit</literal> and <literal role=\"hook\">pretxncommit</literal> "
12313 "hooks (sections <xref linkend=\"sec.hook.commit\"/> and <xref linkend=\"sec."
12314 "hook.pretxncommit\"/>) will also be run."
12315 msgstr ""
12317 #. type: Content of: <book><chapter><sect1><sect2><para>
12318 #: ../en/ch10-hook.xml:1841
12319 msgid ""
12320 "See also: <literal role=\"hook\">tag</literal> (section <xref linkend=\"sec."
12321 "hook.tag\"/>)"
12322 msgstr ""
12324 #. type: Content of: <book><chapter><sect1><sect2><title>
12325 #: ../en/ch10-hook.xml:1846
12326 msgid ""
12327 "<literal role=\"hook\">pretxnchangegroup</literal>&emdash;before completing "
12328 "addition of remote changesets"
12329 msgstr ""
12330 "<literal role=\"hook\">pretxnchangegroup</literal>&emdash;完成增加远程修改集之"
12331 "前"
12333 #. type: Content of: <book><chapter><sect1><sect2><para>
12334 #: ../en/ch10-hook.xml:1850
12335 msgid ""
12336 "This controlling hook is run before a transaction&emdash;that manages the "
12337 "addition of a group of new changesets from outside the repository&emdash;"
12338 "completes. If the hook succeeds, the transaction completes, and all of the "
12339 "changesets become permanent within this repository. If the hook fails, the "
12340 "transaction is rolled back, and the data for the changesets is erased."
12341 msgstr ""
12343 #. type: Content of: <book><chapter><sect1><sect2><para>
12344 #: ../en/ch10-hook.xml:1859
12345 msgid ""
12346 "This hook can access the metadata associated with the almost-added "
12347 "changesets, but it should not do anything permanent with this data. It must "
12348 "also not modify the working directory."
12349 msgstr ""
12351 #. type: Content of: <book><chapter><sect1><sect2><para>
12352 #: ../en/ch10-hook.xml:1865
12353 msgid ""
12354 "While this hook is running, if other Mercurial processes access this "
12355 "repository, they will be able to see the almost-added changesets as if they "
12356 "are permanent. This may lead to race conditions if you do not take steps to "
12357 "avoid them."
12358 msgstr ""
12360 #. type: Content of: <book><chapter><sect1><sect2><para>
12361 #: ../en/ch10-hook.xml:1872
12362 msgid ""
12363 "This hook can be used to automatically vet a group of changesets. If the "
12364 "hook fails, all of the changesets are <quote>rejected</quote> when the "
12365 "transaction rolls back."
12366 msgstr ""
12368 #. type: Content of: <book><chapter><sect1><sect2><para>
12369 #: ../en/ch10-hook.xml:1902
12370 msgid ""
12371 "See also: <literal role=\"hook\">changegroup</literal> (section <xref linkend="
12372 "\"sec.hook.changegroup\"/>), <literal role=\"hook\">incoming</literal> "
12373 "(section <xref linkend=\"sec.hook.incoming\"/>), <literal role=\"hook"
12374 "\">prechangegroup</literal> (section <xref linkend=\"sec.hook.prechangegroup"
12375 "\"/>)"
12376 msgstr ""
12378 #. type: Content of: <book><chapter><sect1><sect2><title>
12379 #: ../en/ch10-hook.xml:1912
12380 msgid ""
12381 "<literal role=\"hook\">pretxncommit</literal>&emdash;before completing commit "
12382 "of new changeset"
12383 msgstr "<literal role=\"hook\">pretxncommit</literal>&emdash;完成提交之前"
12385 #. type: Content of: <book><chapter><sect1><sect2><para>
12386 #: ../en/ch10-hook.xml:1915
12387 msgid ""
12388 "This controlling hook is run before a transaction&emdash;that manages a new "
12389 "commit&emdash;completes. If the hook succeeds, the transaction completes and "
12390 "the changeset becomes permanent within this repository. If the hook fails, "
12391 "the transaction is rolled back, and the commit data is erased."
12392 msgstr ""
12394 #. type: Content of: <book><chapter><sect1><sect2><para>
12395 #: ../en/ch10-hook.xml:1923
12396 msgid ""
12397 "This hook can access the metadata associated with the almost-new changeset, "
12398 "but it should not do anything permanent with this data. It must also not "
12399 "modify the working directory."
12400 msgstr ""
12402 #. type: Content of: <book><chapter><sect1><sect2><para>
12403 #: ../en/ch10-hook.xml:1929
12404 msgid ""
12405 "While this hook is running, if other Mercurial processes access this "
12406 "repository, they will be able to see the almost-new changeset as if it is "
12407 "permanent. This may lead to race conditions if you do not take steps to "
12408 "avoid them."
12409 msgstr ""
12411 #. type: Content of: <book><chapter><sect1><sect2><para>
12412 #: ../en/ch10-hook.xml:1953
12413 msgid ""
12414 "See also: <literal role=\"hook\">precommit</literal> (section <xref linkend="
12415 "\"sec.hook.precommit\"/>)"
12416 msgstr ""
12418 #. type: Content of: <book><chapter><sect1><sect2><title>
12419 #: ../en/ch10-hook.xml:1959
12420 msgid ""
12421 "<literal role=\"hook\">preupdate</literal>&emdash;before updating or merging "
12422 "working directory"
12423 msgstr ""
12424 "<literal role=\"hook\">preupdate</literal>&emdash;更新或合并工作目录之前"
12426 #. type: Content of: <book><chapter><sect1><sect2><para>
12427 #: ../en/ch10-hook.xml:1962
12428 msgid ""
12429 "This controlling hook is run before an update or merge of the working "
12430 "directory begins. It is run only if Mercurial's normal pre-update checks "
12431 "determine that the update or merge can proceed. If the hook succeeds, the "
12432 "update or merge may proceed; if it fails, the update or merge does not start."
12433 msgstr ""
12435 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12436 #: ../en/ch10-hook.xml:1972
12437 msgid ""
12438 "<literal>parent1</literal>: A changeset ID. The ID of the parent that the "
12439 "working directory is to be updated to. If the working directory is being "
12440 "merged, it will not change this parent."
12441 msgstr ""
12443 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12444 #: ../en/ch10-hook.xml:1978
12445 msgid ""
12446 "<literal>parent2</literal>: A changeset ID. Only set if the working "
12447 "directory is being merged. The ID of the revision that the working directory "
12448 "is being merged with."
12449 msgstr ""
12451 #. type: Content of: <book><chapter><sect1><sect2><para>
12452 #: ../en/ch10-hook.xml:1985
12453 msgid ""
12454 "See also: <literal role=\"hook\">update</literal> (section <xref linkend="
12455 "\"sec.hook.update\"/>)"
12456 msgstr ""
12458 #. type: Content of: <book><chapter><sect1><sect2><title>
12459 #: ../en/ch10-hook.xml:1991
12460 msgid "<literal role=\"hook\">tag</literal>&emdash;after tagging a changeset"
12461 msgstr "<literal role=\"hook\">tag</literal>&emdash;创建标签之后"
12463 #. type: Content of: <book><chapter><sect1><sect2><para>
12464 #: ../en/ch10-hook.xml:1994
12465 msgid "This hook is run after a tag has been created."
12466 msgstr ""
12468 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12469 #: ../en/ch10-hook.xml:2000
12470 msgid ""
12471 "<literal>local</literal>: A boolean. Whether the new tag is local to this "
12472 "repository instance (i.e. stored in <filename role=\"special\">.hg/"
12473 "localtags</filename>) or managed by Mercurial (stored in <filename role="
12474 "\"special\">.hgtags</filename>)."
12475 msgstr ""
12477 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12478 #: ../en/ch10-hook.xml:2008
12479 msgid ""
12480 "<literal>node</literal>: A changeset ID. The ID of the changeset that was "
12481 "tagged."
12482 msgstr ""
12484 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12485 #: ../en/ch10-hook.xml:2012
12486 msgid "<literal>tag</literal>: A string. The name of the tag that was created."
12487 msgstr ""
12489 #. type: Content of: <book><chapter><sect1><sect2><para>
12490 #: ../en/ch10-hook.xml:2017
12491 msgid ""
12492 "If the created tag is revision-controlled, the <literal role=\"hook\">commit</"
12493 "literal> hook (section <xref linkend=\"sec.hook.commit\"/>) is run before "
12494 "this hook."
12495 msgstr ""
12497 #. type: Content of: <book><chapter><sect1><sect2><para>
12498 #: ../en/ch10-hook.xml:2022
12499 msgid ""
12500 "See also: <literal role=\"hook\">pretag</literal> (section <xref linkend="
12501 "\"sec.hook.pretag\"/>)"
12502 msgstr ""
12504 #. type: Content of: <book><chapter><sect1><sect2><title>
12505 #: ../en/ch10-hook.xml:2028
12506 msgid ""
12507 "<literal role=\"hook\">update</literal>&emdash;after updating or merging "
12508 "working directory"
12509 msgstr "<literal role=\"hook\">update</literal>&emdash;更新或合并工作目录之后"
12511 #. type: Content of: <book><chapter><sect1><sect2><para>
12512 #: ../en/ch10-hook.xml:2031
12513 msgid ""
12514 "This hook is run after an update or merge of the working directory "
12515 "completes. Since a merge can fail (if the external <command>hgmerge</"
12516 "command> command fails to resolve conflicts in a file), this hook "
12517 "communicates whether the update or merge completed cleanly."
12518 msgstr ""
12520 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12521 #: ../en/ch10-hook.xml:2039
12522 msgid ""
12523 "<literal>error</literal>: A boolean. Indicates whether the update or merge "
12524 "completed successfully."
12525 msgstr ""
12527 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12528 #: ../en/ch10-hook.xml:2044
12529 msgid ""
12530 "<literal>parent1</literal>: A changeset ID. The ID of the parent that the "
12531 "working directory was updated to. If the working directory was merged, it "
12532 "will not have changed this parent."
12533 msgstr ""
12535 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
12536 #: ../en/ch10-hook.xml:2050
12537 msgid ""
12538 "<literal>parent2</literal>: A changeset ID. Only set if the working "
12539 "directory was merged. The ID of the revision that the working directory was "
12540 "merged with."
12541 msgstr ""
12543 #. type: Content of: <book><chapter><sect1><sect2><para>
12544 #: ../en/ch10-hook.xml:2056
12545 msgid ""
12546 "See also: <literal role=\"hook\">preupdate</literal> (section <xref linkend="
12547 "\"sec.hook.preupdate\"/>)"
12548 msgstr ""
12550 #. type: Content of: <book><chapter><title>
12551 #: ../en/ch11-template.xml:5
12552 msgid "Customising the output of Mercurial"
12553 msgstr "定制 Mercurial 的输出"
12555 #. type: Content of: <book><chapter><para>
12556 #: ../en/ch11-template.xml:7
12557 msgid ""
12558 "Mercurial provides a powerful mechanism to let you control how it displays "
12559 "information. The mechanism is based on templates. You can use templates to "
12560 "generate specific output for a single command, or to customise the entire "
12561 "appearance of the built-in web interface."
12562 msgstr ""
12564 #. type: Content of: <book><chapter><sect1><title>
12565 #: ../en/ch11-template.xml:14
12566 msgid "Using precanned output styles"
12567 msgstr "使用预定义的输出样式"
12569 #. type: Content of: <book><chapter><sect1><para>
12570 #: ../en/ch11-template.xml:16
12571 msgid ""
12572 "Packaged with Mercurial are some output styles that you can use immediately. "
12573 "A style is simply a precanned template that someone wrote and installed "
12574 "somewhere that Mercurial can find."
12575 msgstr ""
12577 #. type: Content of: <book><chapter><sect1><para>
12578 #: ../en/ch11-template.xml:21
12579 msgid ""
12580 "Before we take a look at Mercurial's bundled styles, let's review its normal "
12581 "output."
12582 msgstr ""
12584 #. type: Content of: <book><chapter><sect1><para>
12585 #: ../en/ch11-template.xml:26
12586 msgid ""
12587 "This is somewhat informative, but it takes up a lot of space&emdash;five "
12588 "lines of output per changeset. The <literal>compact</literal> style reduces "
12589 "this to three lines, presented in a sparse manner."
12590 msgstr ""
12592 #. type: Content of: <book><chapter><sect1><para>
12593 #: ../en/ch11-template.xml:33
12594 msgid ""
12595 "The <literal>changelog</literal> style hints at the expressive power of "
12596 "Mercurial's templating engine. This style attempts to follow the GNU "
12597 "Project's changelog guidelines<citation>web:changelog</citation>."
12598 msgstr ""
12600 #. type: Content of: <book><chapter><sect1><para>
12601 #: ../en/ch11-template.xml:40
12602 msgid ""
12603 "You will not be shocked to learn that Mercurial's default output style is "
12604 "named <literal>default</literal>."
12605 msgstr ""
12607 #. type: Content of: <book><chapter><sect1><sect2><title>
12608 #: ../en/ch11-template.xml:44
12609 msgid "Setting a default style"
12610 msgstr "设置默认样式"
12612 #. type: Content of: <book><chapter><sect1><sect2><para>
12613 #: ../en/ch11-template.xml:46
12614 msgid ""
12615 "You can modify the output style that Mercurial will use for every command by "
12616 "editing your <filename role=\"special\"> /.hgrc</filename>\\ file, naming the "
12617 "style you would prefer to use."
12618 msgstr ""
12620 #. type: Content of: <book><chapter><sect1><sect2><para>
12621 #: ../en/ch11-template.xml:53
12622 msgid ""
12623 "If you write a style of your own, you can use it by either providing the path "
12624 "to your style file, or copying your style file into a location where "
12625 "Mercurial can find it (typically the <literal>templates</literal> "
12626 "subdirectory of your Mercurial install directory)."
12627 msgstr ""
12629 #. type: Content of: <book><chapter><sect1><title>
12630 #: ../en/ch11-template.xml:62
12631 msgid "Commands that support styles and templates"
12632 msgstr "支持样式和模版的命令"
12634 #. type: Content of: <book><chapter><sect1><para>
12635 #: ../en/ch11-template.xml:64
12636 msgid ""
12637 "All of Mercurial's <quote><literal>log</literal>-like</quote> commands let "
12638 "you use styles and templates: <command role=\"hg-cmd\">hg incoming</command>, "
12639 "<command role=\"hg-cmd\">hg log</command>, <command role=\"hg-cmd\">hg "
12640 "outgoing</command>, and <command role=\"hg-cmd\">hg tip</command>."
12641 msgstr ""
12643 #. type: Content of: <book><chapter><sect1><para>
12644 #: ../en/ch11-template.xml:71
12645 msgid ""
12646 "As I write this manual, these are so far the only commands that support "
12647 "styles and templates. Since these are the most important commands that need "
12648 "customisable output, there has been little pressure from the Mercurial user "
12649 "community to add style and template support to other commands."
12650 msgstr ""
12652 #. type: Content of: <book><chapter><sect1><title>
12653 #: ../en/ch11-template.xml:79
12654 msgid "The basics of templating"
12655 msgstr "模版基础"
12657 #. type: Content of: <book><chapter><sect1><para>
12658 #: ../en/ch11-template.xml:81
12659 msgid ""
12660 "At its simplest, a Mercurial template is a piece of text. Some of the text "
12661 "never changes, while other parts are <emphasis>expanded</emphasis>, or "
12662 "replaced with new text, when necessary."
12663 msgstr ""
12665 #. type: Content of: <book><chapter><sect1><para>
12666 #: ../en/ch11-template.xml:86
12667 msgid ""
12668 "Before we continue, let's look again at a simple example of Mercurial's "
12669 "normal output."
12670 msgstr ""
12672 #. type: Content of: <book><chapter><sect1><para>
12673 #: ../en/ch11-template.xml:91
12674 msgid ""
12675 "Now, let's run the same command, but using a template to change its output."
12676 msgstr ""
12678 #. type: Content of: <book><chapter><sect1><para>
12679 #: ../en/ch11-template.xml:96
12680 msgid ""
12681 "The example above illustrates the simplest possible template; it's just a "
12682 "piece of static text, printed once for each changeset. The <option role=\"hg-"
12683 "opt-log\">--template</option> option to the <command role=\"hg-cmd\">hg log</"
12684 "command> command tells Mercurial to use the given text as the template when "
12685 "printing each changeset."
12686 msgstr ""
12688 #. type: Content of: <book><chapter><sect1><para>
12689 #: ../en/ch11-template.xml:104
12690 msgid ""
12691 "Notice that the template string above ends with the text <quote><literal>\\n</"
12692 "literal></quote>. This is an <emphasis>escape sequence</emphasis>, telling "
12693 "Mercurial to print a newline at the end of each template item. If you omit "
12694 "this newline, Mercurial will run each piece of output together. See section "
12695 "<xref linkend=\"sec.template.escape\"/> for more details of escape sequences."
12696 msgstr ""
12698 #. type: Content of: <book><chapter><sect1><para>
12699 #: ../en/ch11-template.xml:112
12700 msgid ""
12701 "A template that prints a fixed string of text all the time isn't very useful; "
12702 "let's try something a bit more complex."
12703 msgstr ""
12705 #. type: Content of: <book><chapter><sect1><para>
12706 #: ../en/ch11-template.xml:118
12707 msgid ""
12708 "As you can see, the string <quote><literal>{desc}</literal></quote> in the "
12709 "template has been replaced in the output with the description of each "
12710 "changeset. Every time Mercurial finds text enclosed in curly braces "
12711 "(<quote><literal>{</literal></quote> and <quote><literal>}</literal></"
12712 "quote>), it will try to replace the braces and text with the expansion of "
12713 "whatever is inside. To print a literal curly brace, you must escape it, as "
12714 "described in section <xref linkend=\"sec.template.escape\"/>."
12715 msgstr ""
12717 #. type: Content of: <book><chapter><sect1><title>
12718 #: ../en/ch11-template.xml:131
12719 msgid "Common template keywords"
12720 msgstr "模版关键字"
12722 #. type: Content of: <book><chapter><sect1><para>
12723 #: ../en/ch11-template.xml:133
12724 msgid ""
12725 "You can start writing simple templates immediately using the keywords below."
12726 msgstr ""
12728 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12729 #: ../en/ch11-template.xml:137
12730 msgid ""
12731 "<literal role=\"template-keyword\">author</literal>: String. The unmodified "
12732 "author of the changeset."
12733 msgstr ""
12735 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12736 #: ../en/ch11-template.xml:141
12737 msgid ""
12738 "<literal role=\"template-keyword\">branches</literal>: String. The name of "
12739 "the branch on which the changeset was committed. Will be empty if the branch "
12740 "name was <literal>default</literal>."
12741 msgstr ""
12743 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12744 #: ../en/ch11-template.xml:147
12745 msgid ""
12746 "<literal role=\"template-keyword\">date</literal>: Date information. The "
12747 "date when the changeset was committed. This is <emphasis>not</emphasis> "
12748 "human-readable; you must pass it through a filter that will render it "
12749 "appropriately. See section <xref linkend=\"sec.template.filter\"/> for more "
12750 "information on filters. The date is expressed as a pair of numbers. The "
12751 "first number is a Unix UTC timestamp (seconds since January 1, 1970); the "
12752 "second is the offset of the committer's timezone from UTC, in seconds."
12753 msgstr ""
12755 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12756 #: ../en/ch11-template.xml:158
12757 msgid ""
12758 "<literal role=\"template-keyword\">desc</literal>: String. The text of the "
12759 "changeset description."
12760 msgstr ""
12762 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12763 #: ../en/ch11-template.xml:161
12764 msgid ""
12765 "<literal role=\"template-keyword\">files</literal>: List of strings. All "
12766 "files modified, added, or removed by this changeset."
12767 msgstr ""
12769 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12770 #: ../en/ch11-template.xml:166
12771 msgid ""
12772 "<literal role=\"template-keyword\">file_adds</literal>: List of strings. "
12773 "Files added by this changeset."
12774 msgstr ""
12776 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12777 #: ../en/ch11-template.xml:170
12778 msgid ""
12779 "<literal role=\"template-keyword\">file_dels</literal>: List of strings. "
12780 "Files removed by this changeset."
12781 msgstr ""
12783 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12784 #: ../en/ch11-template.xml:174
12785 msgid ""
12786 "<literal role=\"template-keyword\">node</literal>: String. The changeset "
12787 "identification hash, as a 40-character hexadecimal string."
12788 msgstr ""
12790 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12791 #: ../en/ch11-template.xml:178
12792 msgid ""
12793 "<literal role=\"template-keyword\">parents</literal>: List of strings. The "
12794 "parents of the changeset."
12795 msgstr ""
12797 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12798 #: ../en/ch11-template.xml:182
12799 msgid ""
12800 "<literal role=\"template-keyword\">rev</literal>: Integer. The repository-"
12801 "local changeset revision number."
12802 msgstr ""
12804 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12805 #: ../en/ch11-template.xml:186
12806 msgid ""
12807 "<literal role=\"template-keyword\">tags</literal>: List of strings. Any tags "
12808 "associated with the changeset."
12809 msgstr ""
12811 #. type: Content of: <book><chapter><sect1><para>
12812 #: ../en/ch11-template.xml:191
12813 msgid ""
12814 "A few simple experiments will show us what to expect when we use these "
12815 "keywords; you can see the results below."
12816 msgstr ""
12818 #. type: Content of: <book><chapter><sect1><para>
12819 #: ../en/ch11-template.xml:196
12820 msgid ""
12821 "As we noted above, the date keyword does not produce human-readable output, "
12822 "so we must treat it specially. This involves using a <emphasis>filter</"
12823 "emphasis>, about which more in section <xref linkend=\"sec.template.filter\"/"
12824 ">."
12825 msgstr ""
12827 #. type: Content of: <book><chapter><sect1><title>
12828 #: ../en/ch11-template.xml:206
12829 msgid "Escape sequences"
12830 msgstr "转义序列"
12832 #. type: Content of: <book><chapter><sect1><para>
12833 #: ../en/ch11-template.xml:208
12834 msgid ""
12835 "Mercurial's templating engine recognises the most commonly used escape "
12836 "sequences in strings. When it sees a backslash (<quote><literal>\\</"
12837 "literal></quote>) character, it looks at the following character and "
12838 "substitutes the two characters with a single replacement, as described below."
12839 msgstr ""
12841 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12842 #: ../en/ch11-template.xml:215
12843 msgid ""
12844 "<literal>\\textbackslash\\textbackslash</literal>: Backslash, <quote><literal>"
12845 "\\</literal></quote>, ASCII 134."
12846 msgstr ""
12848 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12849 #: ../en/ch11-template.xml:219
12850 msgid "<literal>\\textbackslash n</literal>: Newline, ASCII 12."
12851 msgstr ""
12853 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12854 #: ../en/ch11-template.xml:222
12855 msgid "<literal>\\textbackslash r</literal>: Carriage return, ASCII 15."
12856 msgstr ""
12858 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12859 #: ../en/ch11-template.xml:225
12860 msgid "<literal>\\textbackslash t</literal>: Tab, ASCII 11."
12861 msgstr ""
12863 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12864 #: ../en/ch11-template.xml:228
12865 msgid "<literal>\\textbackslash v</literal>: Vertical tab, ASCII 13."
12866 msgstr ""
12868 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12869 #: ../en/ch11-template.xml:231
12870 msgid ""
12871 "<literal>\\textbackslash {</literal>: Open curly brace, <quote><literal>{</"
12872 "literal></quote>, ASCII 173."
12873 msgstr ""
12875 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12876 #: ../en/ch11-template.xml:235
12877 msgid ""
12878 "<literal>\\textbackslash }</literal>: Close curly brace, <quote><literal>}</"
12879 "literal></quote>, ASCII 175."
12880 msgstr ""
12882 #. type: Content of: <book><chapter><sect1><para>
12883 #: ../en/ch11-template.xml:240
12884 msgid ""
12885 "As indicated above, if you want the expansion of a template to contain a "
12886 "literal <quote><literal>\\</literal></quote>, <quote><literal>{</literal></"
12887 "quote>, or <quote><literal>{</literal></quote> character, you must escape it."
12888 msgstr ""
12890 #. type: Content of: <book><chapter><sect1><title>
12891 #: ../en/ch11-template.xml:248
12892 msgid "Filtering keywords to change their results"
12893 msgstr "通过过滤关键字来修改输出结果"
12895 #. type: Content of: <book><chapter><sect1><para>
12896 #: ../en/ch11-template.xml:250
12897 msgid ""
12898 "Some of the results of template expansion are not immediately easy to use. "
12899 "Mercurial lets you specify an optional chain of <emphasis>filters</emphasis> "
12900 "to modify the result of expanding a keyword. You have already seen a common "
12901 "filter, <literal role=\"template-kw-filt-date\">isodate</literal>, in action "
12902 "above, to make a date readable."
12903 msgstr ""
12905 #. type: Content of: <book><chapter><sect1><para>
12906 #: ../en/ch11-template.xml:257
12907 msgid ""
12908 "Below is a list of the most commonly used filters that Mercurial supports. "
12909 "While some filters can be applied to any text, others can only be used in "
12910 "specific circumstances. The name of each filter is followed first by an "
12911 "indication of where it can be used, then a description of its effect."
12912 msgstr ""
12914 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12915 #: ../en/ch11-template.xml:264
12916 msgid ""
12917 "<literal role=\"template-filter\">addbreaks</literal>: Any text. Add an XHTML "
12918 "<quote><literal><br/></literal></quote> tag before the end of every "
12919 "line except the last. For example, <quote><literal>foo\\nbar</literal></"
12920 "quote> becomes <quote><literal>foo<br/>\\nbar</literal></quote>."
12921 msgstr ""
12923 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12924 #: ../en/ch11-template.xml:271
12925 msgid ""
12926 "<literal role=\"template-kw-filt-date\">age</literal>: <literal role="
12927 "\"template-keyword\">date</literal> keyword. Render the age of the date, "
12928 "relative to the current time. Yields a string like <quote><literal>10 "
12929 "minutes</literal></quote>."
12930 msgstr ""
12932 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12933 #: ../en/ch11-template.xml:278
12934 msgid ""
12935 "<literal role=\"template-filter\">basename</literal>: Any text, but most "
12936 "useful for the <literal role=\"template-keyword\">files</literal> keyword and "
12937 "its relatives. Treat the text as a path, and return the basename. For "
12938 "example, <quote><literal>foo/bar/baz</literal></quote> becomes "
12939 "<quote><literal>baz</literal></quote>."
12940 msgstr ""
12942 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12943 #: ../en/ch11-template.xml:287
12944 msgid ""
12945 "<literal role=\"template-kw-filt-date\">date</literal>: <literal role="
12946 "\"template-keyword\">date</literal> keyword. Render a date in a similar "
12947 "format to the Unix <literal role=\"template-keyword\">date</literal> command, "
12948 "but with timezone included. Yields a string like <quote><literal>Mon Sep 04 "
12949 "15:13:13 2006 -0700</literal></quote>."
12950 msgstr ""
12952 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12953 #: ../en/ch11-template.xml:295
12954 msgid ""
12955 "<literal role=\"template-kw-filt-author\">domain</literal>: Any text, but "
12956 "most useful for the <literal role=\"template-keyword\">author</literal> "
12957 "keyword. Finds the first string that looks like an email address, and "
12958 "extract just the domain component. For example, <quote><literal>Bryan "
12959 "O'Sullivan <bos@serpentine.com></literal></quote> becomes "
12960 "<quote><literal>serpentine.com</literal></quote>."
12961 msgstr ""
12963 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12964 #: ../en/ch11-template.xml:305
12965 msgid ""
12966 "<literal role=\"template-kw-filt-author\">email</literal>: Any text, but most "
12967 "useful for the <literal role=\"template-keyword\">author</literal> keyword. "
12968 "Extract the first string that looks like an email address. For example, "
12969 "<quote><literal>Bryan O'Sullivan <bos@serpentine.com></literal></quote> "
12970 "becomes <quote><literal>bos@serpentine.com</literal></quote>."
12971 msgstr ""
12973 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12974 #: ../en/ch11-template.xml:314
12975 msgid ""
12976 "<literal role=\"template-filter\">escape</literal>: Any text. Replace the "
12977 "special XML/XHTML characters <quote><literal>&</literal></quote>, "
12978 "<quote><literal><</literal></quote> and <quote><literal>></literal></"
12979 "quote> with XML entities."
12980 msgstr ""
12982 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12983 #: ../en/ch11-template.xml:322
12984 msgid ""
12985 "<literal role=\"template-filter\">fill68</literal>: Any text. Wrap the text "
12986 "to fit in 68 columns. This is useful before you pass text through the "
12987 "<literal role=\"template-filter\">tabindent</literal> filter, and still want "
12988 "it to fit in an 80-column fixed-font window."
12989 msgstr ""
12991 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12992 #: ../en/ch11-template.xml:330
12993 msgid ""
12994 "<literal role=\"template-filter\">fill76</literal>: Any text. Wrap the text "
12995 "to fit in 76 columns."
12996 msgstr ""
12998 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
12999 #: ../en/ch11-template.xml:334
13000 msgid ""
13001 "<literal role=\"template-filter\">firstline</literal>: Any text. Yield the "
13002 "first line of text, without any trailing newlines."
13003 msgstr ""
13005 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13006 #: ../en/ch11-template.xml:339
13007 msgid ""
13008 "<literal role=\"template-kw-filt-date\">hgdate</literal>: <literal role="
13009 "\"template-keyword\">date</literal> keyword. Render the date as a pair of "
13010 "readable numbers. Yields a string like <quote><literal>1157407993 25200</"
13011 "literal></quote>."
13012 msgstr ""
13014 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13015 #: ../en/ch11-template.xml:346
13016 msgid ""
13017 "<literal role=\"template-kw-filt-date\">isodate</literal>: <literal role="
13018 "\"template-keyword\">date</literal> keyword. Render the date as a text "
13019 "string in ISO 8601 format. Yields a string like <quote><literal>2006-09-04 "
13020 "15:13:13 -0700</literal></quote>."
13021 msgstr ""
13023 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13024 #: ../en/ch11-template.xml:353
13025 msgid ""
13026 "<literal role=\"template-filter\">obfuscate</literal>: Any text, but most "
13027 "useful for the <literal role=\"template-keyword\">author</literal> keyword. "
13028 "Yield the input text rendered as a sequence of XML entities. This helps to "
13029 "defeat some particularly stupid screen-scraping email harvesting spambots."
13030 msgstr ""
13032 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13033 #: ../en/ch11-template.xml:361
13034 msgid ""
13035 "<literal role=\"template-kw-filt-author\">person</literal>: Any text, but "
13036 "most useful for the <literal role=\"template-keyword\">author</literal> "
13037 "keyword. Yield the text before an email address. For example, "
13038 "<quote><literal>Bryan O'Sullivan <bos@serpentine.com></literal></quote> "
13039 "becomes <quote><literal>Bryan O'Sullivan</literal></quote>."
13040 msgstr ""
13042 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13043 #: ../en/ch11-template.xml:370
13044 msgid ""
13045 "<literal role=\"template-kw-filt-date\">rfc822date</literal>: <literal role="
13046 "\"template-keyword\">date</literal> keyword. Render a date using the same "
13047 "format used in email headers. Yields a string like <quote><literal>Mon, 04 "
13048 "Sep 2006 15:13:13 -0700</literal></quote>."
13049 msgstr ""
13051 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13052 #: ../en/ch11-template.xml:377
13053 msgid ""
13054 "<literal role=\"template-kw-filt-node\">short</literal>: Changeset hash. "
13055 "Yield the short form of a changeset hash, i.e. a 12-character hexadecimal "
13056 "string."
13057 msgstr ""
13059 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13060 #: ../en/ch11-template.xml:382
13061 msgid ""
13062 "<literal role=\"template-kw-filt-date\">shortdate</literal>: <literal role="
13063 "\"template-keyword\">date</literal> keyword. Render the year, month, and day "
13064 "of the date. Yields a string like <quote><literal>2006-09-04</literal></"
13065 "quote>."
13066 msgstr ""
13068 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13069 #: ../en/ch11-template.xml:388
13070 msgid ""
13071 "<literal role=\"template-filter\">strip</literal>: Any text. Strip all "
13072 "leading and trailing whitespace from the string."
13073 msgstr ""
13075 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13076 #: ../en/ch11-template.xml:392
13077 msgid ""
13078 "<literal role=\"template-filter\">tabindent</literal>: Any text. Yield the "
13079 "text, with every line except the first starting with a tab character."
13080 msgstr ""
13082 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13083 #: ../en/ch11-template.xml:397
13084 msgid ""
13085 "<literal role=\"template-filter\">urlescape</literal>: Any text. Escape all "
13086 "characters that are considered <quote>special</quote> by URL parsers. For "
13087 "example, <literal>foo bar</literal> becomes <literal>foo%20bar</literal>."
13088 msgstr ""
13090 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
13091 #: ../en/ch11-template.xml:404
13092 msgid ""
13093 "<literal role=\"template-kw-filt-author\">user</literal>: Any text, but most "
13094 "useful for the <literal role=\"template-keyword\">author</literal> keyword. "
13095 "Return the <quote>user</quote> portion of an email address. For example, "
13096 "<quote><literal>Bryan O'Sullivan <bos@serpentine.com></literal></quote> "
13097 "becomes <quote><literal>bos</literal></quote>."
13098 msgstr ""
13100 #. type: Content of: <book><chapter><sect1><note><para>
13101 #: ../en/ch11-template.xml:417
13102 msgid ""
13103 "If you try to apply a filter to a piece of data that it cannot process, "
13104 "Mercurial will fail and print a Python exception. For example, trying to run "
13105 "the output of the <literal role=\"template-keyword\">desc</literal> keyword "
13106 "into the <literal role=\"template-kw-filt-date\">isodate</literal> filter is "
13107 "not a good idea."
13108 msgstr ""
13110 #. type: Content of: <book><chapter><sect1><sect2><title>
13111 #: ../en/ch11-template.xml:426
13112 msgid "Combining filters"
13113 msgstr "组合过滤器"
13115 #. type: Content of: <book><chapter><sect1><sect2><para>
13116 #: ../en/ch11-template.xml:428
13117 msgid ""
13118 "It is easy to combine filters to yield output in the form you would like. "
13119 "The following chain of filters tidies up a description, then makes sure that "
13120 "it fits cleanly into 68 columns, then indents it by a further 8 characters "
13121 "(at least on Unix-like systems, where a tab is conventionally 8 characters "
13122 "wide)."
13123 msgstr ""
13125 #. type: Content of: <book><chapter><sect1><sect2><para>
13126 #: ../en/ch11-template.xml:437
13127 msgid ""
13128 "Note the use of <quote><literal>\\t</literal></quote> (a tab character) in "
13129 "the template to force the first line to be indented; this is necessary since "
13130 "<literal role=\"template-keyword\">tabindent</literal> indents all lines "
13131 "<emphasis>except</emphasis> the first."
13132 msgstr ""
13134 #. type: Content of: <book><chapter><sect1><sect2><para>
13135 #: ../en/ch11-template.xml:443
13136 msgid ""
13137 "Keep in mind that the order of filters in a chain is significant. The first "
13138 "filter is applied to the result of the keyword; the second to the result of "
13139 "the first filter; and so on. For example, using <literal>fill68|tabindent</"
13140 "literal> gives very different results from <literal>tabindent|fill68</"
13141 "literal>."
13142 msgstr ""
13144 #. type: Content of: <book><chapter><sect1><title>
13145 #: ../en/ch11-template.xml:454
13146 msgid "From templates to styles"
13147 msgstr "从模版到样式"
13149 #. type: Content of: <book><chapter><sect1><para>
13150 #: ../en/ch11-template.xml:456
13151 msgid ""
13152 "A command line template provides a quick and simple way to format some "
13153 "output. Templates can become verbose, though, and it's useful to be able to "
13154 "give a template a name. A style file is a template with a name, stored in a "
13155 "file."
13156 msgstr ""
13158 #. type: Content of: <book><chapter><sect1><para>
13159 #: ../en/ch11-template.xml:461
13160 msgid ""
13161 "More than that, using a style file unlocks the power of Mercurial's "
13162 "templating engine in ways that are not possible using the command line "
13163 "<option role=\"hg-opt-log\">--template</option> option."
13164 msgstr ""
13166 #. type: Content of: <book><chapter><sect1><sect2><title>
13167 #: ../en/ch11-template.xml:467
13168 msgid "The simplest of style files"
13169 msgstr "最简单的样式文件"
13171 #. type: Content of: <book><chapter><sect1><sect2><para>
13172 #: ../en/ch11-template.xml:469
13173 msgid "Our simple style file contains just one line:"
13174 msgstr ""
13176 #. type: Content of: <book><chapter><sect1><sect2><para>
13177 #: ../en/ch11-template.xml:473
13178 msgid ""
13179 "This tells Mercurial, <quote>if you're printing a changeset, use the text on "
13180 "the right as the template</quote>."
13181 msgstr ""
13183 #. type: Content of: <book><chapter><sect1><sect2><title>
13184 #: ../en/ch11-template.xml:479
13185 msgid "Style file syntax"
13186 msgstr "样式文件语法"
13188 #. type: Content of: <book><chapter><sect1><sect2><para>
13189 #: ../en/ch11-template.xml:481
13190 msgid "The syntax rules for a style file are simple."
13191 msgstr ""
13193 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13194 #: ../en/ch11-template.xml:484
13195 msgid "The file is processed one line at a time."
13196 msgstr ""
13198 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13199 #: ../en/ch11-template.xml:487
13200 msgid "Leading and trailing white space are ignored."
13201 msgstr ""
13203 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13204 #: ../en/ch11-template.xml:490
13205 msgid "Empty lines are skipped."
13206 msgstr ""
13208 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13209 #: ../en/ch11-template.xml:492
13210 msgid ""
13211 "If a line starts with either of the characters <quote><literal>#</literal></"
13212 "quote> or <quote><literal>;</literal></quote>, the entire line is treated as "
13213 "a comment, and skipped as if empty."
13214 msgstr ""
13216 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13217 #: ../en/ch11-template.xml:497
13218 msgid ""
13219 "A line starts with a keyword. This must start with an alphabetic character "
13220 "or underscore, and can subsequently contain any alphanumeric character or "
13221 "underscore. (In regexp notation, a keyword must match <literal>[A-Za-z_][A-"
13222 "Za-z0-9_]*</literal>.)"
13223 msgstr ""
13225 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13226 #: ../en/ch11-template.xml:503
13227 msgid ""
13228 "The next element must be an <quote><literal>=</literal></quote> character, "
13229 "which can be preceded or followed by an arbitrary amount of white space."
13230 msgstr ""
13232 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13233 #: ../en/ch11-template.xml:508
13234 msgid ""
13235 "If the rest of the line starts and ends with matching quote characters "
13236 "(either single or double quote), it is treated as a template body."
13237 msgstr ""
13239 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13240 #: ../en/ch11-template.xml:512
13241 msgid ""
13242 "If the rest of the line <emphasis>does not</emphasis> start with a quote "
13243 "character, it is treated as the name of a file; the contents of this file "
13244 "will be read and used as a template body."
13245 msgstr ""
13247 #. type: Content of: <book><chapter><sect1><title>
13248 #: ../en/ch11-template.xml:521
13249 msgid "Style files by example"
13250 msgstr "样式文件例子"
13252 #. type: Content of: <book><chapter><sect1><para>
13253 #: ../en/ch11-template.xml:523
13254 msgid ""
13255 "To illustrate how to write a style file, we will construct a few by example. "
13256 "Rather than provide a complete style file and walk through it, we'll mirror "
13257 "the usual process of developing a style file by starting with something very "
13258 "simple, and walking through a series of successively more complete examples."
13259 msgstr ""
13261 #. type: Content of: <book><chapter><sect1><sect2><title>
13262 #: ../en/ch11-template.xml:530
13263 msgid "Identifying mistakes in style files"
13264 msgstr "在样式文件中定位错误"
13266 #. type: Content of: <book><chapter><sect1><sect2><para>
13267 #: ../en/ch11-template.xml:532
13268 msgid ""
13269 "If Mercurial encounters a problem in a style file you are working on, it "
13270 "prints a terse error message that, once you figure out what it means, is "
13271 "actually quite useful."
13272 msgstr ""
13274 #. type: Content of: <book><chapter><sect1><sect2><para>
13275 #: ../en/ch11-template.xml:538
13276 msgid ""
13277 "Notice that <filename>broken.style</filename> attempts to define a "
13278 "<literal>changeset</literal> keyword, but forgets to give any content for it. "
13279 "When instructed to use this style file, Mercurial promptly complains."
13280 msgstr ""
13282 #. type: Content of: <book><chapter><sect1><sect2><para>
13283 #: ../en/ch11-template.xml:545
13284 msgid "This error message looks intimidating, but it is not too hard to follow."
13285 msgstr ""
13287 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13288 #: ../en/ch11-template.xml:549
13289 msgid ""
13290 "The first component is simply Mercurial's way of saying <quote>I am giving "
13291 "up</quote>."
13292 msgstr ""
13294 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13295 #: ../en/ch11-template.xml:554
13296 msgid "Next comes the name of the style file that contains the error."
13297 msgstr ""
13299 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13300 #: ../en/ch11-template.xml:560
13301 msgid ""
13302 "Following the file name is the line number where the error was encountered."
13303 msgstr ""
13305 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13306 #: ../en/ch11-template.xml:565
13307 msgid "Finally, a description of what went wrong."
13308 msgstr ""
13310 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13311 #: ../en/ch11-template.xml:570
13312 msgid ""
13313 "The description of the problem is not always clear (as in this case), but "
13314 "even when it is cryptic, it is almost always trivial to visually inspect the "
13315 "offending line in the style file and see what is wrong."
13316 msgstr ""
13318 #. type: Content of: <book><chapter><sect1><sect2><title>
13319 #: ../en/ch11-template.xml:578
13320 msgid "Uniquely identifying a repository"
13321 msgstr "版本库的唯一标识"
13323 #. type: Content of: <book><chapter><sect1><sect2><para>
13324 #: ../en/ch11-template.xml:580
13325 msgid ""
13326 "If you would like to be able to identify a Mercurial repository <quote>fairly "
13327 "uniquely</quote> using a short string as an identifier, you can use the first "
13328 "revision in the repository."
13329 msgstr ""
13331 #. type: Content of: <book><chapter><sect1><sect2><para>
13332 #: ../en/ch11-template.xml:587
13333 msgid ""
13334 "This is not guaranteed to be unique, but it is nevertheless useful in many "
13335 "cases."
13336 msgstr ""
13338 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13339 #: ../en/ch11-template.xml:590
13340 msgid ""
13341 "It will not work in a completely empty repository, because such a repository "
13342 "does not have a revision zero."
13343 msgstr ""
13345 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13346 #: ../en/ch11-template.xml:594
13347 msgid ""
13348 "Neither will it work in the (extremely rare) case where a repository is a "
13349 "merge of two or more formerly independent repositories, and you still have "
13350 "those repositories around."
13351 msgstr ""
13353 #. type: Content of: <book><chapter><sect1><sect2><para>
13354 #: ../en/ch11-template.xml:599
13355 msgid "Here are some uses to which you could put this identifier:"
13356 msgstr ""
13358 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13359 #: ../en/ch11-template.xml:602
13360 msgid ""
13361 "As a key into a table for a database that manages repositories on a server."
13362 msgstr ""
13364 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13365 #: ../en/ch11-template.xml:605
13366 msgid ""
13367 "As half of a {<emphasis>repository ID</emphasis>, <emphasis>revision ID</"
13368 "emphasis>} tuple. Save this information away when you run an automated build "
13369 "or other activity, so that you can <quote>replay</quote> the build later if "
13370 "necessary."
13371 msgstr ""
13373 #. type: Content of: <book><chapter><sect1><sect2><title>
13374 #: ../en/ch11-template.xml:614
13375 msgid "Mimicking Subversion's output"
13376 msgstr "模仿 Subversion 的输出"
13378 #
13379 #. type: Content of: <book><chapter><sect1><sect2><para>
13380 #: ../en/ch11-template.xml:616
13381 msgid ""
13382 "Let's try to emulate the default output format used by another revision "
13383 "control tool, Subversion."
13384 msgstr ""
13386 #
13387 #. type: Content of: <book><chapter><sect1><sect2><para>
13388 #: ../en/ch11-template.xml:621
13389 msgid ""
13390 "Since Subversion's output style is fairly simple, it is easy to copy-and-"
13391 "paste a hunk of its output into a file, and replace the text produced above "
13392 "by Subversion with the template values we'd like to see expanded."
13393 msgstr ""
13395 #. type: Content of: <book><chapter><sect1><sect2><para>
13396 #: ../en/ch11-template.xml:628
13397 msgid ""
13398 "There are a few small ways in which this template deviates from the output "
13399 "produced by Subversion."
13400 msgstr ""
13402 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13403 #: ../en/ch11-template.xml:631
13404 msgid ""
13405 "Subversion prints a <quote>readable</quote> date (the <quote><literal>Wed, 27 "
13406 "Sep 2006</literal></quote> in the example output above) in parentheses. "
13407 "Mercurial's templating engine does not provide a way to display a date in "
13408 "this format without also printing the time and time zone."
13409 msgstr ""
13411 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13412 #: ../en/ch11-template.xml:638
13413 msgid ""
13414 "We emulate Subversion's printing of <quote>separator</quote> lines full of "
13415 "<quote><literal>-</literal></quote> characters by ending the template with "
13416 "such a line. We use the templating engine's <literal role=\"template-keyword"
13417 "\">header</literal> keyword to print a separator line as the first line of "
13418 "output (see below), thus achieving similar output to Subversion."
13419 msgstr ""
13421 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13422 #: ../en/ch11-template.xml:647
13423 msgid ""
13424 "Subversion's output includes a count in the header of the number of lines in "
13425 "the commit message. We cannot replicate this in Mercurial; the templating "
13426 "engine does not currently provide a filter that counts the number of lines "
13427 "the template generates."
13428 msgstr ""
13430 #
13431 #. type: Content of: <book><chapter><sect1><sect2><para>
13432 #: ../en/ch11-template.xml:653
13433 msgid ""
13434 "It took me no more than a minute or two of work to replace literal text from "
13435 "an example of Subversion's output with some keywords and filters to give the "
13436 "template above. The style file simply refers to the template."
13437 msgstr ""
13439 #. type: Content of: <book><chapter><sect1><sect2><para>
13440 #: ../en/ch11-template.xml:660
13441 msgid ""
13442 "We could have included the text of the template file directly in the style "
13443 "file by enclosing it in quotes and replacing the newlines with "
13444 "<quote><literal>\\n</literal></quote> sequences, but it would have made the "
13445 "style file too difficult to read. Readability is a good guide when you're "
13446 "trying to decide whether some text belongs in a style file, or in a template "
13447 "file that the style file points to. If the style file will look too big or "
13448 "cluttered if you insert a literal piece of text, drop it into a template "
13449 "instead."
13450 msgstr ""
13452 #. type: Content of: <book><chapter><title>
13453 #: ../en/ch12-mq.xml:5
13454 msgid "Managing change with Mercurial Queues"
13455 msgstr "使用 MQ 管理修改"
13457 #. type: Content of: <book><chapter><sect1><title>
13458 #: ../en/ch12-mq.xml:8
13459 msgid "The patch management problem"
13460 msgstr "补丁的管理问题"
13462 #. type: Content of: <book><chapter><sect1><para>
13463 #: ../en/ch12-mq.xml:10
13464 msgid ""
13465 "Here is a common scenario: you need to install a software package from "
13466 "source, but you find a bug that you must fix in the source before you can "
13467 "start using the package. You make your changes, forget about the package for "
13468 "a while, and a few months later you need to upgrade to a newer version of the "
13469 "package. If the newer version of the package still has the bug, you must "
13470 "extract your fix from the older source tree and apply it against the newer "
13471 "version. This is a tedious task, and it's easy to make mistakes."
13472 msgstr ""
13474 #. type: Content of: <book><chapter><sect1><para>
13475 #: ../en/ch12-mq.xml:20
13476 msgid ""
13477 "This is a simple case of the <quote>patch management</quote> problem. You "
13478 "have an <quote>upstream</quote> source tree that you can't change; you need "
13479 "to make some local changes on top of the upstream tree; and you'd like to be "
13480 "able to keep those changes separate, so that you can apply them to newer "
13481 "versions of the upstream source."
13482 msgstr ""
13484 #. type: Content of: <book><chapter><sect1><para>
13485 #: ../en/ch12-mq.xml:27
13486 msgid ""
13487 "The patch management problem arises in many situations. Probably the most "
13488 "visible is that a user of an open source software project will contribute a "
13489 "bug fix or new feature to the project's maintainers in the form of a patch."
13490 msgstr ""
13492 #. type: Content of: <book><chapter><sect1><para>
13493 #: ../en/ch12-mq.xml:32
13494 msgid ""
13495 "Distributors of operating systems that include open source software often "
13496 "need to make changes to the packages they distribute so that they will build "
13497 "properly in their environments."
13498 msgstr ""
13500 #. type: Content of: <book><chapter><sect1><para>
13501 #: ../en/ch12-mq.xml:37
13502 msgid ""
13503 "When you have few changes to maintain, it is easy to manage a single patch "
13504 "using the standard <command>diff</command> and <command>patch</command> "
13505 "programs (see section <xref linkend=\"sec.mq.patch\"/> for a discussion of "
13506 "these tools). Once the number of changes grows, it starts to make sense to "
13507 "maintain patches as discrete <quote>chunks of work,</quote> so that for "
13508 "example a single patch will contain only one bug fix (the patch might modify "
13509 "several files, but it's doing <quote>only one thing</quote>), and you may "
13510 "have a number of such patches for different bugs you need fixed and local "
13511 "changes you require. In this situation, if you submit a bug fix patch to the "
13512 "upstream maintainers of a package and they include your fix in a subsequent "
13513 "release, you can simply drop that single patch when you're updating to the "
13514 "newer release."
13515 msgstr ""
13517 #. type: Content of: <book><chapter><sect1><para>
13518 #: ../en/ch12-mq.xml:52
13519 msgid ""
13520 "Maintaining a single patch against an upstream tree is a little tedious and "
13521 "error-prone, but not difficult. However, the complexity of the problem grows "
13522 "rapidly as the number of patches you have to maintain increases. With more "
13523 "than a tiny number of patches in hand, understanding which ones you have "
13524 "applied and maintaining them moves from messy to overwhelming."
13525 msgstr ""
13527 #. type: Content of: <book><chapter><sect1><para>
13528 #: ../en/ch12-mq.xml:59
13529 msgid ""
13530 "Fortunately, Mercurial includes a powerful extension, Mercurial Queues (or "
13531 "simply <quote>MQ</quote>), that massively simplifies the patch management "
13532 "problem."
13533 msgstr ""
13535 #. type: Content of: <book><chapter><sect1><title>
13536 #: ../en/ch12-mq.xml:65
13537 msgid "The prehistory of Mercurial Queues"
13538 msgstr "MQ 的历史"
13540 #. type: Content of: <book><chapter><sect1><para>
13541 #: ../en/ch12-mq.xml:67
13542 msgid ""
13543 "During the late 1990s, several Linux kernel developers started to maintain "
13544 "<quote>patch series</quote> that modified the behaviour of the Linux kernel. "
13545 "Some of these series were focused on stability, some on feature coverage, and "
13546 "others were more speculative."
13547 msgstr ""
13549 #. type: Content of: <book><chapter><sect1><para>
13550 #: ../en/ch12-mq.xml:73
13551 msgid ""
13552 "The sizes of these patch series grew rapidly. In 2002, Andrew Morton "
13553 "published some shell scripts he had been using to automate the task of "
13554 "managing his patch queues. Andrew was successfully using these scripts to "
13555 "manage hundreds (sometimes thousands) of patches on top of the Linux kernel."
13556 msgstr ""
13558 #. type: Content of: <book><chapter><sect1><sect2><title>
13559 #: ../en/ch12-mq.xml:80
13560 msgid "A patchwork quilt"
13561 msgstr ""
13563 #. type: Content of: <book><chapter><sect1><sect2><para>
13564 #: ../en/ch12-mq.xml:82
13565 msgid ""
13566 "In early 2003, Andreas Gruenbacher and Martin Quinson borrowed the approach "
13567 "of Andrew's scripts and published a tool called <quote>patchwork quilt</"
13568 "quote> <citation>web:quilt</citation>, or simply <quote>quilt</quote> (see "
13569 "<citation>gruenbacher:2005</citation> for a paper describing it). Because "
13570 "quilt substantially automated patch management, it rapidly gained a large "
13571 "following among open source software developers."
13572 msgstr ""
13574 #. type: Content of: <book><chapter><sect1><sect2><para>
13575 #: ../en/ch12-mq.xml:91
13576 msgid ""
13577 "Quilt manages a <emphasis>stack of patches</emphasis> on top of a directory "
13578 "tree. To begin, you tell quilt to manage a directory tree, and tell it which "
13579 "files you want to manage; it stores away the names and contents of those "
13580 "files. To fix a bug, you create a new patch (using a single command), edit "
13581 "the files you need to fix, then <quote>refresh</quote> the patch."
13582 msgstr ""
13584 #. type: Content of: <book><chapter><sect1><sect2><para>
13585 #: ../en/ch12-mq.xml:99
13586 msgid ""
13587 "The refresh step causes quilt to scan the directory tree; it updates the "
13588 "patch with all of the changes you have made. You can create another patch on "
13589 "top of the first, which will track the changes required to modify the tree "
13590 "from <quote>tree with one patch applied</quote> to <quote>tree with two "
13591 "patches applied</quote>."
13592 msgstr ""
13594 #. type: Content of: <book><chapter><sect1><sect2><para>
13595 #: ../en/ch12-mq.xml:106
13596 msgid ""
13597 "You can <emphasis>change</emphasis> which patches are applied to the tree. "
13598 "If you <quote>pop</quote> a patch, the changes made by that patch will vanish "
13599 "from the directory tree. Quilt remembers which patches you have popped, "
13600 "though, so you can <quote>push</quote> a popped patch again, and the "
13601 "directory tree will be restored to contain the modifications in the patch. "
13602 "Most importantly, you can run the <quote>refresh</quote> command at any time, "
13603 "and the topmost applied patch will be updated. This means that you can, at "
13604 "any time, change both which patches are applied and what modifications those "
13605 "patches make."
13606 msgstr ""
13608 #. type: Content of: <book><chapter><sect1><sect2><para>
13609 #: ../en/ch12-mq.xml:118
13610 msgid ""
13611 "Quilt knows nothing about revision control tools, so it works equally well on "
13612 "top of an unpacked tarball or a Subversion working copy."
13613 msgstr ""
13615 #. type: Content of: <book><chapter><sect1><sect2><title>
13616 #: ../en/ch12-mq.xml:124
13617 msgid "From patchwork quilt to Mercurial Queues"
13618 msgstr "从 patchwork quilt 到 MQ"
13620 #. type: Content of: <book><chapter><sect1><sect2><para>
13621 #: ../en/ch12-mq.xml:126
13622 msgid ""
13623 "In mid-2005, Chris Mason took the features of quilt and wrote an extension "
13624 "that he called Mercurial Queues, which added quilt-like behaviour to "
13625 "Mercurial."
13626 msgstr ""
13628 #. type: Content of: <book><chapter><sect1><sect2><para>
13629 #: ../en/ch12-mq.xml:130
13630 msgid ""
13631 "The key difference between quilt and MQ is that quilt knows nothing about "
13632 "revision control systems, while MQ is <emphasis>integrated</emphasis> into "
13633 "Mercurial. Each patch that you push is represented as a Mercurial "
13634 "changeset. Pop a patch, and the changeset goes away."
13635 msgstr ""
13637 #. type: Content of: <book><chapter><sect1><sect2><para>
13638 #: ../en/ch12-mq.xml:136
13639 msgid ""
13640 "Because quilt does not care about revision control tools, it is still a "
13641 "tremendously useful piece of software to know about for situations where you "
13642 "cannot use Mercurial and MQ."
13643 msgstr ""
13645 #. type: Content of: <book><chapter><sect1><title>
13646 #: ../en/ch12-mq.xml:144
13647 msgid "The huge advantage of MQ"
13648 msgstr "MQ 的巨大优势"
13650 #. type: Content of: <book><chapter><sect1><para>
13651 #: ../en/ch12-mq.xml:146
13652 msgid ""
13653 "I cannot overstate the value that MQ offers through the unification of "
13654 "patches and revision control."
13655 msgstr ""
13657 #. type: Content of: <book><chapter><sect1><para>
13658 #: ../en/ch12-mq.xml:149
13659 msgid ""
13660 "A major reason that patches have persisted in the free software and open "
13661 "source world&emdash;in spite of the availability of increasingly capable "
13662 "revision control tools over the years&emdash;is the <emphasis>agility</"
13663 "emphasis> they offer."
13664 msgstr ""
13666 #. type: Content of: <book><chapter><sect1><para>
13667 #: ../en/ch12-mq.xml:155
13668 msgid ""
13669 "Traditional revision control tools make a permanent, irreversible record of "
13670 "everything that you do. While this has great value, it's also somewhat "
13671 "stifling. If you want to perform a wild-eyed experiment, you have to be "
13672 "careful in how you go about it, or you risk leaving unneeded&emdash;or worse, "
13673 "misleading or destabilising&emdash;traces of your missteps and errors in the "
13674 "permanent revision record."
13675 msgstr ""
13677 #. type: Content of: <book><chapter><sect1><para>
13678 #: ../en/ch12-mq.xml:163
13679 msgid ""
13680 "By contrast, MQ's marriage of distributed revision control with patches makes "
13681 "it much easier to isolate your work. Your patches live on top of normal "
13682 "revision history, and you can make them disappear or reappear at will. If "
13683 "you don't like a patch, you can drop it. If a patch isn't quite as you want "
13684 "it to be, simply fix it&emdash;as many times as you need to, until you have "
13685 "refined it into the form you desire."
13686 msgstr ""
13688 #. type: Content of: <book><chapter><sect1><para>
13689 #: ../en/ch12-mq.xml:171
13690 msgid ""
13691 "As an example, the integration of patches with revision control makes "
13692 "understanding patches and debugging their effects&emdash;and their interplay "
13693 "with the code they're based on&emdash;<emphasis>enormously</emphasis> easier. "
13694 "Since every applied patch has an associated changeset, you can give <command "
13695 "role=\"hg-cmd\">hg log</command> a file name to see which changesets and "
13696 "patches affected the file. You can use the <command role=\"hg-cmd\">hg "
13697 "bisect</command> command to binary-search through all changesets and applied "
13698 "patches to see where a bug got introduced or fixed. You can use the <command "
13699 "role=\"hg-cmd\">hg annotate</command> command to see which changeset or patch "
13700 "modified a particular line of a source file. And so on."
13701 msgstr ""
13703 #. type: Content of: <book><chapter><sect1><title>
13704 #: ../en/ch12-mq.xml:187
13705 msgid "Understanding patches"
13706 msgstr "理解补丁"
13708 #. type: Content of: <book><chapter><sect1><para>
13709 #: ../en/ch12-mq.xml:189
13710 msgid ""
13711 "Because MQ doesn't hide its patch-oriented nature, it is helpful to "
13712 "understand what patches are, and a little about the tools that work with them."
13713 msgstr ""
13715 #. type: Content of: <book><chapter><sect1><para>
13716 #: ../en/ch12-mq.xml:193
13717 msgid ""
13718 "The traditional Unix <command>diff</command> command compares two files, and "
13719 "prints a list of differences between them. The <command>patch</command> "
13720 "command understands these differences as <emphasis>modifications</emphasis> "
13721 "to make to a file. Take a look below for a simple example of these commands "
13722 "in action."
13723 msgstr ""
13725 #. type: Content of: <book><chapter><sect1><para>
13726 #: ../en/ch12-mq.xml:202
13727 msgid ""
13728 "The type of file that <command>diff</command> generates (and <command>patch</"
13729 "command> takes as input) is called a <quote>patch</quote> or a <quote>diff</"
13730 "quote>; there is no difference between a patch and a diff. (We'll use the "
13731 "term <quote>patch</quote>, since it's more commonly used.)"
13732 msgstr ""
13734 #. type: Content of: <book><chapter><sect1><para>
13735 #: ../en/ch12-mq.xml:208
13736 msgid ""
13737 "A patch file can start with arbitrary text; the <command>patch</command> "
13738 "command ignores this text, but MQ uses it as the commit message when creating "
13739 "changesets. To find the beginning of the patch content, <command>patch</"
13740 "command> searches for the first line that starts with the string "
13741 "<quote><literal>diff -</literal></quote>."
13742 msgstr ""
13744 #. type: Content of: <book><chapter><sect1><para>
13745 #: ../en/ch12-mq.xml:215
13746 msgid ""
13747 "MQ works with <emphasis>unified</emphasis> diffs (<command>patch</command> "
13748 "can accept several other diff formats, but MQ doesn't). A unified diff "
13749 "contains two kinds of header. The <emphasis>file header</emphasis> describes "
13750 "the file being modified; it contains the name of the file to modify. When "
13751 "<command>patch</command> sees a new file header, it looks for a file with "
13752 "that name to start modifying."
13753 msgstr ""
13755 #. type: Content of: <book><chapter><sect1><para>
13756 #: ../en/ch12-mq.xml:223
13757 msgid ""
13758 "After the file header comes a series of <emphasis>hunks</emphasis>. Each "
13759 "hunk starts with a header; this identifies the range of line numbers within "
13760 "the file that the hunk should modify. Following the header, a hunk starts "
13761 "and ends with a few (usually three) lines of text from the unmodified file; "
13762 "these are called the <emphasis>context</emphasis> for the hunk. If there's "
13763 "only a small amount of context between successive hunks, <command>diff</"
13764 "command> doesn't print a new hunk header; it just runs the hunks together, "
13765 "with a few lines of context between modifications."
13766 msgstr ""
13768 #. type: Content of: <book><chapter><sect1><para>
13769 #: ../en/ch12-mq.xml:235
13770 msgid ""
13771 "Each line of context begins with a space character. Within the hunk, a line "
13772 "that begins with <quote><literal>-</literal></quote> means <quote>remove this "
13773 "line,</quote> while a line that begins with <quote><literal>+</literal></"
13774 "quote> means <quote>insert this line.</quote> For example, a line that is "
13775 "modified is represented by one deletion and one insertion."
13776 msgstr ""
13778 #. type: Content of: <book><chapter><sect1><para>
13779 #: ../en/ch12-mq.xml:243
13780 msgid ""
13781 "We will return to some of the more subtle aspects of patches later (in "
13782 "section <xref linkend=\"sec.mq.adv-patch\"/>), but you should have enough "
13783 "information now to use MQ."
13784 msgstr ""
13786 #. type: Content of: <book><chapter><sect1><title>
13787 #: ../en/ch12-mq.xml:250
13788 msgid "Getting started with Mercurial Queues"
13789 msgstr "开始使用 MQ"
13791 #. type: Content of: <book><chapter><sect1><para>
13792 #: ../en/ch12-mq.xml:252
13793 msgid ""
13794 "Because MQ is implemented as an extension, you must explicitly enable before "
13795 "you can use it. (You don't need to download anything; MQ ships with the "
13796 "standard Mercurial distribution.) To enable MQ, edit your <filename role="
13797 "\"home\">~/.hgrc</filename> file, and add the lines below."
13798 msgstr ""
13800 #. type: Content of: <book><chapter><sect1><para>
13801 #: ../en/ch12-mq.xml:261
13802 msgid ""
13803 "Once the extension is enabled, it will make a number of new commands "
13804 "available. To verify that the extension is working, you can use <command "
13805 "role=\"hg-cmd\">hg help</command> to see if the <command role=\"hg-ext-mq"
13806 "\">qinit</command> command is now available."
13807 msgstr ""
13809 #. type: Content of: <book><chapter><sect1><para>
13810 #: ../en/ch12-mq.xml:269
13811 msgid ""
13812 "You can use MQ with <emphasis>any</emphasis> Mercurial repository, and its "
13813 "commands only operate within that repository. To get started, simply prepare "
13814 "the repository using the <command role=\"hg-ext-mq\">qinit</command> command."
13815 msgstr ""
13817 #. type: Content of: <book><chapter><sect1><para>
13818 #: ../en/ch12-mq.xml:276
13819 msgid ""
13820 "This command creates an empty directory called <filename role=\"special\" "
13821 "class=\"directory\">.hg/patches</filename>, where MQ will keep its metadata. "
13822 "As with many Mercurial commands, the <command role=\"hg-ext-mq\">qinit</"
13823 "command> command prints nothing if it succeeds."
13824 msgstr ""
13826 #. type: Content of: <book><chapter><sect1><sect2><title>
13827 #: ../en/ch12-mq.xml:283
13828 msgid "Creating a new patch"
13829 msgstr "创建新补丁"
13831 #. type: Content of: <book><chapter><sect1><sect2><para>
13832 #: ../en/ch12-mq.xml:285
13833 msgid ""
13834 "To begin work on a new patch, use the <command role=\"hg-ext-mq\">qnew</"
13835 "command> command. This command takes one argument, the name of the patch to "
13836 "create."
13837 msgstr ""
13839 #. type: Content of: <book><chapter><sect1><sect2><para>
13840 #: ../en/ch12-mq.xml:289
13841 msgid ""
13842 "MQ will use this as the name of an actual file in the <filename role=\"special"
13843 "\" class=\"directory\">.hg/patches</filename> directory, as you can see below."
13844 msgstr ""
13846 #. type: Content of: <book><chapter><sect1><sect2><para>
13847 #: ../en/ch12-mq.xml:296
13848 msgid ""
13849 "Also newly present in the <filename role=\"special\" class=\"directory\">.hg/"
13850 "patches</filename> directory are two other files, <filename role=\"special"
13851 "\">series</filename> and <filename role=\"special\">status</filename>. The "
13852 "<filename role=\"special\">series</filename> file lists all of the patches "
13853 "that MQ knows about for this repository, with one patch per line. Mercurial "
13854 "uses the <filename role=\"special\">status</filename> file for internal book-"
13855 "keeping; it tracks all of the patches that MQ has <emphasis>applied</"
13856 "emphasis> in this repository."
13857 msgstr ""
13859 #. type: Content of: <book><chapter><sect1><sect2><note><para>
13860 #: ../en/ch12-mq.xml:308
13861 msgid ""
13862 "You may sometimes want to edit the <filename role=\"special\">series</"
13863 "filename> file by hand; for example, to change the sequence in which some "
13864 "patches are applied. However, manually editing the <filename role=\"special"
13865 "\">status</filename> file is almost always a bad idea, as it's easy to "
13866 "corrupt MQ's idea of what is happening."
13867 msgstr ""
13869 #. type: Content of: <book><chapter><sect1><sect2><para>
13870 #: ../en/ch12-mq.xml:317
13871 msgid ""
13872 "Once you have created your new patch, you can edit files in the working "
13873 "directory as you usually would. All of the normal Mercurial commands, such "
13874 "as <command role=\"hg-cmd\">hg diff</command> and <command role=\"hg-cmd\">hg "
13875 "annotate</command>, work exactly as they did before."
13876 msgstr ""
13878 #. type: Content of: <book><chapter><sect1><sect2><title>
13879 #: ../en/ch12-mq.xml:325
13880 msgid "Refreshing a patch"
13881 msgstr "刷新补丁"
13883 #. type: Content of: <book><chapter><sect1><sect2><para>
13884 #: ../en/ch12-mq.xml:327
13885 msgid ""
13886 "When you reach a point where you want to save your work, use the <command "
13887 "role=\"hg-ext-mq\">qrefresh</command> command to update the patch you are "
13888 "working on."
13889 msgstr ""
13891 #. type: Content of: <book><chapter><sect1><sect2><para>
13892 #: ../en/ch12-mq.xml:333
13893 msgid ""
13894 "This command folds the changes you have made in the working directory into "
13895 "your patch, and updates its corresponding changeset to contain those changes."
13896 msgstr ""
13898 #. type: Content of: <book><chapter><sect1><sect2><para>
13899 #: ../en/ch12-mq.xml:337
13900 msgid ""
13901 "You can run <command role=\"hg-ext-mq\">qrefresh</command> as often as you "
13902 "like, so it's a good way to <quote>checkpoint</quote> your work. Refresh "
13903 "your patch at an opportune time; try an experiment; and if the experiment "
13904 "doesn't work out, <command role=\"hg-cmd\">hg revert</command> your "
13905 "modifications back to the last time you refreshed."
13906 msgstr ""
13908 #. type: Content of: <book><chapter><sect1><sect2><title>
13909 #: ../en/ch12-mq.xml:348
13910 msgid "Stacking and tracking patches"
13911 msgstr "堆叠和跟踪补丁"
13913 #. type: Content of: <book><chapter><sect1><sect2><para>
13914 #: ../en/ch12-mq.xml:350
13915 msgid ""
13916 "Once you have finished working on a patch, or need to work on another, you "
13917 "can use the <command role=\"hg-ext-mq\">qnew</command> command again to "
13918 "create a new patch. Mercurial will apply this patch on top of your existing "
13919 "patch."
13920 msgstr ""
13922 #. type: Content of: <book><chapter><sect1><sect2><para>
13923 #: ../en/ch12-mq.xml:357
13924 msgid ""
13925 "Notice that the patch contains the changes in our prior patch as part of its "
13926 "context (you can see this more clearly in the output of <command role=\"hg-cmd"
13927 "\">hg annotate</command>)."
13928 msgstr ""
13930 #. type: Content of: <book><chapter><sect1><sect2><para>
13931 #: ../en/ch12-mq.xml:362
13932 msgid ""
13933 "So far, with the exception of <command role=\"hg-ext-mq\">qnew</command> and "
13934 "<command role=\"hg-ext-mq\">qrefresh</command>, we've been careful to only "
13935 "use regular Mercurial commands. However, MQ provides many commands that are "
13936 "easier to use when you are thinking about patches, as illustrated below."
13937 msgstr ""
13939 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13940 #: ../en/ch12-mq.xml:372
13941 msgid ""
13942 "The <command role=\"hg-ext-mq\">qseries</command> command lists every patch "
13943 "that MQ knows about in this repository, from oldest to newest (most recently "
13944 "<emphasis>created</emphasis>)."
13945 msgstr ""
13947 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
13948 #: ../en/ch12-mq.xml:378
13949 msgid ""
13950 "The <command role=\"hg-ext-mq\">qapplied</command> command lists every patch "
13951 "that MQ has <emphasis>applied</emphasis> in this repository, again from "
13952 "oldest to newest (most recently applied)."
13953 msgstr ""
13955 #. type: Content of: <book><chapter><sect1><sect2><title>
13956 #: ../en/ch12-mq.xml:387
13957 msgid "Manipulating the patch stack"
13958 msgstr "操作补丁堆栈"
13960 #. type: Content of: <book><chapter><sect1><sect2><para>
13961 #: ../en/ch12-mq.xml:389
13962 msgid ""
13963 "The previous discussion implied that there must be a difference between "
13964 "<quote>known</quote> and <quote>applied</quote> patches, and there is. MQ "
13965 "can manage a patch without it being applied in the repository."
13966 msgstr ""
13968 #. type: Content of: <book><chapter><sect1><sect2><para>
13969 #: ../en/ch12-mq.xml:394
13970 msgid ""
13971 "An <emphasis>applied</emphasis> patch has a corresponding changeset in the "
13972 "repository, and the effects of the patch and changeset are visible in the "
13973 "working directory. You can undo the application of a patch using the "
13974 "<command role=\"hg-ext-mq\">qpop</command> command. MQ still <emphasis>knows "
13975 "about</emphasis>, or manages, a popped patch, but the patch no longer has a "
13976 "corresponding changeset in the repository, and the working directory does not "
13977 "contain the changes made by the patch. Figure <xref endterm=\"fig.mq.stack."
13978 "caption\" linkend=\"fig.mq.stack\"/> illustrates the difference between "
13979 "applied and tracked patches."
13980 msgstr ""
13982 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject>
13983 #: ../en/ch12-mq.xml:408
13984 msgid "<imageobject><imagedata fileref=\"images/mq-stack.png\"/></imageobject>"
13985 msgstr ""
13987 #. type: Content of: <book><chapter><sect1><sect2><informalfigure><mediaobject><caption><para>
13988 #: ../en/ch12-mq.xml:410
13989 msgid "Applied and unapplied patches in the MQ patch stack"
13990 msgstr ""
13992 #. type: Content of: <book><chapter><sect1><sect2><para>
13993 #: ../en/ch12-mq.xml:415
13994 msgid ""
13995 "You can reapply an unapplied, or popped, patch using the <command role=\"hg-"
13996 "ext-mq\">qpush</command> command. This creates a new changeset to correspond "
13997 "to the patch, and the patch's changes once again become present in the "
13998 "working directory. See below for examples of <command role=\"hg-ext-mq"
13999 "\">qpop</command> and <command role=\"hg-ext-mq\">qpush</command> in action."
14000 msgstr ""
14002 #. type: Content of: <book><chapter><sect1><sect2><para>
14003 #: ../en/ch12-mq.xml:424
14004 msgid ""
14005 "Notice that once we have popped a patch or two patches, the output of "
14006 "<command role=\"hg-ext-mq\">qseries</command> remains the same, while that of "
14007 "<command role=\"hg-ext-mq\">qapplied</command> has changed."
14008 msgstr ""
14010 #. type: Content of: <book><chapter><sect1><sect2><title>
14011 #: ../en/ch12-mq.xml:432
14012 msgid "Pushing and popping many patches"
14013 msgstr "压入或弹出多个补丁"
14015 #. type: Content of: <book><chapter><sect1><sect2><para>
14016 #: ../en/ch12-mq.xml:434
14017 msgid ""
14018 "While <command role=\"hg-ext-mq\">qpush</command> and <command role=\"hg-ext-"
14019 "mq\">qpop</command> each operate on a single patch at a time by default, you "
14020 "can push and pop many patches in one go. The <option role=\"hg-ext-mq-cmd-"
14021 "qpush-opt\">hg -a</option> option to <command role=\"hg-ext-mq\">qpush</"
14022 "command> causes it to push all unapplied patches, while the <option role=\"hg-"
14023 "ext-mq-cmd-qpop-opt\">-a</option> option to <command role=\"hg-ext-mq\">qpop</"
14024 "command> causes it to pop all applied patches. (For some more ways to push "
14025 "and pop many patches, see section <xref linkend=\"sec.mq.perf\"/> below.)"
14026 msgstr ""
14028 #. type: Content of: <book><chapter><sect1><sect2><title>
14029 #: ../en/ch12-mq.xml:451
14030 msgid "Safety checks, and overriding them"
14031 msgstr "安全的检查，然后覆盖它们"
14033 #. type: Content of: <book><chapter><sect1><sect2><para>
14034 #: ../en/ch12-mq.xml:453
14035 msgid ""
14036 "Several MQ commands check the working directory before they do anything, and "
14037 "fail if they find any modifications. They do this to ensure that you won't "
14038 "lose any changes that you have made, but not yet incorporated into a patch. "
14039 "The example below illustrates this; the <command role=\"hg-ext-mq\">qnew</"
14040 "command> command will not create a new patch if there are outstanding "
14041 "changes, caused in this case by the <command role=\"hg-cmd\">hg add</command> "
14042 "of <filename>file3</filename>."
14043 msgstr ""
14045 #. type: Content of: <book><chapter><sect1><sect2><para>
14046 #: ../en/ch12-mq.xml:465
14047 msgid ""
14048 "Commands that check the working directory all take an <quote>I know what I'm "
14049 "doing</quote> option, which is always named <option>-f</option>. The exact "
14050 "meaning of <option>-f</option> depends on the command. For example, <command "
14051 "role=\"hg-cmd\">hg qnew <option role=\"hg-ext-mq-cmd-qnew-opt\">hg -f</"
14052 "option></command> will incorporate any outstanding changes into the new patch "
14053 "it creates, but <command role=\"hg-cmd\">hg qpop <option role=\"hg-ext-mq-cmd-"
14054 "qpop-opt\">hg -f</option></command> will revert modifications to any files "
14055 "affected by the patch that it is popping. Be sure to read the documentation "
14056 "for a command's <option>-f</option> option before you use it!"
14057 msgstr ""
14059 #. type: Content of: <book><chapter><sect1><sect2><title>
14060 #: ../en/ch12-mq.xml:480
14061 msgid "Working on several patches at once"
14062 msgstr "同时处理多个补丁"
14064 #. type: Content of: <book><chapter><sect1><sect2><para>
14065 #: ../en/ch12-mq.xml:482
14066 msgid ""
14067 "The <command role=\"hg-ext-mq\">qrefresh</command> command always refreshes "
14068 "the <emphasis>topmost</emphasis> applied patch. This means that you can "
14069 "suspend work on one patch (by refreshing it), pop or push to make a different "
14070 "patch the top, and work on <emphasis>that</emphasis> patch for a while."
14071 msgstr ""
14073 #. type: Content of: <book><chapter><sect1><sect2><para>
14074 #: ../en/ch12-mq.xml:489
14075 msgid ""
14076 "Here's an example that illustrates how you can use this ability. Let's say "
14077 "you're developing a new feature as two patches. The first is a change to the "
14078 "core of your software, and the second&emdash;layered on top of the "
14079 "first&emdash;changes the user interface to use the code you just added to the "
14080 "core. If you notice a bug in the core while you're working on the UI patch, "
14081 "it's easy to fix the core. Simply <command role=\"hg-ext-mq\">qrefresh</"
14082 "command> the UI patch to save your in-progress changes, and <command role="
14083 "\"hg-ext-mq\">qpop</command> down to the core patch. Fix the core bug, "
14084 "<command role=\"hg-ext-mq\">qrefresh</command> the core patch, and <command "
14085 "role=\"hg-ext-mq\">qpush</command> back to the UI patch to continue where you "
14086 "left off."
14087 msgstr ""
14089 #. type: Content of: <book><chapter><sect1><title>
14090 #: ../en/ch12-mq.xml:506
14091 msgid "More about patches"
14092 msgstr "关于补丁的更多信息"
14094 #. type: Content of: <book><chapter><sect1><para>
14095 #: ../en/ch12-mq.xml:508
14096 msgid ""
14097 "MQ uses the GNU <command>patch</command> command to apply patches, so it's "
14098 "helpful to know a few more detailed aspects of how <command>patch</command> "
14099 "works, and about patches themselves."
14100 msgstr ""
14102 #. type: Content of: <book><chapter><sect1><sect2><title>
14103 #: ../en/ch12-mq.xml:514
14104 msgid "The strip count"
14105 msgstr "修剪计数"
14107 #. type: Content of: <book><chapter><sect1><sect2><para>
14108 #: ../en/ch12-mq.xml:516
14109 msgid ""
14110 "If you look at the file headers in a patch, you will notice that the "
14111 "pathnames usually have an extra component on the front that isn't present in "
14112 "the actual path name. This is a holdover from the way that people used to "
14113 "generate patches (people still do this, but it's somewhat rare with modern "
14114 "revision control tools)."
14115 msgstr ""
14117 #. type: Content of: <book><chapter><sect1><sect2><para>
14118 #: ../en/ch12-mq.xml:523
14119 msgid ""
14120 "Alice would unpack a tarball, edit her files, then decide that she wanted to "
14121 "create a patch. So she'd rename her working directory, unpack the tarball "
14122 "again (hence the need for the rename), and use the <option role=\"cmd-opt-diff"
14123 "\">-r</option> and <option role=\"cmd-opt-diff\">-N</option> options to "
14124 "<command>diff</command> to recursively generate a patch between the "
14125 "unmodified directory and the modified one. The result would be that the name "
14126 "of the unmodified directory would be at the front of the left-hand path in "
14127 "every file header, and the name of the modified directory would be at the "
14128 "front of the right-hand path."
14129 msgstr ""
14131 #. type: Content of: <book><chapter><sect1><sect2><para>
14132 #: ../en/ch12-mq.xml:536
14133 msgid ""
14134 "Since someone receiving a patch from the Alices of the net would be unlikely "
14135 "to have unmodified and modified directories with exactly the same names, the "
14136 "<command>patch</command> command has a <option role=\"cmd-opt-patch\">-p</"
14137 "option> option that indicates the number of leading path name components to "
14138 "strip when trying to apply a patch. This number is called the "
14139 "<emphasis>strip count</emphasis>."
14140 msgstr ""
14142 #. type: Content of: <book><chapter><sect1><sect2><para>
14143 #: ../en/ch12-mq.xml:544
14144 msgid ""
14145 "An option of <quote><literal>-p1</literal></quote> means <quote>use a strip "
14146 "count of one</quote>. If <command>patch</command> sees a file name "
14147 "<filename>foo/bar/baz</filename> in a file header, it will strip "
14148 "<filename>foo</filename> and try to patch a file named <filename>bar/baz</"
14149 "filename>. (Strictly speaking, the strip count refers to the number of "
14150 "<emphasis>path separators</emphasis> (and the components that go with them ) "
14151 "to strip. A strip count of one will turn <filename>foo/bar</filename> into "
14152 "<filename>bar</filename>, but <filename>/foo/bar</filename> (notice the extra "
14153 "leading slash) into <filename>foo/bar</filename>.)"
14154 msgstr ""
14156 #. type: Content of: <book><chapter><sect1><sect2><para>
14157 #: ../en/ch12-mq.xml:557
14158 msgid ""
14159 "The <quote>standard</quote> strip count for patches is one; almost all "
14160 "patches contain one leading path name component that needs to be stripped. "
14161 "Mercurial's <command role=\"hg-cmd\">hg diff</command> command generates path "
14162 "names in this form, and the <command role=\"hg-cmd\">hg import</command> "
14163 "command and MQ expect patches to have a strip count of one."
14164 msgstr ""
14166 #. type: Content of: <book><chapter><sect1><sect2><para>
14167 #: ../en/ch12-mq.xml:565
14168 msgid ""
14169 "If you receive a patch from someone that you want to add to your patch queue, "
14170 "and the patch needs a strip count other than one, you cannot just <command "
14171 "role=\"hg-ext-mq\">qimport</command> the patch, because <command role=\"hg-"
14172 "ext-mq\">qimport</command> does not yet have a <literal>-p</literal> option "
14173 "(see <ulink role=\"hg-bug\" url=\"http://www.selenic.com/mercurial/bts/"
14174 "issue311\">issue 311</ulink>). Your best bet is to <command role=\"hg-ext-mq"
14175 "\">qnew</command> a patch of your own, then use <command>patch -pN</command> "
14176 "to apply their patch, followed by <command role=\"hg-cmd\">hg addremove</"
14177 "command> to pick up any files added or removed by the patch, followed by "
14178 "<command role=\"hg-ext-mq\">hg qrefresh</command>. This complexity may become "
14179 "unnecessary; see <ulink role=\"hg-bug\" url=\"http://www.selenic.com/"
14180 "mercurial/bts/issue311\">issue 311</ulink> for details."
14181 msgstr ""
14183 #. type: Content of: <book><chapter><sect1><sect2><title>
14184 #: ../en/ch12-mq.xml:584
14185 msgid "Strategies for applying a patch"
14186 msgstr "应用补丁的策略"
14188 #. type: Content of: <book><chapter><sect1><sect2><para>
14189 #: ../en/ch12-mq.xml:586
14190 msgid ""
14191 "When <command>patch</command> applies a hunk, it tries a handful of "
14192 "successively less accurate strategies to try to make the hunk apply. This "
14193 "falling-back technique often makes it possible to take a patch that was "
14194 "generated against an old version of a file, and apply it against a newer "
14195 "version of that file."
14196 msgstr ""
14198 #. type: Content of: <book><chapter><sect1><sect2><para>
14199 #: ../en/ch12-mq.xml:593
14200 msgid ""
14201 "First, <command>patch</command> tries an exact match, where the line numbers, "
14202 "the context, and the text to be modified must apply exactly. If it cannot "
14203 "make an exact match, it tries to find an exact match for the context, without "
14204 "honouring the line numbering information. If this succeeds, it prints a line "
14205 "of output saying that the hunk was applied, but at some <emphasis>offset</"
14206 "emphasis> from the original line number."
14207 msgstr ""
14209 #. type: Content of: <book><chapter><sect1><sect2><para>
14210 #: ../en/ch12-mq.xml:602
14211 msgid ""
14212 "If a context-only match fails, <command>patch</command> removes the first and "
14213 "last lines of the context, and tries a <emphasis>reduced</emphasis> context-"
14214 "only match. If the hunk with reduced context succeeds, it prints a message "
14215 "saying that it applied the hunk with a <emphasis>fuzz factor</emphasis> (the "
14216 "number after the fuzz factor indicates how many lines of context "
14217 "<command>patch</command> had to trim before the patch applied)."
14218 msgstr ""
14220 #. type: Content of: <book><chapter><sect1><sect2><para>
14221 #: ../en/ch12-mq.xml:611
14222 msgid ""
14223 "When neither of these techniques works, <command>patch</command> prints a "
14224 "message saying that the hunk in question was rejected. It saves rejected "
14225 "hunks (also simply called <quote>rejects</quote>) to a file with the same "
14226 "name, and an added <filename role=\"special\">.rej</filename> extension. It "
14227 "also saves an unmodified copy of the file with a <filename role=\"special\">."
14228 "orig</filename> extension; the copy of the file without any extensions will "
14229 "contain any changes made by hunks that <emphasis>did</emphasis> apply "
14230 "cleanly. If you have a patch that modifies <filename>foo</filename> with six "
14231 "hunks, and one of them fails to apply, you will have: an unmodified "
14232 "<filename>foo.orig</filename>, a <filename>foo.rej</filename> containing one "
14233 "hunk, and <filename>foo</filename>, containing the changes made by the five "
14234 "successful hunks."
14235 msgstr ""
14237 #. type: Content of: <book><chapter><sect1><sect2><title>
14238 #: ../en/ch12-mq.xml:629
14239 msgid "Some quirks of patch representation"
14240 msgstr "补丁的一些特性"
14242 #. type: Content of: <book><chapter><sect1><sect2><para>
14243 #: ../en/ch12-mq.xml:631
14244 msgid ""
14245 "There are a few useful things to know about how <command>patch</command> "
14246 "works with files."
14247 msgstr ""
14249 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14250 #: ../en/ch12-mq.xml:634
14251 msgid ""
14252 "This should already be obvious, but <command>patch</command> cannot handle "
14253 "binary files."
14254 msgstr ""
14256 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14257 #: ../en/ch12-mq.xml:638
14258 msgid ""
14259 "Neither does it care about the executable bit; it creates new files as "
14260 "readable, but not executable."
14261 msgstr ""
14263 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14264 #: ../en/ch12-mq.xml:642
14265 msgid ""
14266 "<command>patch</command> treats the removal of a file as a diff between the "
14267 "file to be removed and the empty file. So your idea of <quote>I deleted this "
14268 "file</quote> looks like <quote>every line of this file was deleted</quote> in "
14269 "a patch."
14270 msgstr ""
14272 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14273 #: ../en/ch12-mq.xml:648
14274 msgid ""
14275 "It treats the addition of a file as a diff between the empty file and the "
14276 "file to be added. So in a patch, your idea of <quote>I added this file</"
14277 "quote> looks like <quote>every line of this file was added</quote>."
14278 msgstr ""
14280 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14281 #: ../en/ch12-mq.xml:654
14282 msgid ""
14283 "It treats a renamed file as the removal of the old name, and the addition of "
14284 "the new name. This means that renamed files have a big footprint in "
14285 "patches. (Note also that Mercurial does not currently try to infer when "
14286 "files have been renamed or copied in a patch.)"
14287 msgstr ""
14289 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14290 #: ../en/ch12-mq.xml:660
14291 msgid ""
14292 "<command>patch</command> cannot represent empty files, so you cannot use a "
14293 "patch to represent the notion <quote>I added this empty file to the tree</"
14294 "quote>."
14295 msgstr ""
14297 #. type: Content of: <book><chapter><sect1><sect2><title>
14298 #: ../en/ch12-mq.xml:667
14299 msgid "Beware the fuzz"
14300 msgstr "当心毛刺"
14302 #. type: Content of: <book><chapter><sect1><sect2><para>
14303 #: ../en/ch12-mq.xml:669
14304 msgid ""
14305 "While applying a hunk at an offset, or with a fuzz factor, will often be "
14306 "completely successful, these inexact techniques naturally leave open the "
14307 "possibility of corrupting the patched file. The most common cases typically "
14308 "involve applying a patch twice, or at an incorrect location in the file. If "
14309 "<command>patch</command> or <command role=\"hg-ext-mq\">qpush</command> ever "
14310 "mentions an offset or fuzz factor, you should make sure that the modified "
14311 "files are correct afterwards."
14312 msgstr ""
14314 #. type: Content of: <book><chapter><sect1><sect2><para>
14315 #: ../en/ch12-mq.xml:679
14316 msgid ""
14317 "It's often a good idea to refresh a patch that has applied with an offset or "
14318 "fuzz factor; refreshing the patch generates new context information that will "
14319 "make it apply cleanly. I say <quote>often,</quote> not <quote>always,</"
14320 "quote> because sometimes refreshing a patch will make it fail to apply "
14321 "against a different revision of the underlying files. In some cases, such as "
14322 "when you're maintaining a patch that must sit on top of multiple versions of "
14323 "a source tree, it's acceptable to have a patch apply with some fuzz, provided "
14324 "you've verified the results of the patching process in such cases."
14325 msgstr ""
14327 #. type: Content of: <book><chapter><sect1><sect2><title>
14328 #: ../en/ch12-mq.xml:692
14329 msgid "Handling rejection"
14330 msgstr "处理拒绝"
14332 #. type: Content of: <book><chapter><sect1><sect2><para>
14333 #: ../en/ch12-mq.xml:694
14334 msgid ""
14335 "If <command role=\"hg-ext-mq\">qpush</command> fails to apply a patch, it "
14336 "will print an error message and exit. If it has left <filename role=\"special"
14337 "\">.rej</filename> files behind, it is usually best to fix up the rejected "
14338 "hunks before you push more patches or do any further work."
14339 msgstr ""
14341 #. type: Content of: <book><chapter><sect1><sect2><para>
14342 #: ../en/ch12-mq.xml:700
14343 msgid ""
14344 "If your patch <emphasis>used to</emphasis> apply cleanly, and no longer does "
14345 "because you've changed the underlying code that your patches are based on, "
14346 "Mercurial Queues can help; see section <xref linkend=\"sec.mq.merge\"/> for "
14347 "details."
14348 msgstr ""
14350 #. type: Content of: <book><chapter><sect1><sect2><para>
14351 #: ../en/ch12-mq.xml:706
14352 msgid ""
14353 "Unfortunately, there aren't any great techniques for dealing with rejected "
14354 "hunks. Most often, you'll need to view the <filename role=\"special\">.rej</"
14355 "filename> file and edit the target file, applying the rejected hunks by hand."
14356 msgstr ""
14358 #. type: Content of: <book><chapter><sect1><sect2><para>
14359 #: ../en/ch12-mq.xml:711
14360 msgid ""
14361 "If you're feeling adventurous, Neil Brown, a Linux kernel hacker, wrote a "
14362 "tool called <command>wiggle</command> <citation>web:wiggle</citation>, which "
14363 "is more vigorous than <command>patch</command> in its attempts to make a "
14364 "patch apply."
14365 msgstr ""
14367 #. type: Content of: <book><chapter><sect1><sect2><para>
14368 #: ../en/ch12-mq.xml:717
14369 msgid ""
14370 "Another Linux kernel hacker, Chris Mason (the author of Mercurial Queues), "
14371 "wrote a similar tool called <command>mpatch</command> <citation>web:mpatch</"
14372 "citation>, which takes a simple approach to automating the application of "
14373 "hunks rejected by <command>patch</command>. The <command>mpatch</command> "
14374 "command can help with four common reasons that a hunk may be rejected:"
14375 msgstr ""
14377 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14378 #: ../en/ch12-mq.xml:726
14379 msgid "The context in the middle of a hunk has changed."
14380 msgstr ""
14382 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14383 #: ../en/ch12-mq.xml:729
14384 msgid "A hunk is missing some context at the beginning or end."
14385 msgstr ""
14387 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14388 #: ../en/ch12-mq.xml:732
14389 msgid ""
14390 "A large hunk might apply better&emdash;either entirely or in part&emdash;if "
14391 "it was broken up into smaller hunks."
14392 msgstr ""
14394 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
14395 #: ../en/ch12-mq.xml:736
14396 msgid ""
14397 "A hunk removes lines with slightly different content than those currently "
14398 "present in the file."
14399 msgstr ""
14401 #. type: Content of: <book><chapter><sect1><sect2><para>
14402 #: ../en/ch12-mq.xml:740
14403 msgid ""
14404 "If you use <command>wiggle</command> or <command>mpatch</command>, you should "
14405 "be doubly careful to check your results when you're done. In fact, "
14406 "<command>mpatch</command> enforces this method of double-checking the tool's "
14407 "output, by automatically dropping you into a merge program when it has done "
14408 "its job, so that you can verify its work and finish off any remaining merges."
14409 msgstr ""
14411 #. type: Content of: <book><chapter><sect1><title>
14412 #: ../en/ch12-mq.xml:752
14413 msgid "Getting the best performance out of MQ"
14414 msgstr "MQ 的性能"
14416 #. type: Content of: <book><chapter><sect1><para>
14417 #: ../en/ch12-mq.xml:754
14418 msgid ""
14419 "MQ is very efficient at handling a large number of patches. I ran some "
14420 "performance experiments in mid-2006 for a talk that I gave at the 2006 "
14421 "EuroPython conference <citation>web:europython</citation>. I used as my data "
14422 "set the Linux 2.6.17-mm1 patch series, which consists of 1,738 patches. I "
14423 "applied these on top of a Linux kernel repository containing all 27,472 "
14424 "revisions between Linux 2.6.12-rc2 and Linux 2.6.17."
14425 msgstr ""
14427 #. type: Content of: <book><chapter><sect1><para>
14428 #: ../en/ch12-mq.xml:763
14429 msgid ""
14430 "On my old, slow laptop, I was able to <command role=\"hg-cmd\">hg qpush "
14431 "<option role=\"hg-ext-mq-cmd-qpush-opt\">hg -a</option></command> all 1,738 "
14432 "patches in 3.5 minutes, and <command role=\"hg-cmd\">hg qpop <option role="
14433 "\"hg-ext-mq-cmd-qpop-opt\">hg -a</option></command> them all in 30 seconds. "
14434 "(On a newer laptop, the time to push all patches dropped to two minutes.) I "
14435 "could <command role=\"hg-ext-mq\">qrefresh</command> one of the biggest "
14436 "patches (which made 22,779 lines of changes to 287 files) in 6.6 seconds."
14437 msgstr ""
14439 #. type: Content of: <book><chapter><sect1><para>
14440 #: ../en/ch12-mq.xml:774
14441 msgid ""
14442 "Clearly, MQ is well suited to working in large trees, but there are a few "
14443 "tricks you can use to get the best performance of it."
14444 msgstr ""
14446 #. type: Content of: <book><chapter><sect1><para>
14447 #: ../en/ch12-mq.xml:778
14448 msgid ""
14449 "First of all, try to <quote>batch</quote> operations together. Every time "
14450 "you run <command role=\"hg-ext-mq\">qpush</command> or <command role=\"hg-ext-"
14451 "mq\">qpop</command>, these commands scan the working directory once to make "
14452 "sure you haven't made some changes and then forgotten to run <command role="
14453 "\"hg-ext-mq\">qrefresh</command>. On a small tree, the time that this scan "
14454 "takes is unnoticeable. However, on a medium-sized tree (containing tens of "
14455 "thousands of files), it can take a second or more."
14456 msgstr ""
14458 #. type: Content of: <book><chapter><sect1><para>
14459 #: ../en/ch12-mq.xml:789
14460 msgid ""
14461 "The <command role=\"hg-ext-mq\">qpush</command> and <command role=\"hg-ext-mq"
14462 "\">qpop</command> commands allow you to push and pop multiple patches at a "
14463 "time. You can identify the <quote>destination patch</quote> that you want to "
14464 "end up at. When you <command role=\"hg-ext-mq\">qpush</command> with a "
14465 "destination specified, it will push patches until that patch is at the top of "
14466 "the applied stack. When you <command role=\"hg-ext-mq\">qpop</command> to a "
14467 "destination, MQ will pop patches until the destination patch is at the top."
14468 msgstr ""
14470 #. type: Content of: <book><chapter><sect1><para>
14471 #: ../en/ch12-mq.xml:799
14472 msgid ""
14473 "You can identify a destination patch using either the name of the patch, or "
14474 "by number. If you use numeric addressing, patches are counted from zero; "
14475 "this means that the first patch is zero, the second is one, and so on."
14476 msgstr ""
14478 #. type: Content of: <book><chapter><sect1><title>
14479 #: ../en/ch12-mq.xml:806
14480 msgid "Updating your patches when the underlying code changes"
14481 msgstr "当基础代码改变时，更新补丁的方法"
14483 #. type: Content of: <book><chapter><sect1><para>
14484 #: ../en/ch12-mq.xml:809
14485 msgid ""
14486 "It's common to have a stack of patches on top of an underlying repository "
14487 "that you don't modify directly. If you're working on changes to third-party "
14488 "code, or on a feature that is taking longer to develop than the rate of "
14489 "change of the code beneath, you will often need to sync up with the "
14490 "underlying code, and fix up any hunks in your patches that no longer apply. "
14491 "This is called <emphasis>rebasing</emphasis> your patch series."
14492 msgstr ""
14494 #. type: Content of: <book><chapter><sect1><para>
14495 #: ../en/ch12-mq.xml:818
14496 msgid ""
14497 "The simplest way to do this is to <command role=\"hg-cmd\">hg qpop <option "
14498 "role=\"hg-ext-mq-cmd-qpop-opt\">hg -a</option></command> your patches, then "
14499 "<command role=\"hg-cmd\">hg pull</command> changes into the underlying "
14500 "repository, and finally <command role=\"hg-cmd\">hg qpush <option role=\"hg-"
14501 "ext-mq-cmd-qpop-opt\">hg -a</option></command> your patches again. MQ will "
14502 "stop pushing any time it runs across a patch that fails to apply during "
14503 "conflicts, allowing you to fix your conflicts, <command role=\"hg-ext-mq"
14504 "\">qrefresh</command> the affected patch, and continue pushing until you have "
14505 "fixed your entire stack."
14506 msgstr ""
14508 #. type: Content of: <book><chapter><sect1><para>
14509 #: ../en/ch12-mq.xml:830
14510 msgid ""
14511 "This approach is easy to use and works well if you don't expect changes to "
14512 "the underlying code to affect how well your patches apply. If your patch "
14513 "stack touches code that is modified frequently or invasively in the "
14514 "underlying repository, however, fixing up rejected hunks by hand quickly "
14515 "becomes tiresome."
14516 msgstr ""
14518 #. type: Content of: <book><chapter><sect1><para>
14519 #: ../en/ch12-mq.xml:837
14520 msgid ""
14521 "It's possible to partially automate the rebasing process. If your patches "
14522 "apply cleanly against some revision of the underlying repo, MQ can use this "
14523 "information to help you to resolve conflicts between your patches and a "
14524 "different revision."
14525 msgstr ""
14527 #. type: Content of: <book><chapter><sect1><para>
14528 #: ../en/ch12-mq.xml:843
14529 msgid "The process is a little involved."
14530 msgstr ""
14532 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
14533 #: ../en/ch12-mq.xml:845
14534 msgid ""
14535 "To begin, <command role=\"hg-cmd\">hg qpush -a</command> all of your patches "
14536 "on top of the revision where you know that they apply cleanly."
14537 msgstr ""
14539 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
14540 #: ../en/ch12-mq.xml:849
14541 msgid ""
14542 "Save a backup copy of your patch directory using <command role=\"hg-cmd\">hg "
14543 "qsave <option role=\"hg-ext-mq-cmd-qsave-opt\">hg -e</option> <option role="
14544 "\"hg-ext-mq-cmd-qsave-opt\">hg -c</option></command>. This prints the name "
14545 "of the directory that it has saved the patches in. It will save the patches "
14546 "to a directory called <filename role=\"special\" class=\"directory\">.hg/"
14547 "patches.N</filename>, where <literal>N</literal> is a small integer. It also "
14548 "commits a <quote>save changeset</quote> on top of your applied patches; this "
14549 "is for internal book-keeping, and records the states of the <filename role="
14550 "\"special\">series</filename> and <filename role=\"special\">status</"
14551 "filename> files."
14552 msgstr ""
14554 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
14555 #: ../en/ch12-mq.xml:863
14556 msgid ""
14557 "Use <command role=\"hg-cmd\">hg pull</command> to bring new changes into the "
14558 "underlying repository. (Don't run <command role=\"hg-cmd\">hg pull -u</"
14559 "command>; see below for why.)"
14560 msgstr ""
14562 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
14563 #: ../en/ch12-mq.xml:868
14564 msgid ""
14565 "Update to the new tip revision, using <command role=\"hg-cmd\">hg update "
14566 "<option role=\"hg-opt-update\">-C</option></command> to override the patches "
14567 "you have pushed."
14568 msgstr ""
14570 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
14571 #: ../en/ch12-mq.xml:873
14572 msgid ""
14573 "Merge all patches using \\hgcmdargs{qpush}{<option role=\"hg-ext-mq-cmd-qpush-"
14574 "opt\">hg -m</option> <option role=\"hg-ext-mq-cmd-qpush-opt\">hg -a</"
14575 "option>}. The <option role=\"hg-ext-mq-cmd-qpush-opt\">hg -m</option> option "
14576 "to <command role=\"hg-ext-mq\">qpush</command> tells MQ to perform a three-"
14577 "way merge if the patch fails to apply."
14578 msgstr ""
14580 #. type: Content of: <book><chapter><sect1><para>
14581 #: ../en/ch12-mq.xml:883
14582 msgid ""
14583 "During the <command role=\"hg-cmd\">hg qpush <option role=\"hg-ext-mq-cmd-"
14584 "qpush-opt\">hg -m</option></command>, each patch in the <filename role="
14585 "\"special\">series</filename> file is applied normally. If a patch applies "
14586 "with fuzz or rejects, MQ looks at the queue you <command role=\"hg-ext-mq"
14587 "\">qsave</command>d, and performs a three-way merge with the corresponding "
14588 "changeset. This merge uses Mercurial's normal merge machinery, so it may pop "
14589 "up a GUI merge tool to help you to resolve problems."
14590 msgstr ""
14592 #. type: Content of: <book><chapter><sect1><para>
14593 #: ../en/ch12-mq.xml:893
14594 msgid ""
14595 "When you finish resolving the effects of a patch, MQ refreshes your patch "
14596 "based on the result of the merge."
14597 msgstr ""
14599 #. type: Content of: <book><chapter><sect1><para>
14600 #: ../en/ch12-mq.xml:896
14601 msgid ""
14602 "At the end of this process, your repository will have one extra head from the "
14603 "old patch queue, and a copy of the old patch queue will be in <filename role="
14604 "\"special\" class=\"directory\">.hg/patches.N</filename>. You can remove the "
14605 "extra head using <command role=\"hg-cmd\">hg qpop -a -n patches.N</command> "
14606 "or <command role=\"hg-cmd\">hg strip</command>. You can delete <filename "
14607 "role=\"special\" class=\"directory\">.hg/patches.N</filename> once you are "
14608 "sure that you no longer need it as a backup."
14609 msgstr ""
14611 #. type: Content of: <book><chapter><sect1><title>
14612 #: ../en/ch12-mq.xml:908
14613 msgid "Identifying patches"
14614 msgstr "标识补丁"
14616 #. type: Content of: <book><chapter><sect1><para>
14617 #: ../en/ch12-mq.xml:910
14618 msgid ""
14619 "MQ commands that work with patches let you refer to a patch either by using "
14620 "its name or by a number. By name is obvious enough; pass the name "
14621 "<filename>foo.patch</filename> to <command role=\"hg-ext-mq\">qpush</"
14622 "command>, for example, and it will push patches until <filename>foo.patch</"
14623 "filename> is applied."
14624 msgstr ""
14626 #. type: Content of: <book><chapter><sect1><para>
14627 #: ../en/ch12-mq.xml:917
14628 msgid ""
14629 "As a shortcut, you can refer to a patch using both a name and a numeric "
14630 "offset; <literal>foo.patch-2</literal> means <quote>two patches before "
14631 "<literal>foo.patch</literal></quote>, while <literal>bar.patch+4</literal> "
14632 "means <quote>four patches after <literal>bar.patch</literal></quote>."
14633 msgstr ""
14635 #. type: Content of: <book><chapter><sect1><para>
14636 #: ../en/ch12-mq.xml:923
14637 msgid ""
14638 "Referring to a patch by index isn't much different. The first patch printed "
14639 "in the output of <command role=\"hg-ext-mq\">qseries</command> is patch zero "
14640 "(yes, it's one of those start-at-zero counting systems); the second is patch "
14641 "one; and so on."
14642 msgstr ""
14644 #. type: Content of: <book><chapter><sect1><para>
14645 #: ../en/ch12-mq.xml:929
14646 msgid ""
14647 "MQ also makes it easy to work with patches when you are using normal "
14648 "Mercurial commands. Every command that accepts a changeset ID will also "
14649 "accept the name of an applied patch. MQ augments the tags normally in the "
14650 "repository with an eponymous one for each applied patch. In addition, the "
14651 "special tags \\index{tags!special tag names!<literal>qbase</literal>}"
14652 "<literal>qbase</literal> and \\index{tags!special tag names!<literal>qtip</"
14653 "literal>}<literal>qtip</literal> identify the <quote>bottom-most</quote> and "
14654 "topmost applied patches, respectively."
14655 msgstr ""
14657 #. type: Content of: <book><chapter><sect1><para>
14658 #: ../en/ch12-mq.xml:941
14659 msgid ""
14660 "These additions to Mercurial's normal tagging capabilities make dealing with "
14661 "patches even more of a breeze."
14662 msgstr ""
14664 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
14665 #: ../en/ch12-mq.xml:944
14666 msgid "Want to patchbomb a mailing list with your latest series of changes?"
14667 msgstr ""
14669 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
14670 #: ../en/ch12-mq.xml:948
14671 msgid ""
14672 "(Don't know what <quote>patchbombing</quote> is? See section <xref linkend="
14673 "\"sec.hgext.patchbomb\"/>.)"
14674 msgstr ""
14676 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
14677 #: ../en/ch12-mq.xml:951
14678 msgid ""
14679 "Need to see all of the patches since <literal>foo.patch</literal> that have "
14680 "touched files in a subdirectory of your tree?"
14681 msgstr ""
14683 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><programlisting><emphasis>
14684 #: ../en/ch12-mq.xml:955
14685 msgid "subdir"
14686 msgstr ""
14688 #. type: Content of: <book><chapter><sect1><para>
14689 #: ../en/ch12-mq.xml:960
14690 msgid ""
14691 "Because MQ makes the names of patches available to the rest of Mercurial "
14692 "through its normal internal tag machinery, you don't need to type in the "
14693 "entire name of a patch when you want to identify it by name."
14694 msgstr ""
14696 #. type: Content of: <book><chapter><sect1><para>
14697 #: ../en/ch12-mq.xml:965
14698 msgid ""
14699 "Another nice consequence of representing patch names as tags is that when you "
14700 "run the <command role=\"hg-cmd\">hg log</command> command, it will display a "
14701 "patch's name as a tag, simply as part of its normal output. This makes it "
14702 "easy to visually distinguish applied patches from underlying <quote>normal</"
14703 "quote> revisions. The following example shows a few normal Mercurial "
14704 "commands in use with applied patches."
14705 msgstr ""
14707 #. type: Content of: <book><chapter><sect1><title>
14708 #: ../en/ch12-mq.xml:978
14709 msgid "Useful things to know about"
14710 msgstr "其它需要了解的东西"
14712 #. type: Content of: <book><chapter><sect1><para>
14713 #: ../en/ch12-mq.xml:980
14714 msgid ""
14715 "There are a number of aspects of MQ usage that don't fit tidily into sections "
14716 "of their own, but that are good to know. Here they are, in one place."
14717 msgstr ""
14719 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
14720 #: ../en/ch12-mq.xml:985
14721 msgid ""
14722 "Normally, when you <command role=\"hg-ext-mq\">qpop</command> a patch and "
14723 "<command role=\"hg-ext-mq\">qpush</command> it again, the changeset that "
14724 "represents the patch after the pop/push will have a <emphasis>different "
14725 "identity</emphasis> than the changeset that represented the hash beforehand. "
14726 "See section <xref linkend=\"sec.mqref.cmd.qpush\"/> for information as to why "
14727 "this is."
14728 msgstr ""
14730 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
14731 #: ../en/ch12-mq.xml:994
14732 msgid ""
14733 "It's not a good idea to <command role=\"hg-cmd\">hg merge</command> changes "
14734 "from another branch with a patch changeset, at least if you want to maintain "
14735 "the <quote>patchiness</quote> of that changeset and changesets below it on "
14736 "the patch stack. If you try to do this, it will appear to succeed, but MQ "
14737 "will become confused."
14738 msgstr ""
14740 #. type: Content of: <book><chapter><sect1><title>
14741 #: ../en/ch12-mq.xml:1005
14742 msgid "Managing patches in a repository"
14743 msgstr "在版本库管理补丁"
14745 #. type: Content of: <book><chapter><sect1><para>
14746 #: ../en/ch12-mq.xml:1007
14747 msgid ""
14748 "Because MQ's <filename role=\"special\" class=\"directory\">.hg/patches</"
14749 "filename> directory resides outside a Mercurial repository's working "
14750 "directory, the <quote>underlying</quote> Mercurial repository knows nothing "
14751 "about the management or presence of patches."
14752 msgstr ""
14754 #. type: Content of: <book><chapter><sect1><para>
14755 #: ../en/ch12-mq.xml:1013
14756 msgid ""
14757 "This presents the interesting possibility of managing the contents of the "
14758 "patch directory as a Mercurial repository in its own right. This can be a "
14759 "useful way to work. For example, you can work on a patch for a while, "
14760 "<command role=\"hg-ext-mq\">qrefresh</command> it, then <command role=\"hg-cmd"
14761 "\">hg commit</command> the current state of the patch. This lets you "
14762 "<quote>roll back</quote> to that version of the patch later on."
14763 msgstr ""
14765 #. type: Content of: <book><chapter><sect1><para>
14766 #: ../en/ch12-mq.xml:1022
14767 msgid ""
14768 "You can then share different versions of the same patch stack among multiple "
14769 "underlying repositories. I use this when I am developing a Linux kernel "
14770 "feature. I have a pristine copy of my kernel sources for each of several CPU "
14771 "architectures, and a cloned repository under each that contains the patches I "
14772 "am working on. When I want to test a change on a different architecture, I "
14773 "push my current patches to the patch repository associated with that kernel "
14774 "tree, pop and push all of my patches, and build and test that kernel."
14775 msgstr ""
14777 #. type: Content of: <book><chapter><sect1><para>
14778 #: ../en/ch12-mq.xml:1032
14779 msgid ""
14780 "Managing patches in a repository makes it possible for multiple developers to "
14781 "work on the same patch series without colliding with each other, all on top "
14782 "of an underlying source base that they may or may not control."
14783 msgstr ""
14785 #. type: Content of: <book><chapter><sect1><sect2><title>
14786 #: ../en/ch12-mq.xml:1038
14787 msgid "MQ support for patch repositories"
14788 msgstr "MQ 支持补丁版本库"
14790 #. type: Content of: <book><chapter><sect1><sect2><para>
14791 #: ../en/ch12-mq.xml:1040
14792 msgid ""
14793 "MQ helps you to work with the <filename role=\"special\" class=\"directory\">."
14794 "hg/patches</filename> directory as a repository; when you prepare a "
14795 "repository for working with patches using <command role=\"hg-ext-mq\">qinit</"
14796 "command>, you can pass the <option role=\"hg-ext-mq-cmd-qinit-opt\">hg -c</"
14797 "option> option to create the <filename role=\"special\" class=\"directory\">."
14798 "hg/patches</filename> directory as a Mercurial repository."
14799 msgstr ""
14801 #. type: Content of: <book><chapter><sect1><sect2><note><para>
14802 #: ../en/ch12-mq.xml:1050
14803 msgid ""
14804 "If you forget to use the <option role=\"hg-ext-mq-cmd-qinit-opt\">hg -c</"
14805 "option> option, you can simply go into the <filename role=\"special\" class="
14806 "\"directory\">.hg/patches</filename> directory at any time and run <command "
14807 "role=\"hg-cmd\">hg init</command>. Don't forget to add an entry for the "
14808 "<filename role=\"special\">status</filename> file to the <filename role="
14809 "\"special\">.hgignore</filename> file, though"
14810 msgstr ""
14812 #. type: Content of: <book><chapter><sect1><sect2><note><para>
14813 #: ../en/ch12-mq.xml:1059
14814 msgid ""
14815 "(<command role=\"hg-cmd\">hg qinit <option role=\"hg-ext-mq-cmd-qinit-opt"
14816 "\">hg -c</option></command> does this for you automatically); you "
14817 "<emphasis>really</emphasis> don't want to manage the <filename role=\"special"
14818 "\">status</filename> file."
14819 msgstr ""
14821 #. type: Content of: <book><chapter><sect1><sect2><para>
14822 #: ../en/ch12-mq.xml:1066
14823 msgid ""
14824 "As a convenience, if MQ notices that the <filename class=\"directory\">.hg/"
14825 "patches</filename> directory is a repository, it will automatically <command "
14826 "role=\"hg-cmd\">hg add</command> every patch that you create and import."
14827 msgstr ""
14829 #. type: Content of: <book><chapter><sect1><sect2><para>
14830 #: ../en/ch12-mq.xml:1071
14831 msgid ""
14832 "MQ provides a shortcut command, <command role=\"hg-ext-mq\">qcommit</"
14833 "command>, that runs <command role=\"hg-cmd\">hg commit</command> in the "
14834 "<filename role=\"special\" class=\"directory\">.hg/patches</filename> "
14835 "directory. This saves some bothersome typing."
14836 msgstr ""
14838 #. type: Content of: <book><chapter><sect1><sect2><para>
14839 #: ../en/ch12-mq.xml:1077
14840 msgid ""
14841 "Finally, as a convenience to manage the patch directory, you can define the "
14842 "alias <command>mq</command> on Unix systems. For example, on Linux systems "
14843 "using the <command>bash</command> shell, you can include the following "
14844 "snippet in your <filename role=\"home\">~/.bashrc</filename>."
14845 msgstr ""
14847 #. type: Content of: <book><chapter><sect1><sect2><para>
14848 #: ../en/ch12-mq.xml:1087
14849 msgid ""
14850 "You can then issue commands of the form <command>mq pull</command> from the "
14851 "main repository."
14852 msgstr ""
14854 #. type: Content of: <book><chapter><sect1><sect2><title>
14855 #: ../en/ch12-mq.xml:1092
14856 msgid "A few things to watch out for"
14857 msgstr "需要注意的事情"
14859 #. type: Content of: <book><chapter><sect1><sect2><para>
14860 #: ../en/ch12-mq.xml:1094
14861 msgid ""
14862 "MQ's support for working with a repository full of patches is limited in a "
14863 "few small respects."
14864 msgstr ""
14866 #. type: Content of: <book><chapter><sect1><sect2><para>
14867 #: ../en/ch12-mq.xml:1097
14868 msgid ""
14869 "MQ cannot automatically detect changes that you make to the patch directory. "
14870 "If you <command role=\"hg-cmd\">hg pull</command>, manually edit, or <command "
14871 "role=\"hg-cmd\">hg update</command> changes to patches or the <filename role="
14872 "\"special\">series</filename> file, you will have to <command role=\"hg-cmd"
14873 "\">hg qpop <option role=\"hg-ext-mq-cmd-qpop-opt\">hg -a</option></command> "
14874 "and then <command role=\"hg-cmd\">hg qpush <option role=\"hg-ext-mq-cmd-qpush-"
14875 "opt\">hg -a</option></command> in the underlying repository to see those "
14876 "changes show up there. If you forget to do this, you can confuse MQ's idea "
14877 "of which patches are applied."
14878 msgstr ""
14880 #. type: Content of: <book><chapter><sect1><title>
14881 #: ../en/ch12-mq.xml:1113
14882 msgid "Third party tools for working with patches"
14883 msgstr "操作补丁的第三方工具"
14885 #. type: Content of: <book><chapter><sect1><para>
14886 #: ../en/ch12-mq.xml:1115
14887 msgid ""
14888 "Once you've been working with patches for a while, you'll find yourself "
14889 "hungry for tools that will help you to understand and manipulate the patches "
14890 "you're dealing with."
14891 msgstr ""
14893 #. type: Content of: <book><chapter><sect1><para>
14894 #: ../en/ch12-mq.xml:1119
14895 msgid ""
14896 "The <command>diffstat</command> command <citation>web:diffstat</citation> "
14897 "generates a histogram of the modifications made to each file in a patch. It "
14898 "provides a good way to <quote>get a sense of</quote> a patch&emdash;which "
14899 "files it affects, and how much change it introduces to each file and as a "
14900 "whole. (I find that it's a good idea to use <command>diffstat</command>'s "
14901 "<option role=\"cmd-opt-diffstat\">-p</option> option as a matter of course, "
14902 "as otherwise it will try to do clever things with prefixes of file names that "
14903 "inevitably confuse at least me.)"
14904 msgstr ""
14906 #. type: Content of: <book><chapter><sect1><para>
14907 #: ../en/ch12-mq.xml:1133
14908 msgid ""
14909 "The <literal role=\"package\">patchutils</literal> package <citation>web:"
14910 "patchutils</citation> is invaluable. It provides a set of small utilities "
14911 "that follow the <quote>Unix philosophy;</quote> each does one useful thing "
14912 "with a patch. The <literal role=\"package\">patchutils</literal> command I "
14913 "use most is <command>filterdiff</command>, which extracts subsets from a "
14914 "patch file. For example, given a patch that modifies hundreds of files "
14915 "across dozens of directories, a single invocation of <command>filterdiff</"
14916 "command> can generate a smaller patch that only touches files whose names "
14917 "match a particular glob pattern. See section <xref linkend=\"mq-collab.tips."
14918 "interdiff\"/> for another example."
14919 msgstr ""
14921 #. type: Content of: <book><chapter><sect1><title>
14922 #: ../en/ch12-mq.xml:1149
14923 msgid "Good ways to work with patches"
14924 msgstr "操作补丁的好习惯"
14926 #. type: Content of: <book><chapter><sect1><para>
14927 #: ../en/ch12-mq.xml:1151
14928 msgid ""
14929 "Whether you are working on a patch series to submit to a free software or "
14930 "open source project, or a series that you intend to treat as a sequence of "
14931 "regular changesets when you're done, you can use some simple techniques to "
14932 "keep your work well organised."
14933 msgstr ""
14935 #. type: Content of: <book><chapter><sect1><para>
14936 #: ../en/ch12-mq.xml:1157
14937 msgid ""
14938 "Give your patches descriptive names. A good name for a patch might be "
14939 "<filename>rework-device-alloc.patch</filename>, because it will immediately "
14940 "give you a hint what the purpose of the patch is. Long names shouldn't be a "
14941 "problem; you won't be typing the names often, but you <emphasis>will</"
14942 "emphasis> be running commands like <command role=\"hg-ext-mq\">qapplied</"
14943 "command> and <command role=\"hg-ext-mq\">qtop</command> over and over. Good "
14944 "naming becomes especially important when you have a number of patches to work "
14945 "with, or if you are juggling a number of different tasks and your patches "
14946 "only get a fraction of your attention."
14947 msgstr ""
14949 #. type: Content of: <book><chapter><sect1><para>
14950 #: ../en/ch12-mq.xml:1169
14951 msgid ""
14952 "Be aware of what patch you're working on. Use the <command role=\"hg-ext-mq"
14953 "\">qtop</command> command and skim over the text of your patches "
14954 "frequently&emdash;for example, using <command role=\"hg-cmd\">hg tip <option "
14955 "role=\"hg-opt-tip\">-p</option></command>)&emdash;to be sure of where you "
14956 "stand. I have several times worked on and <command role=\"hg-ext-mq"
14957 "\">qrefresh</command>ed a patch other than the one I intended, and it's often "
14958 "tricky to migrate changes into the right patch after making them in the wrong "
14959 "one."
14960 msgstr ""
14962 #. type: Content of: <book><chapter><sect1><para>
14963 #: ../en/ch12-mq.xml:1179
14964 msgid ""
14965 "For this reason, it is very much worth investing a little time to learn how "
14966 "to use some of the third-party tools I described in section <xref linkend="
14967 "\"sec.mq.tools\"/>, particularly <command>diffstat</command> and "
14968 "<command>filterdiff</command>. The former will give you a quick idea of what "
14969 "changes your patch is making, while the latter makes it easy to splice hunks "
14970 "selectively out of one patch and into another."
14971 msgstr ""
14973 #. type: Content of: <book><chapter><sect1><title>
14974 #: ../en/ch12-mq.xml:1190
14975 msgid "MQ cookbook"
14976 msgstr "MQ 手册"
14978 #. type: Content of: <book><chapter><sect1><sect2><title>
14979 #: ../en/ch12-mq.xml:1193
14980 msgid "Manage <quote>trivial</quote> patches"
14981 msgstr "管理<quote>琐碎的</quote>补丁"
14983 #. type: Content of: <book><chapter><sect1><sect2><para>
14984 #: ../en/ch12-mq.xml:1195
14985 msgid ""
14986 "Because the overhead of dropping files into a new Mercurial repository is so "
14987 "low, it makes a lot of sense to manage patches this way even if you simply "
14988 "want to make a few changes to a source tarball that you downloaded."
14989 msgstr ""
14991 #
14992 #. type: Content of: <book><chapter><sect1><sect2><para>
14993 #: ../en/ch12-mq.xml:1200
14994 msgid ""
14995 "Begin by downloading and unpacking the source tarball, and turning it into a "
14996 "Mercurial repository."
14997 msgstr ""
14999 #. type: Content of: <book><chapter><sect1><sect2><para>
15000 #: ../en/ch12-mq.xml:1205
15001 msgid "Continue by creating a patch stack and making your changes."
15002 msgstr ""
15004 #. type: Content of: <book><chapter><sect1><sect2><para>
15005 #: ../en/ch12-mq.xml:1210
15006 msgid ""
15007 "Let's say a few weeks or months pass, and your package author releases a new "
15008 "version. First, bring their changes into the repository."
15009 msgstr ""
15011 #. type: Content of: <book><chapter><sect1><sect2><para>
15012 #: ../en/ch12-mq.xml:1216
15013 msgid ""
15014 "The pipeline starting with <command role=\"hg-cmd\">hg locate</command> above "
15015 "deletes all files in the working directory, so that <command role=\"hg-cmd"
15016 "\">hg commit</command>'s <option role=\"hg-opt-commit\">--addremove</option> "
15017 "option can actually tell which files have really been removed in the newer "
15018 "version of the source."
15019 msgstr ""
15021 #. type: Content of: <book><chapter><sect1><sect2><para>
15022 #: ../en/ch12-mq.xml:1224
15023 msgid "Finally, you can apply your patches on top of the new tree."
15024 msgstr ""
15026 #. type: Content of: <book><chapter><sect1><sect2><title>
15027 #: ../en/ch12-mq.xml:1231
15028 msgid "Combining entire patches"
15029 msgstr "组合全部的补丁"
15031 #. type: Content of: <book><chapter><sect1><sect2><para>
15032 #: ../en/ch12-mq.xml:1233
15033 msgid ""
15034 "MQ provides a command, <command role=\"hg-ext-mq\">qfold</command> that lets "
15035 "you combine entire patches. This <quote>folds</quote> the patches you name, "
15036 "in the order you name them, into the topmost applied patch, and concatenates "
15037 "their descriptions onto the end of its description. The patches that you "
15038 "fold must be unapplied before you fold them."
15039 msgstr ""
15041 #. type: Content of: <book><chapter><sect1><sect2><para>
15042 #: ../en/ch12-mq.xml:1241
15043 msgid ""
15044 "The order in which you fold patches matters. If your topmost applied patch "
15045 "is <literal>foo</literal>, and you <command role=\"hg-ext-mq\">qfold</"
15046 "command> <literal>bar</literal> and <literal>quux</literal> into it, you will "
15047 "end up with a patch that has the same effect as if you applied first "
15048 "<literal>foo</literal>, then <literal>bar</literal>, followed by "
15049 "<literal>quux</literal>."
15050 msgstr ""
15052 #. type: Content of: <book><chapter><sect1><sect2><title>
15053 #: ../en/ch12-mq.xml:1252
15054 msgid "Merging part of one patch into another"
15055 msgstr "合并补丁的部分内容到其它补丁"
15057 #. type: Content of: <book><chapter><sect1><sect2><para>
15058 #: ../en/ch12-mq.xml:1254
15059 msgid ""
15060 "Merging <emphasis>part</emphasis> of one patch into another is more difficult "
15061 "than combining entire patches."
15062 msgstr ""
15064 #. type: Content of: <book><chapter><sect1><sect2><para>
15065 #: ../en/ch12-mq.xml:1258
15066 msgid ""
15067 "If you want to move changes to entire files, you can use <command>filterdiff</"
15068 "command>'s <option role=\"cmd-opt-filterdiff\">-i</option> and <option role="
15069 "\"cmd-opt-filterdiff\">-x</option> options to choose the modifications to "
15070 "snip out of one patch, concatenating its output onto the end of the patch you "
15071 "want to merge into. You usually won't need to modify the patch you've merged "
15072 "the changes from. Instead, MQ will report some rejected hunks when you "
15073 "<command role=\"hg-ext-mq\">qpush</command> it (from the hunks you moved into "
15074 "the other patch), and you can simply <command role=\"hg-ext-mq\">qrefresh</"
15075 "command> the patch to drop the duplicate hunks."
15076 msgstr ""
15078 #. type: Content of: <book><chapter><sect1><sect2><para>
15079 #: ../en/ch12-mq.xml:1271
15080 msgid ""
15081 "If you have a patch that has multiple hunks modifying a file, and you only "
15082 "want to move a few of those hunks, the job becomes more messy, but you can "
15083 "still partly automate it. Use <command>lsdiff -nvv</command> to print some "
15084 "metadata about the patch."
15085 msgstr ""
15087 #. type: Content of: <book><chapter><sect1><sect2><para>
15088 #: ../en/ch12-mq.xml:1279
15089 msgid "This command prints three different kinds of number:"
15090 msgstr ""
15092 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
15093 #: ../en/ch12-mq.xml:1282
15094 msgid ""
15095 "(in the first column) a <emphasis>file number</emphasis> to identify each "
15096 "file modified in the patch;"
15097 msgstr ""
15099 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
15100 #: ../en/ch12-mq.xml:1286
15101 msgid ""
15102 "(on the next line, indented) the line number within a modified file where a "
15103 "hunk starts; and"
15104 msgstr ""
15106 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
15107 #: ../en/ch12-mq.xml:1289
15108 msgid ""
15109 "(on the same line) a <emphasis>hunk number</emphasis> to identify that hunk."
15110 msgstr ""
15112 #. type: Content of: <book><chapter><sect1><sect2><para>
15113 #: ../en/ch12-mq.xml:1293
15114 msgid ""
15115 "You'll have to use some visual inspection, and reading of the patch, to "
15116 "identify the file and hunk numbers you'll want, but you can then pass them to "
15117 "to <command>filterdiff</command>'s <option role=\"cmd-opt-filterdiff\">--"
15118 "files</option> and <option role=\"cmd-opt-filterdiff\">--hunks</option> "
15119 "options, to select exactly the file and hunk you want to extract."
15120 msgstr ""
15122 #. type: Content of: <book><chapter><sect1><sect2><para>
15123 #: ../en/ch12-mq.xml:1301
15124 msgid ""
15125 "Once you have this hunk, you can concatenate it onto the end of your "
15126 "destination patch and continue with the remainder of section <xref linkend="
15127 "\"sec.mq.combine\"/>."
15128 msgstr ""
15130 #. type: Content of: <book><chapter><sect1><title>
15131 #: ../en/ch12-mq.xml:1308
15132 msgid "Differences between quilt and MQ"
15133 msgstr "MQ 与 quilt 的区别"
15135 #. type: Content of: <book><chapter><sect1><para>
15136 #: ../en/ch12-mq.xml:1310
15137 msgid ""
15138 "If you are already familiar with quilt, MQ provides a similar command set. "
15139 "There are a few differences in the way that it works."
15140 msgstr ""
15142 #. type: Content of: <book><chapter><sect1><para>
15143 #: ../en/ch12-mq.xml:1314
15144 msgid ""
15145 "You will already have noticed that most quilt commands have MQ counterparts "
15146 "that simply begin with a <quote><literal>q</literal></quote>. The exceptions "
15147 "are quilt's <literal>add</literal> and <literal>remove</literal> commands, "
15148 "the counterparts for which are the normal Mercurial <command role=\"hg-cmd"
15149 "\">hg add</command> and <command role=\"hg-cmd\">hg remove</command> "
15150 "commands. There is no MQ equivalent of the quilt <literal>edit</literal> "
15151 "command."
15152 msgstr ""
15154 #. type: Content of: <book><chapter><title>
15155 #: ../en/ch13-mq-collab.xml:5
15156 msgid "Advanced uses of Mercurial Queues"
15157 msgstr "MQ 的高级用法"
15159 #. type: Content of: <book><chapter><para>
15160 #: ../en/ch13-mq-collab.xml:7
15161 msgid ""
15162 "While it's easy to pick up straightforward uses of Mercurial Queues, use of a "
15163 "little discipline and some of MQ's less frequently used capabilities makes it "
15164 "possible to work in complicated development environments."
15165 msgstr ""
15167 #. type: Content of: <book><chapter><para>
15168 #: ../en/ch13-mq-collab.xml:12
15169 msgid ""
15170 "In this chapter, I will use as an example a technique I have used to manage "
15171 "the development of an Infiniband device driver for the Linux kernel. The "
15172 "driver in question is large (at least as drivers go), with 25,000 lines of "
15173 "code spread across 35 source files. It is maintained by a small team of "
15174 "developers."
15175 msgstr ""
15177 #. type: Content of: <book><chapter><para>
15178 #: ../en/ch13-mq-collab.xml:18
15179 msgid ""
15180 "While much of the material in this chapter is specific to Linux, the same "
15181 "principles apply to any code base for which you're not the primary owner, and "
15182 "upon which you need to do a lot of development."
15183 msgstr ""
15185 #. type: Content of: <book><chapter><sect1><title>
15186 #: ../en/ch13-mq-collab.xml:24
15187 msgid "The problem of many targets"
15188 msgstr "多个目标的问题"
15190 #. type: Content of: <book><chapter><sect1><para>
15191 #: ../en/ch13-mq-collab.xml:26
15192 msgid ""
15193 "The Linux kernel changes rapidly, and has never been internally stable; "
15194 "developers frequently make drastic changes between releases. This means that "
15195 "a version of the driver that works well with a particular released version of "
15196 "the kernel will not even <emphasis>compile</emphasis> correctly against, "
15197 "typically, any other version."
15198 msgstr ""
15200 #. type: Content of: <book><chapter><sect1><para>
15201 #: ../en/ch13-mq-collab.xml:33
15202 msgid ""
15203 "To maintain a driver, we have to keep a number of distinct versions of Linux "
15204 "in mind."
15205 msgstr ""
15207 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15208 #: ../en/ch13-mq-collab.xml:36
15209 msgid ""
15210 "One target is the main Linux kernel development tree. Maintenance of the code "
15211 "is in this case partly shared by other developers in the kernel community, "
15212 "who make <quote>drive-by</quote> modifications to the driver as they develop "
15213 "and refine kernel subsystems."
15214 msgstr ""
15216 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15217 #: ../en/ch13-mq-collab.xml:42
15218 msgid ""
15219 "We also maintain a number of <quote>backports</quote> to older versions of "
15220 "the Linux kernel, to support the needs of customers who are running older "
15221 "Linux distributions that do not incorporate our drivers. (To "
15222 "<emphasis>backport</emphasis> a piece of code is to modify it to work in an "
15223 "older version of its target environment than the version it was developed "
15224 "for.)"
15225 msgstr ""
15227 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15228 #: ../en/ch13-mq-collab.xml:50
15229 msgid ""
15230 "Finally, we make software releases on a schedule that is necessarily not "
15231 "aligned with those used by Linux distributors and kernel developers, so that "
15232 "we can deliver new features to customers without forcing them to upgrade "
15233 "their entire kernels or distributions."
15234 msgstr ""
15236 #. type: Content of: <book><chapter><sect1><sect2><title>
15237 #: ../en/ch13-mq-collab.xml:58
15238 msgid "Tempting approaches that don't work well"
15239 msgstr "工作不好的诱人方法"
15241 #. type: Content of: <book><chapter><sect1><sect2><para>
15242 #: ../en/ch13-mq-collab.xml:60
15243 msgid ""
15244 "There are two <quote>standard</quote> ways to maintain a piece of software "
15245 "that has to target many different environments."
15246 msgstr ""
15248 #. type: Content of: <book><chapter><sect1><sect2><para>
15249 #: ../en/ch13-mq-collab.xml:64
15250 msgid ""
15251 "The first is to maintain a number of branches, each intended for a single "
15252 "target. The trouble with this approach is that you must maintain iron "
15253 "discipline in the flow of changes between repositories. A new feature or bug "
15254 "fix must start life in a <quote>pristine</quote> repository, then percolate "
15255 "out to every backport repository. Backport changes are more limited in the "
15256 "branches they should propagate to; a backport change that is applied to a "
15257 "branch where it doesn't belong will probably stop the driver from compiling."
15258 msgstr ""
15260 #. type: Content of: <book><chapter><sect1><sect2><para>
15261 #: ../en/ch13-mq-collab.xml:74
15262 msgid ""
15263 "The second is to maintain a single source tree filled with conditional "
15264 "statements that turn chunks of code on or off depending on the intended "
15265 "target. Because these <quote>ifdefs</quote> are not allowed in the Linux "
15266 "kernel tree, a manual or automatic process must be followed to strip them out "
15267 "and yield a clean tree. A code base maintained in this fashion rapidly "
15268 "becomes a rat's nest of conditional blocks that are difficult to understand "
15269 "and maintain."
15270 msgstr ""
15272 #. type: Content of: <book><chapter><sect1><sect2><para>
15273 #: ../en/ch13-mq-collab.xml:83
15274 msgid ""
15275 "Neither of these approaches is well suited to a situation where you don't "
15276 "<quote>own</quote> the canonical copy of a source tree. In the case of a "
15277 "Linux driver that is distributed with the standard kernel, Linus's tree "
15278 "contains the copy of the code that will be treated by the world as "
15279 "canonical. The upstream version of <quote>my</quote> driver can be modified "
15280 "by people I don't know, without me even finding out about it until after the "
15281 "changes show up in Linus's tree."
15282 msgstr ""
15284 #. type: Content of: <book><chapter><sect1><sect2><para>
15285 #: ../en/ch13-mq-collab.xml:93
15286 msgid ""
15287 "These approaches have the added weakness of making it difficult to generate "
15288 "well-formed patches to submit upstream."
15289 msgstr ""
15291 #. type: Content of: <book><chapter><sect1><sect2><para>
15292 #: ../en/ch13-mq-collab.xml:97
15293 msgid ""
15294 "In principle, Mercurial Queues seems like a good candidate to manage a "
15295 "development scenario such as the above. While this is indeed the case, MQ "
15296 "contains a few added features that make the job more pleasant."
15297 msgstr ""
15299 #. type: Content of: <book><chapter><sect1><title>
15300 #: ../en/ch13-mq-collab.xml:105
15301 msgid "Conditionally applying patches with guards"
15302 msgstr "有条件的应用补丁"
15304 #. type: Content of: <book><chapter><sect1><para>
15305 #: ../en/ch13-mq-collab.xml:107
15306 msgid ""
15307 "Perhaps the best way to maintain sanity with so many targets is to be able to "
15308 "choose specific patches to apply for a given situation. MQ provides a "
15309 "feature called <quote>guards</quote> (which originates with quilt's "
15310 "<literal>guards</literal> command) that does just this. To start off, let's "
15311 "create a simple repository for experimenting in."
15312 msgstr ""
15314 #. type: Content of: <book><chapter><sect1><para>
15315 #: ../en/ch13-mq-collab.xml:116
15316 msgid ""
15317 "This gives us a tiny repository that contains two patches that don't have any "
15318 "dependencies on each other, because they touch different files."
15319 msgstr ""
15321 #. type: Content of: <book><chapter><sect1><para>
15322 #: ../en/ch13-mq-collab.xml:120
15323 msgid ""
15324 "The idea behind conditional application is that you can <quote>tag</quote> a "
15325 "patch with a <emphasis>guard</emphasis>, which is simply a text string of "
15326 "your choosing, then tell MQ to select specific guards to use when applying "
15327 "patches. MQ will then either apply, or skip over, a guarded patch, depending "
15328 "on the guards that you have selected."
15329 msgstr ""
15331 #. type: Content of: <book><chapter><sect1><para>
15332 #: ../en/ch13-mq-collab.xml:127
15333 msgid ""
15334 "A patch can have an arbitrary number of guards; each one is "
15335 "<emphasis>positive</emphasis> (<quote>apply this patch if this guard is "
15336 "selected</quote>) or <emphasis>negative</emphasis> (<quote>skip this patch if "
15337 "this guard is selected</quote>). A patch with no guards is always applied."
15338 msgstr ""
15340 #. type: Content of: <book><chapter><sect1><title>
15341 #: ../en/ch13-mq-collab.xml:135
15342 msgid "Controlling the guards on a patch"
15343 msgstr "控制补丁的应用条件"
15345 #. type: Content of: <book><chapter><sect1><para>
15346 #: ../en/ch13-mq-collab.xml:137
15347 msgid ""
15348 "The <command role=\"hg-ext-mq\">qguard</command> command lets you determine "
15349 "which guards should apply to a patch, or display the guards that are already "
15350 "in effect. Without any arguments, it displays the guards on the current "
15351 "topmost patch."
15352 msgstr ""
15354 #. type: Content of: <book><chapter><sect1><para>
15355 #: ../en/ch13-mq-collab.xml:144
15356 msgid ""
15357 "To set a positive guard on a patch, prefix the name of the guard with a "
15358 "<quote><literal>+</literal></quote>."
15359 msgstr ""
15361 #. type: Content of: <book><chapter><sect1><para>
15362 #: ../en/ch13-mq-collab.xml:149
15363 msgid ""
15364 "To set a negative guard on a patch, prefix the name of the guard with a "
15365 "<quote><literal>-</literal></quote>."
15366 msgstr ""
15368 #. type: Content of: <book><chapter><sect1><note><para>
15369 #: ../en/ch13-mq-collab.xml:156
15370 msgid ""
15371 "The <command role=\"hg-ext-mq\">qguard</command> command <emphasis>sets</"
15372 "emphasis> the guards on a patch; it doesn't <emphasis>modify</emphasis> "
15373 "them. What this means is that if you run <command role=\"hg-cmd\">hg qguard "
15374 "+a +b</command> on a patch, then <command role=\"hg-cmd\">hg qguard +c</"
15375 "command> on the same patch, the <emphasis>only</emphasis> guard that will be "
15376 "set on it afterwards is <literal>+c</literal>."
15377 msgstr ""
15379 #
15380 #. type: Content of: <book><chapter><sect1><para>
15381 #: ../en/ch13-mq-collab.xml:165
15382 msgid ""
15383 "Mercurial stores guards in the <filename role=\"special\">series</filename> "
15384 "file; the form in which they are stored is easy both to understand and to "
15385 "edit by hand. (In other words, you don't have to use the <command role=\"hg-"
15386 "ext-mq\">qguard</command> command if you don't want to; it's okay to simply "
15387 "edit the <filename role=\"special\">series</filename> file.)"
15388 msgstr ""
15390 #. type: Content of: <book><chapter><sect1><title>
15391 #: ../en/ch13-mq-collab.xml:177
15392 msgid "Selecting the guards to use"
15393 msgstr "选择使用的条件"
15395 #. type: Content of: <book><chapter><sect1><para>
15396 #: ../en/ch13-mq-collab.xml:179
15397 msgid ""
15398 "The <command role=\"hg-ext-mq\">qselect</command> command determines which "
15399 "guards are active at a given time. The effect of this is to determine which "
15400 "patches MQ will apply the next time you run <command role=\"hg-ext-mq"
15401 "\">qpush</command>. It has no other effect; in particular, it doesn't do "
15402 "anything to patches that are already applied."
15403 msgstr ""
15405 #. type: Content of: <book><chapter><sect1><para>
15406 #: ../en/ch13-mq-collab.xml:186
15407 msgid ""
15408 "With no arguments, the <command role=\"hg-ext-mq\">qselect</command> command "
15409 "lists the guards currently in effect, one per line of output. Each argument "
15410 "is treated as the name of a guard to apply."
15411 msgstr ""
15413 #. type: Content of: <book><chapter><sect1><para>
15414 #: ../en/ch13-mq-collab.xml:193
15415 msgid ""
15416 "In case you're interested, the currently selected guards are stored in the "
15417 "<filename role=\"special\">guards</filename> file."
15418 msgstr ""
15420 #. type: Content of: <book><chapter><sect1><para>
15421 #: ../en/ch13-mq-collab.xml:198
15422 msgid ""
15423 "We can see the effect the selected guards have when we run <command role=\"hg-"
15424 "ext-mq\">qpush</command>."
15425 msgstr ""
15427 #. type: Content of: <book><chapter><sect1><para>
15428 #: ../en/ch13-mq-collab.xml:203
15429 msgid ""
15430 "A guard cannot start with a <quote><literal>+</literal></quote> or "
15431 "<quote><literal>-</literal></quote> character. The name of a guard must not "
15432 "contain white space, but most other characters are acceptable. If you try to "
15433 "use a guard with an invalid name, MQ will complain:"
15434 msgstr ""
15436 #. type: Content of: <book><chapter><sect1><para>
15437 #: ../en/ch13-mq-collab.xml:212
15438 msgid "Changing the selected guards changes the patches that are applied."
15439 msgstr ""
15441 #. type: Content of: <book><chapter><sect1><para>
15442 #: ../en/ch13-mq-collab.xml:217
15443 msgid ""
15444 "You can see in the example below that negative guards take precedence over "
15445 "positive guards."
15446 msgstr ""
15448 #. type: Content of: <book><chapter><sect1><title>
15449 #: ../en/ch13-mq-collab.xml:224
15450 msgid "MQ's rules for applying patches"
15451 msgstr "MQ 应用补丁的规则"
15453 #. type: Content of: <book><chapter><sect1><para>
15454 #: ../en/ch13-mq-collab.xml:226
15455 msgid ""
15456 "The rules that MQ uses when deciding whether to apply a patch are as follows."
15457 msgstr ""
15459 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15460 #: ../en/ch13-mq-collab.xml:229
15461 msgid "A patch that has no guards is always applied."
15462 msgstr ""
15464 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15465 #: ../en/ch13-mq-collab.xml:232
15466 msgid ""
15467 "If the patch has any negative guard that matches any currently selected "
15468 "guard, the patch is skipped."
15469 msgstr ""
15471 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15472 #: ../en/ch13-mq-collab.xml:235
15473 msgid ""
15474 "If the patch has any positive guard that matches any currently selected "
15475 "guard, the patch is applied."
15476 msgstr ""
15478 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15479 #: ../en/ch13-mq-collab.xml:238
15480 msgid ""
15481 "If the patch has positive or negative guards, but none matches any currently "
15482 "selected guard, the patch is skipped."
15483 msgstr ""
15485 #. type: Content of: <book><chapter><sect1><title>
15486 #: ../en/ch13-mq-collab.xml:245
15487 msgid "Trimming the work environment"
15488 msgstr "修剪工作环境"
15490 #. type: Content of: <book><chapter><sect1><para>
15491 #: ../en/ch13-mq-collab.xml:247
15492 msgid ""
15493 "In working on the device driver I mentioned earlier, I don't apply the "
15494 "patches to a normal Linux kernel tree. Instead, I use a repository that "
15495 "contains only a snapshot of the source files and headers that are relevant to "
15496 "Infiniband development. This repository is 1% the size of a kernel "
15497 "repository, so it's easier to work with."
15498 msgstr ""
15500 #. type: Content of: <book><chapter><sect1><para>
15501 #: ../en/ch13-mq-collab.xml:254
15502 msgid ""
15503 "I then choose a <quote>base</quote> version on top of which the patches are "
15504 "applied. This is a snapshot of the Linux kernel tree as of a revision of my "
15505 "choosing. When I take the snapshot, I record the changeset ID from the "
15506 "kernel repository in the commit message. Since the snapshot preserves the "
15507 "<quote>shape</quote> and content of the relevant parts of the kernel tree, I "
15508 "can apply my patches on top of either my tiny repository or a normal kernel "
15509 "tree."
15510 msgstr ""
15512 #. type: Content of: <book><chapter><sect1><para>
15513 #: ../en/ch13-mq-collab.xml:263
15514 msgid ""
15515 "Normally, the base tree atop which the patches apply should be a snapshot of "
15516 "a very recent upstream tree. This best facilitates the development of "
15517 "patches that can easily be submitted upstream with few or no modifications."
15518 msgstr ""
15520 #. type: Content of: <book><chapter><sect1><title>
15521 #: ../en/ch13-mq-collab.xml:270
15522 msgid "Dividing up the <filename role=\"special\">series</filename> file"
15523 msgstr "分类补丁<filename role=\"special\">系列</filename>"
15525 #. type: Content of: <book><chapter><sect1><para>
15526 #: ../en/ch13-mq-collab.xml:273
15527 msgid ""
15528 "I categorise the patches in the <filename role=\"special\">series</filename> "
15529 "file into a number of logical groups. Each section of like patches begins "
15530 "with a block of comments that describes the purpose of the patches that "
15531 "follow."
15532 msgstr ""
15534 #. type: Content of: <book><chapter><sect1><para>
15535 #: ../en/ch13-mq-collab.xml:279
15536 msgid ""
15537 "The sequence of patch groups that I maintain follows. The ordering of these "
15538 "groups is important; I'll describe why after I introduce the groups."
15539 msgstr ""
15541 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15542 #: ../en/ch13-mq-collab.xml:283
15543 msgid ""
15544 "The <quote>accepted</quote> group. Patches that the development team has "
15545 "submitted to the maintainer of the Infiniband subsystem, and which he has "
15546 "accepted, but which are not present in the snapshot that the tiny repository "
15547 "is based on. These are <quote>read only</quote> patches, present only to "
15548 "transform the tree into a similar state as it is in the upstream maintainer's "
15549 "repository."
15550 msgstr ""
15552 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15553 #: ../en/ch13-mq-collab.xml:291
15554 msgid ""
15555 "The <quote>rework</quote> group. Patches that I have submitted, but that the "
15556 "upstream maintainer has requested modifications to before he will accept them."
15557 msgstr ""
15559 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15560 #: ../en/ch13-mq-collab.xml:296
15561 msgid ""
15562 "The <quote>pending</quote> group. Patches that I have not yet submitted to "
15563 "the upstream maintainer, but which we have finished working on. These will be "
15564 "<quote>read only</quote> for a while. If the upstream maintainer accepts "
15565 "them upon submission, I'll move them to the end of the <quote>accepted</"
15566 "quote> group. If he requests that I modify any, I'll move them to the "
15567 "beginning of the <quote>rework</quote> group."
15568 msgstr ""
15570 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15571 #: ../en/ch13-mq-collab.xml:305
15572 msgid ""
15573 "The <quote>in progress</quote> group. Patches that are actively being "
15574 "developed, and should not be submitted anywhere yet."
15575 msgstr ""
15577 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15578 #: ../en/ch13-mq-collab.xml:309
15579 msgid ""
15580 "The <quote>backport</quote> group. Patches that adapt the source tree to "
15581 "older versions of the kernel tree."
15582 msgstr ""
15584 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15585 #: ../en/ch13-mq-collab.xml:313
15586 msgid ""
15587 "The <quote>do not ship</quote> group. Patches that for some reason should "
15588 "never be submitted upstream. For example, one such patch might change "
15589 "embedded driver identification strings to make it easier to distinguish, in "
15590 "the field, between an out-of-tree version of the driver and a version shipped "
15591 "by a distribution vendor."
15592 msgstr ""
15594 #. type: Content of: <book><chapter><sect1><para>
15595 #: ../en/ch13-mq-collab.xml:321
15596 msgid ""
15597 "Now to return to the reasons for ordering groups of patches in this way. We "
15598 "would like the lowest patches in the stack to be as stable as possible, so "
15599 "that we will not need to rework higher patches due to changes in context. "
15600 "Putting patches that will never be changed first in the <filename role="
15601 "\"special\">series</filename> file serves this purpose."
15602 msgstr ""
15604 #. type: Content of: <book><chapter><sect1><para>
15605 #: ../en/ch13-mq-collab.xml:329
15606 msgid ""
15607 "We would also like the patches that we know we'll need to modify to be "
15608 "applied on top of a source tree that resembles the upstream tree as closely "
15609 "as possible. This is why we keep accepted patches around for a while."
15610 msgstr ""
15612 #. type: Content of: <book><chapter><sect1><para>
15613 #: ../en/ch13-mq-collab.xml:334
15614 msgid ""
15615 "The <quote>backport</quote> and <quote>do not ship</quote> patches float at "
15616 "the end of the <filename role=\"special\">series</filename> file. The "
15617 "backport patches must be applied on top of all other patches, and the "
15618 "<quote>do not ship</quote> patches might as well stay out of harm's way."
15619 msgstr ""
15621 #. type: Content of: <book><chapter><sect1><title>
15622 #: ../en/ch13-mq-collab.xml:343
15623 msgid "Maintaining the patch series"
15624 msgstr "维护补丁系列"
15626 #. type: Content of: <book><chapter><sect1><para>
15627 #: ../en/ch13-mq-collab.xml:345
15628 msgid ""
15629 "In my work, I use a number of guards to control which patches are to be "
15630 "applied."
15631 msgstr ""
15633 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15634 #: ../en/ch13-mq-collab.xml:349
15635 msgid ""
15636 "<quote>Accepted</quote> patches are guarded with <literal>accepted</"
15637 "literal>. I enable this guard most of the time. When I'm applying the "
15638 "patches on top of a tree where the patches are already present, I can turn "
15639 "this patch off, and the patches that follow it will apply cleanly."
15640 msgstr ""
15642 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15643 #: ../en/ch13-mq-collab.xml:356
15644 msgid ""
15645 "Patches that are <quote>finished</quote>, but not yet submitted, have no "
15646 "guards. If I'm applying the patch stack to a copy of the upstream tree, I "
15647 "don't need to enable any guards in order to get a reasonably safe source tree."
15648 msgstr ""
15650 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15651 #: ../en/ch13-mq-collab.xml:362
15652 msgid ""
15653 "Those patches that need reworking before being resubmitted are guarded with "
15654 "<literal>rework</literal>."
15655 msgstr ""
15657 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15658 #: ../en/ch13-mq-collab.xml:366
15659 msgid ""
15660 "For those patches that are still under development, I use <literal>devel</"
15661 "literal>."
15662 msgstr ""
15664 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
15665 #: ../en/ch13-mq-collab.xml:369
15666 msgid ""
15667 "A backport patch may have several guards, one for each version of the kernel "
15668 "to which it applies. For example, a patch that backports a piece of code to "
15669 "2.6.9 will have a <literal>2.6.9</literal> guard."
15670 msgstr ""
15672 #. type: Content of: <book><chapter><sect1><para>
15673 #: ../en/ch13-mq-collab.xml:374
15674 msgid ""
15675 "This variety of guards gives me considerable flexibility in determining what "
15676 "kind of source tree I want to end up with. For most situations, the "
15677 "selection of appropriate guards is automated during the build process, but I "
15678 "can manually tune the guards to use for less common circumstances."
15679 msgstr ""
15681 #. type: Content of: <book><chapter><sect1><sect2><title>
15682 #: ../en/ch13-mq-collab.xml:381
15683 msgid "The art of writing backport patches"
15684 msgstr "编写向后移植补丁的艺术"
15686 #. type: Content of: <book><chapter><sect1><sect2><para>
15687 #: ../en/ch13-mq-collab.xml:383
15688 msgid ""
15689 "Using MQ, writing a backport patch is a simple process. All such a patch has "
15690 "to do is modify a piece of code that uses a kernel feature not present in the "
15691 "older version of the kernel, so that the driver continues to work correctly "
15692 "under that older version."
15693 msgstr ""
15695 #. type: Content of: <book><chapter><sect1><sect2><para>
15696 #: ../en/ch13-mq-collab.xml:389
15697 msgid ""
15698 "A useful goal when writing a good backport patch is to make your code look as "
15699 "if it was written for the older version of the kernel you're targeting. The "
15700 "less obtrusive the patch, the easier it will be to understand and maintain. "
15701 "If you're writing a collection of backport patches to avoid the <quote>rat's "
15702 "nest</quote> effect of lots of <literal>#ifdef</literal>s (hunks of source "
15703 "code that are only used conditionally) in your code, don't introduce version-"
15704 "dependent <literal>#ifdef</literal>s into the patches. Instead, write "
15705 "several patches, each of which makes unconditional changes, and control their "
15706 "application using guards."
15707 msgstr ""
15709 #. type: Content of: <book><chapter><sect1><sect2><para>
15710 #: ../en/ch13-mq-collab.xml:402
15711 msgid ""
15712 "There are two reasons to divide backport patches into a distinct group, away "
15713 "from the <quote>regular</quote> patches whose effects they modify. The first "
15714 "is that intermingling the two makes it more difficult to use a tool like the "
15715 "<literal role=\"hg-ext\">patchbomb</literal> extension to automate the "
15716 "process of submitting the patches to an upstream maintainer. The second is "
15717 "that a backport patch could perturb the context in which a subsequent regular "
15718 "patch is applied, making it impossible to apply the regular patch cleanly "
15719 "<emphasis>without</emphasis> the earlier backport patch already being applied."
15720 msgstr ""
15722 #. type: Content of: <book><chapter><sect1><title>
15723 #: ../en/ch13-mq-collab.xml:417
15724 msgid "Useful tips for developing with MQ"
15725 msgstr "使用 MQ 开发的技巧"
15727 #. type: Content of: <book><chapter><sect1><sect2><title>
15728 #: ../en/ch13-mq-collab.xml:420
15729 msgid "Organising patches in directories"
15730 msgstr "将补丁放到几个目录中"
15732 #. type: Content of: <book><chapter><sect1><sect2><para>
15733 #: ../en/ch13-mq-collab.xml:422
15734 msgid ""
15735 "If you're working on a substantial project with MQ, it's not difficult to "
15736 "accumulate a large number of patches. For example, I have one patch "
15737 "repository that contains over 250 patches."
15738 msgstr ""
15740 #. type: Content of: <book><chapter><sect1><sect2><para>
15741 #: ../en/ch13-mq-collab.xml:427
15742 msgid ""
15743 "If you can group these patches into separate logical categories, you can if "
15744 "you like store them in different directories; MQ has no problems with patch "
15745 "names that contain path separators."
15746 msgstr ""
15748 #. type: Content of: <book><chapter><sect1><sect2><title>
15749 #: ../en/ch13-mq-collab.xml:434
15750 msgid "Viewing the history of a patch"
15751 msgstr "察看补丁的历史"
15753 #. type: Content of: <book><chapter><sect1><sect2><para>
15754 #: ../en/ch13-mq-collab.xml:436
15755 msgid ""
15756 "If you're developing a set of patches over a long time, it's a good idea to "
15757 "maintain them in a repository, as discussed in section <xref linkend=\"sec.mq."
15758 "repo\"/>. If you do so, you'll quickly discover that using the <command role="
15759 "\"hg-cmd\">hg diff</command> command to look at the history of changes to a "
15760 "patch is unworkable. This is in part because you're looking at the second "
15761 "derivative of the real code (a diff of a diff), but also because MQ adds "
15762 "noise to the process by modifying time stamps and directory names when it "
15763 "updates a patch."
15764 msgstr ""
15766 #. type: Content of: <book><chapter><sect1><sect2><para>
15767 #: ../en/ch13-mq-collab.xml:448
15768 msgid ""
15769 "However, you can use the <literal role=\"hg-ext\">extdiff</literal> "
15770 "extension, which is bundled with Mercurial, to turn a diff of two versions of "
15771 "a patch into something readable. To do this, you will need a third-party "
15772 "package called <literal role=\"package\">patchutils</literal> <citation>web:"
15773 "patchutils</citation>. This provides a command named <command>interdiff</"
15774 "command>, which shows the differences between two diffs as a diff. Used on "
15775 "two versions of the same diff, it generates a diff that represents the diff "
15776 "from the first to the second version."
15777 msgstr ""
15779 #. type: Content of: <book><chapter><sect1><sect2><para>
15780 #: ../en/ch13-mq-collab.xml:459
15781 msgid ""
15782 "You can enable the <literal role=\"hg-ext\">extdiff</literal> extension in "
15783 "the usual way, by adding a line to the <literal role=\"rc-extensions"
15784 "\">extensions</literal> section of your <filename role=\"special\"> /.hgrc</"
15785 "filename>."
15786 msgstr ""
15788 #
15789 #. &example.hg-interdiff;
15790 #. type: Content of: <book><chapter><sect1><sect2><para>
15791 #: ../en/ch13-mq-collab.xml:465
15792 msgid ""
15793 "The <command>interdiff</command> command expects to be passed the names of "
15794 "two files, but the <literal role=\"hg-ext\">extdiff</literal> extension "
15795 "passes the program it runs a pair of directories, each of which can contain "
15796 "an arbitrary number of files. We thus need a small program that will run "
15797 "<command>interdiff</command> on each pair of files in these two directories. "
15798 "This program is available as <filename role=\"special\">hg-interdiff</"
15799 "filename> in the <filename class=\"directory\">examples</filename> directory "
15800 "of the source code repository that accompanies this book."
15801 msgstr ""
15803 #. type: Content of: <book><chapter><sect1><sect2><para>
15804 #: ../en/ch13-mq-collab.xml:477
15805 msgid ""
15806 "With the <filename role=\"special\">hg-interdiff</filename> program in your "
15807 "shell's search path, you can run it as follows, from inside an MQ patch "
15808 "directory:"
15809 msgstr ""
15811 #. type: Content of: <book><chapter><sect1><sect2><para>
15812 #: ../en/ch13-mq-collab.xml:482
15813 msgid ""
15814 "Since you'll probably want to use this long-winded command a lot, you can get "
15815 "<literal role=\"hg-ext\">hgext</literal> to make it available as a normal "
15816 "Mercurial command, again by editing your <filename role=\"special\"> /.hgrc</"
15817 "filename>."
15818 msgstr ""
15820 #. type: Content of: <book><chapter><sect1><sect2><para>
15821 #: ../en/ch13-mq-collab.xml:489
15822 msgid ""
15823 "This directs <literal role=\"hg-ext\">hgext</literal> to make an "
15824 "<literal>interdiff</literal> command available, so you can now shorten the "
15825 "previous invocation of <command role=\"hg-ext-extdiff\">extdiff</command> to "
15826 "something a little more wieldy."
15827 msgstr ""
15829 #. type: Content of: <book><chapter><sect1><sect2><note><para>
15830 #: ../en/ch13-mq-collab.xml:498
15831 msgid ""
15832 "The <command>interdiff</command> command works well only if the underlying "
15833 "files against which versions of a patch are generated remain the same. If "
15834 "you create a patch, modify the underlying files, and then regenerate the "
15835 "patch, <command>interdiff</command> may not produce useful output."
15836 msgstr ""
15838 #. type: Content of: <book><chapter><sect1><sect2><para>
15839 #: ../en/ch13-mq-collab.xml:506
15840 msgid ""
15841 "The <literal role=\"hg-ext\">extdiff</literal> extension is useful for more "
15842 "than merely improving the presentation of MQ patches. To read more about it, "
15843 "go to section <xref linkend=\"sec.hgext.extdiff\"/>."
15844 msgstr ""
15846 #. type: Content of: <book><chapter><title>
15847 #: ../en/ch14-hgext.xml:5
15848 msgid "Adding functionality with extensions"
15849 msgstr "使用扩展增加功能"
15851 #. type: Content of: <book><chapter><para>
15852 #: ../en/ch14-hgext.xml:7
15853 msgid ""
15854 "While the core of Mercurial is quite complete from a functionality "
15855 "standpoint, it's deliberately shorn of fancy features. This approach of "
15856 "preserving simplicity keeps the software easy to deal with for both "
15857 "maintainers and users."
15858 msgstr ""
15860 #. type: Content of: <book><chapter><para>
15861 #: ../en/ch14-hgext.xml:12
15862 msgid ""
15863 "However, Mercurial doesn't box you in with an inflexible command set: you can "
15864 "add features to it as <emphasis>extensions</emphasis> (sometimes known as "
15865 "<emphasis>plugins</emphasis>). We've already discussed a few of these "
15866 "extensions in earlier chapters."
15867 msgstr ""
15869 #. type: Content of: <book><chapter><itemizedlist><listitem><para>
15870 #: ../en/ch14-hgext.xml:18
15871 msgid ""
15872 "Section <xref linkend=\"sec.tour-merge.fetch\"/> covers the <literal role="
15873 "\"hg-ext\">fetch</literal> extension; this combines pulling new changes and "
15874 "merging them with local changes into a single command, <command role=\"hg-ext-"
15875 "fetch\">fetch</command>."
15876 msgstr ""
15878 #. type: Content of: <book><chapter><itemizedlist><listitem><para>
15879 #: ../en/ch14-hgext.xml:24
15880 msgid ""
15881 "In chapter <xref linkend=\"chap.hook\"/>, we covered several extensions that "
15882 "are useful for hook-related functionality: <literal role=\"hg-ext\">acl</"
15883 "literal> adds access control lists; <literal role=\"hg-ext\">bugzilla</"
15884 "literal> adds integration with the Bugzilla bug tracking system; and <literal "
15885 "role=\"hg-ext\">notify</literal> sends notification emails on new changes."
15886 msgstr ""
15888 #. type: Content of: <book><chapter><itemizedlist><listitem><para>
15889 #: ../en/ch14-hgext.xml:33
15890 msgid ""
15891 "The Mercurial Queues patch management extension is so invaluable that it "
15892 "merits two chapters and an appendix all to itself. Chapter <xref linkend="
15893 "\"chap.mq\"/> covers the basics; chapter <xref linkend=\"chap.mq-collab\"/> "
15894 "discusses advanced topics; and appendix <xref linkend=\"chap.mqref\"/> goes "
15895 "into detail on each command."
15896 msgstr ""
15898 #. type: Content of: <book><chapter><para>
15899 #: ../en/ch14-hgext.xml:43
15900 msgid ""
15901 "In this chapter, we'll cover some of the other extensions that are available "
15902 "for Mercurial, and briefly touch on some of the machinery you'll need to know "
15903 "about if you want to write an extension of your own."
15904 msgstr ""
15906 #. type: Content of: <book><chapter><itemizedlist><listitem><para>
15907 #: ../en/ch14-hgext.xml:48
15908 msgid ""
15909 "In section <xref linkend=\"sec.hgext.inotify\"/>, we'll discuss the "
15910 "possibility of <emphasis>huge</emphasis> performance improvements using the "
15911 "<literal role=\"hg-ext\">inotify</literal> extension."
15912 msgstr ""
15914 #. type: Content of: <book><chapter><sect1><title>
15915 #: ../en/ch14-hgext.xml:55
15916 msgid ""
15917 "Improve performance with the <literal role=\"hg-ext\">inotify</literal> "
15918 "extension"
15919 msgstr "使用扩展 <literal role=\"hg-ext\">inotify</literal> 以提高性能"
15921 #. type: Content of: <book><chapter><sect1><para>
15922 #: ../en/ch14-hgext.xml:58
15923 msgid ""
15924 "Are you interested in having some of the most common Mercurial operations run "
15925 "as much as a hundred times faster? Read on!"
15926 msgstr ""
15928 #. type: Content of: <book><chapter><sect1><para>
15929 #: ../en/ch14-hgext.xml:62
15930 msgid ""
15931 "Mercurial has great performance under normal circumstances. For example, "
15932 "when you run the <command role=\"hg-cmd\">hg status</command> command, "
15933 "Mercurial has to scan almost every directory and file in your repository so "
15934 "that it can display file status. Many other Mercurial commands need to do "
15935 "the same work behind the scenes; for example, the <command role=\"hg-cmd\">hg "
15936 "diff</command> command uses the status machinery to avoid doing an expensive "
15937 "comparison operation on files that obviously haven't changed."
15938 msgstr ""
15940 #. type: Content of: <book><chapter><sect1><para>
15941 #: ../en/ch14-hgext.xml:72
15942 msgid ""
15943 "Because obtaining file status is crucial to good performance, the authors of "
15944 "Mercurial have optimised this code to within an inch of its life. However, "
15945 "there's no avoiding the fact that when you run <command role=\"hg-cmd\">hg "
15946 "status</command>, Mercurial is going to have to perform at least one "
15947 "expensive system call for each managed file to determine whether it's changed "
15948 "since the last time Mercurial checked. For a sufficiently large repository, "
15949 "this can take a long time."
15950 msgstr ""
15952 #. type: Content of: <book><chapter><sect1><para>
15953 #: ../en/ch14-hgext.xml:82
15954 msgid ""
15955 "To put a number on the magnitude of this effect, I created a repository "
15956 "containing 150,000 managed files. I timed <command role=\"hg-cmd\">hg "
15957 "status</command> as taking ten seconds to run, even when <emphasis>none</"
15958 "emphasis> of those files had been modified."
15959 msgstr ""
15961 #. type: Content of: <book><chapter><sect1><para>
15962 #: ../en/ch14-hgext.xml:88
15963 msgid ""
15964 "Many modern operating systems contain a file notification facility. If a "
15965 "program signs up to an appropriate service, the operating system will notify "
15966 "it every time a file of interest is created, modified, or deleted. On Linux "
15967 "systems, the kernel component that does this is called <literal>inotify</"
15968 "literal>."
15969 msgstr ""
15971 #. type: Content of: <book><chapter><sect1><para>
15972 #: ../en/ch14-hgext.xml:95
15973 msgid ""
15974 "Mercurial's <literal role=\"hg-ext\">inotify</literal> extension talks to the "
15975 "kernel's <literal>inotify</literal> component to optimise <command role=\"hg-"
15976 "cmd\">hg status</command> commands. The extension has two components. A "
15977 "daemon sits in the background and receives notifications from the "
15978 "<literal>inotify</literal> subsystem. It also listens for connections from a "
15979 "regular Mercurial command. The extension modifies Mercurial's behaviour so "
15980 "that instead of scanning the filesystem, it queries the daemon. Since the "
15981 "daemon has perfect information about the state of the repository, it can "
15982 "respond with a result instantaneously, avoiding the need to scan every "
15983 "directory and file in the repository."
15984 msgstr ""
15986 #. type: Content of: <book><chapter><sect1><para>
15987 #: ../en/ch14-hgext.xml:108
15988 msgid ""
15989 "Recall the ten seconds that I measured plain Mercurial as taking to run "
15990 "<command role=\"hg-cmd\">hg status</command> on a 150,000 file repository. "
15991 "With the <literal role=\"hg-ext\">inotify</literal> extension enabled, the "
15992 "time dropped to 0.1 seconds, a factor of <emphasis>one hundred</emphasis> "
15993 "faster."
15994 msgstr ""
15996 #. type: Content of: <book><chapter><sect1><para>
15997 #: ../en/ch14-hgext.xml:115
15998 msgid "Before we continue, please pay attention to some caveats."
15999 msgstr ""
16001 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
16002 #: ../en/ch14-hgext.xml:118
16003 msgid ""
16004 "The <literal role=\"hg-ext\">inotify</literal> extension is Linux-specific. "
16005 "Because it interfaces directly to the Linux kernel's <literal>inotify</"
16006 "literal> subsystem, it does not work on other operating systems."
16007 msgstr ""
16009 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
16010 #: ../en/ch14-hgext.xml:123
16011 msgid ""
16012 "It should work on any Linux distribution that was released after early 2005. "
16013 "Older distributions are likely to have a kernel that lacks <literal>inotify</"
16014 "literal>, or a version of <literal>glibc</literal> that does not have the "
16015 "necessary interfacing support."
16016 msgstr ""
16018 #. type: Content of: <book><chapter><sect1><itemizedlist><listitem><para>
16019 #: ../en/ch14-hgext.xml:130
16020 msgid ""
16021 "Not all filesystems are suitable for use with the <literal role=\"hg-ext"
16022 "\">inotify</literal> extension. Network filesystems such as NFS are a non-"
16023 "starter, for example, particularly if you're running Mercurial on several "
16024 "systems, all mounting the same network filesystem. The kernel's "
16025 "<literal>inotify</literal> system has no way of knowing about changes made on "
16026 "another system. Most local filesystems (e.g. ext3, XFS, ReiserFS) should "
16027 "work fine."
16028 msgstr ""
16030 #. type: Content of: <book><chapter><sect1><para>
16031 #: ../en/ch14-hgext.xml:141
16032 msgid ""
16033 "The <literal role=\"hg-ext\">inotify</literal> extension is not yet shipped "
16034 "with Mercurial as of May 2007, so it's a little more involved to set up than "
16035 "other extensions. But the performance improvement is worth it!"
16036 msgstr ""
16038 #. type: Content of: <book><chapter><sect1><para>
16039 #: ../en/ch14-hgext.xml:146
16040 msgid ""
16041 "The extension currently comes in two parts: a set of patches to the Mercurial "
16042 "source code, and a library of Python bindings to the <literal>inotify</"
16043 "literal> subsystem."
16044 msgstr ""
16046 #. type: Content of: <book><chapter><sect1><note><para>
16047 #: ../en/ch14-hgext.xml:150
16048 msgid ""
16049 "There are <emphasis>two</emphasis> Python <literal>inotify</literal> binding "
16050 "libraries. One of them is called <literal>pyinotify</literal>, and is "
16051 "packaged by some Linux distributions as <literal>python-inotify</literal>. "
16052 "This is <emphasis>not</emphasis> the one you'll need, as it is too buggy and "
16053 "inefficient to be practical."
16054 msgstr ""
16056 #. type: Content of: <book><chapter><sect1><para>
16057 #: ../en/ch14-hgext.xml:157
16058 msgid ""
16059 "To get going, it's best to already have a functioning copy of Mercurial "
16060 "installed."
16061 msgstr ""
16063 #. type: Content of: <book><chapter><sect1><note><para>
16064 #: ../en/ch14-hgext.xml:160
16065 msgid ""
16066 "If you follow the instructions below, you'll be <emphasis>replacing</"
16067 "emphasis> and overwriting any existing installation of Mercurial that you "
16068 "might already have, using the latest <quote>bleeding edge</quote> Mercurial "
16069 "code. Don't say you weren't warned!"
16070 msgstr ""
16072 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
16073 #: ../en/ch14-hgext.xml:167
16074 msgid ""
16075 "Clone the Python <literal>inotify</literal> binding repository. Build and "
16076 "install it."
16077 msgstr ""
16079 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
16080 #: ../en/ch14-hgext.xml:175
16081 msgid ""
16082 "Clone the <filename class=\"directory\">crew</filename> Mercurial "
16083 "repository. Clone the <literal role=\"hg-ext\">inotify</literal> patch "
16084 "repository so that Mercurial Queues will be able to apply patches to your "
16085 "cope of the <filename class=\"directory\">crew</filename> repository."
16086 msgstr ""
16088 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
16089 #: ../en/ch14-hgext.xml:188
16090 msgid ""
16091 "Make sure that you have the Mercurial Queues extension, <literal role=\"hg-ext"
16092 "\">mq</literal>, enabled. If you've never used MQ, read section <xref "
16093 "linkend=\"sec.mq.start\"/> to get started quickly."
16094 msgstr ""
16096 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
16097 #: ../en/ch14-hgext.xml:194
16098 msgid ""
16099 "Go into the <filename class=\"directory\">inotify</filename> repo, and apply "
16100 "all of the <literal role=\"hg-ext\">inotify</literal> patches using the "
16101 "<option role=\"hg-ext-mq-cmd-qpush-opt\">hg -a</option> option to the "
16102 "<command role=\"hg-ext-mq\">qpush</command> command."
16103 msgstr ""
16105 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
16106 #: ../en/ch14-hgext.xml:204
16107 msgid ""
16108 "If you get an error message from <command role=\"hg-ext-mq\">qpush</command>, "
16109 "you should not continue. Instead, ask for help."
16110 msgstr ""
16112 #. type: Content of: <book><chapter><sect1><orderedlist><listitem><para>
16113 #: ../en/ch14-hgext.xml:208
16114 msgid "Build and install the patched version of Mercurial."
16115 msgstr ""
16117 #. type: Content of: <book><chapter><sect1><para>
16118 #: ../en/ch14-hgext.xml:216
16119 msgid ""
16120 "Once you've build a suitably patched version of Mercurial, all you need to do "
16121 "to enable the <literal role=\"hg-ext\">inotify</literal> extension is add an "
16122 "entry to your <filename role=\"special\"> /.hgrc</filename>."
16123 msgstr ""
16125 #. type: Content of: <book><chapter><sect1><para>
16126 #: ../en/ch14-hgext.xml:221
16127 msgid ""
16128 "When the <literal role=\"hg-ext\">inotify</literal> extension is enabled, "
16129 "Mercurial will automatically and transparently start the status daemon the "
16130 "first time you run a command that needs status in a repository. It runs one "
16131 "status daemon per repository."
16132 msgstr ""
16134 #. type: Content of: <book><chapter><sect1><para>
16135 #: ../en/ch14-hgext.xml:227
16136 msgid ""
16137 "The status daemon is started silently, and runs in the background. If you "
16138 "look at a list of running processes after you've enabled the <literal role="
16139 "\"hg-ext\">inotify</literal> extension and run a few commands in different "
16140 "repositories, you'll thus see a few <literal>hg</literal> processes sitting "
16141 "around, waiting for updates from the kernel and queries from Mercurial."
16142 msgstr ""
16144 #. type: Content of: <book><chapter><sect1><para>
16145 #: ../en/ch14-hgext.xml:235
16146 msgid ""
16147 "The first time you run a Mercurial command in a repository when you have the "
16148 "<literal role=\"hg-ext\">inotify</literal> extension enabled, it will run "
16149 "with about the same performance as a normal Mercurial command. This is "
16150 "because the status daemon needs to perform a normal status scan so that it "
16151 "has a baseline against which to apply later updates from the kernel. "
16152 "However, <emphasis>every</emphasis> subsequent command that does any kind of "
16153 "status check should be noticeably faster on repositories of even fairly "
16154 "modest size. Better yet, the bigger your repository is, the greater a "
16155 "performance advantage you'll see. The <literal role=\"hg-ext\">inotify</"
16156 "literal> daemon makes status operations almost instantaneous on repositories "
16157 "of all sizes!"
16158 msgstr ""
16160 #. type: Content of: <book><chapter><sect1><para>
16161 #: ../en/ch14-hgext.xml:249
16162 msgid ""
16163 "If you like, you can manually start a status daemon using the <command role="
16164 "\"hg-ext-inotify\">inserve</command> command. This gives you slightly finer "
16165 "control over how the daemon ought to run. This command will of course only "
16166 "be available when the <literal role=\"hg-ext\">inotify</literal> extension is "
16167 "enabled."
16168 msgstr ""
16170 #. type: Content of: <book><chapter><sect1><para>
16171 #: ../en/ch14-hgext.xml:256
16172 msgid ""
16173 "When you're using the <literal role=\"hg-ext\">inotify</literal> extension, "
16174 "you should notice <emphasis>no difference at all</emphasis> in Mercurial's "
16175 "behaviour, with the sole exception of status-related commands running a whole "
16176 "lot faster than they used to. You should specifically expect that commands "
16177 "will not print different output; neither should they give different results. "
16178 "If either of these situations occurs, please report a bug."
16179 msgstr ""
16181 #. type: Content of: <book><chapter><sect1><title>
16182 #: ../en/ch14-hgext.xml:267
16183 msgid ""
16184 "Flexible diff support with the <literal role=\"hg-ext\">extdiff</literal> "
16185 "extension"
16186 msgstr "使用扩展 <literal role=\"hg-ext\">extdiff</literal> 以扩展差异支持"
16188 #. type: Content of: <book><chapter><sect1><para>
16189 #: ../en/ch14-hgext.xml:270
16190 msgid ""
16191 "Mercurial's built-in <command role=\"hg-cmd\">hg diff</command> command "
16192 "outputs plaintext unified diffs."
16193 msgstr ""
16194 "Mercurial 内置命令 <command role=\"hg-cmd\">hg diff</command> 的输出与统一差异"
16195 "不同。"
16197 #. type: Content of: <book><chapter><sect1><para>
16198 #: ../en/ch14-hgext.xml:275
16199 msgid ""
16200 "If you would like to use an external tool to display modifications, you'll "
16201 "want to use the <literal role=\"hg-ext\">extdiff</literal> extension. This "
16202 "will let you use, for example, a graphical diff tool."
16203 msgstr ""
16205 #. type: Content of: <book><chapter><sect1><para>
16206 #: ../en/ch14-hgext.xml:280
16207 msgid ""
16208 "The <literal role=\"hg-ext\">extdiff</literal> extension is bundled with "
16209 "Mercurial, so it's easy to set up. In the <literal role=\"rc-extensions"
16210 "\">extensions</literal> section of your <filename role=\"special\"> /.hgrc</"
16211 "filename>, simply add a one-line entry to enable the extension."
16212 msgstr ""
16214 #. type: Content of: <book><chapter><sect1><para>
16215 #: ../en/ch14-hgext.xml:286
16216 msgid ""
16217 "This introduces a command named <command role=\"hg-ext-extdiff\">extdiff</"
16218 "command>, which by default uses your system's <command>diff</command> command "
16219 "to generate a unified diff in the same form as the built-in <command role="
16220 "\"hg-cmd\">hg diff</command> command."
16221 msgstr ""
16223 #. type: Content of: <book><chapter><sect1><para>
16224 #: ../en/ch14-hgext.xml:294
16225 msgid ""
16226 "The result won't be exactly the same as with the built-in <command role=\"hg-"
16227 "cmd\">hg diff</command> variations, because the output of <command>diff</"
16228 "command> varies from one system to another, even when passed the same options."
16229 msgstr ""
16231 #. type: Content of: <book><chapter><sect1><para>
16232 #: ../en/ch14-hgext.xml:299
16233 msgid ""
16234 "As the <quote><literal>making snapshot</literal></quote> lines of output "
16235 "above imply, the <command role=\"hg-ext-extdiff\">extdiff</command> command "
16236 "works by creating two snapshots of your source tree. The first snapshot is "
16237 "of the source revision; the second, of the target revision or working "
16238 "directory. The <command role=\"hg-ext-extdiff\">extdiff</command> command "
16239 "generates these snapshots in a temporary directory, passes the name of each "
16240 "directory to an external diff viewer, then deletes the temporary directory. "
16241 "For efficiency, it only snapshots the directories and files that have changed "
16242 "between the two revisions."
16243 msgstr ""
16245 #. type: Content of: <book><chapter><sect1><para>
16246 #: ../en/ch14-hgext.xml:312
16247 msgid ""
16248 "Snapshot directory names have the same base name as your repository. If your "
16249 "repository path is <filename class=\"directory\">/quux/bar/foo</filename>, "
16250 "then <filename class=\"directory\">foo</filename> will be the name of each "
16251 "snapshot directory. Each snapshot directory name has its changeset ID "
16252 "appended, if appropriate. If a snapshot is of revision "
16253 "<literal>a631aca1083f</literal>, the directory will be named <filename class="
16254 "\"directory\">foo.a631aca1083f</filename>. A snapshot of the working "
16255 "directory won't have a changeset ID appended, so it would just be <filename "
16256 "class=\"directory\">foo</filename> in this example. To see what this looks "
16257 "like in practice, look again at the <command role=\"hg-ext-extdiff\">extdiff</"
16258 "command> example above. Notice that the diff has the snapshot directory "
16259 "names embedded in its header."
16260 msgstr ""
16262 #. type: Content of: <book><chapter><sect1><para>
16263 #: ../en/ch14-hgext.xml:328
16264 msgid ""
16265 "The <command role=\"hg-ext-extdiff\">extdiff</command> command accepts two "
16266 "important options. The <option role=\"hg-ext-extdiff-cmd-extdiff-opt\">hg -p</"
16267 "option> option lets you choose a program to view differences with, instead of "
16268 "<command>diff</command>. With the <option role=\"hg-ext-extdiff-cmd-extdiff-"
16269 "opt\">hg -o</option> option, you can change the options that <command role="
16270 "\"hg-ext-extdiff\">extdiff</command> passes to the program (by default, these "
16271 "options are <quote><literal>-Npru</literal></quote>, which only make sense if "
16272 "you're running <command>diff</command>). In other respects, the <command "
16273 "role=\"hg-ext-extdiff\">extdiff</command> command acts similarly to the built-"
16274 "in <command role=\"hg-cmd\">hg diff</command> command: you use the same "
16275 "option names, syntax, and arguments to specify the revisions you want, the "
16276 "files you want, and so on."
16277 msgstr ""
16279 #
16280 #. type: Content of: <book><chapter><sect1><para>
16281 #: ../en/ch14-hgext.xml:345
16282 msgid ""
16283 "As an example, here's how to run the normal system <command>diff</command> "
16284 "command, getting it to generate context diffs (using the <option role=\"cmd-"
16285 "opt-diff\">-c</option> option) instead of unified diffs, and five lines of "
16286 "context instead of the default three (passing <literal>5</literal> as the "
16287 "argument to the <option role=\"cmd-opt-diff\">-C</option> option)."
16288 msgstr ""
16290 #. type: Content of: <book><chapter><sect1><para>
16291 #: ../en/ch14-hgext.xml:354
16292 msgid ""
16293 "Launching a visual diff tool is just as easy. Here's how to launch the "
16294 "<command>kdiff3</command> viewer."
16295 msgstr ""
16297 #. type: Content of: <book><chapter><sect1><para>
16298 #: ../en/ch14-hgext.xml:358
16299 msgid ""
16300 "If your diff viewing command can't deal with directories, you can easily work "
16301 "around this with a little scripting. For an example of such scripting in "
16302 "action with the <literal role=\"hg-ext\">mq</literal> extension and the "
16303 "<command>interdiff</command> command, see section <xref linkend=\"mq-collab."
16304 "tips.interdiff\"/>."
16305 msgstr ""
16307 #. type: Content of: <book><chapter><sect1><sect2><title>
16308 #: ../en/ch14-hgext.xml:366
16309 msgid "Defining command aliases"
16310 msgstr "定义命令的别名"
16312 #. type: Content of: <book><chapter><sect1><sect2><para>
16313 #: ../en/ch14-hgext.xml:368
16314 msgid ""
16315 "It can be cumbersome to remember the options to both the <command role=\"hg-"
16316 "ext-extdiff\">extdiff</command> command and the diff viewer you want to use, "
16317 "so the <literal role=\"hg-ext\">extdiff</literal> extension lets you define "
16318 "<emphasis>new</emphasis> commands that will invoke your diff viewer with "
16319 "exactly the right options."
16320 msgstr ""
16322 #. type: Content of: <book><chapter><sect1><sect2><para>
16323 #: ../en/ch14-hgext.xml:375
16324 msgid ""
16325 "All you need to do is edit your <filename role=\"special\"> /.hgrc</"
16326 "filename>, and add a section named <literal role=\"rc-extdiff\">extdiff</"
16327 "literal>. Inside this section, you can define multiple commands. Here's how "
16328 "to add a <literal>kdiff3</literal> command. Once you've defined this, you "
16329 "can type <quote><literal>hg kdiff3</literal></quote> and the <literal role="
16330 "\"hg-ext\">extdiff</literal> extension will run <command>kdiff3</command> for "
16331 "you."
16332 msgstr ""
16334 #. type: Content of: <book><chapter><sect1><sect2><para>
16335 #: ../en/ch14-hgext.xml:384
16336 msgid ""
16337 "If you leave the right hand side of the definition empty, as above, the "
16338 "<literal role=\"hg-ext\">extdiff</literal> extension uses the name of the "
16339 "command you defined as the name of the external program to run. But these "
16340 "names don't have to be the same. Here, we define a command named "
16341 "<quote><literal>hg wibble</literal></quote>, which runs <command>kdiff3</"
16342 "command>."
16343 msgstr ""
16345 #. type: Content of: <book><chapter><sect1><sect2><para>
16346 #: ../en/ch14-hgext.xml:393
16347 msgid ""
16348 "You can also specify the default options that you want to invoke your diff "
16349 "viewing program with. The prefix to use is <quote><literal>opts.</literal></"
16350 "quote>, followed by the name of the command to which the options apply. This "
16351 "example defines a <quote><literal>hg vimdiff</literal></quote> command that "
16352 "runs the <command>vim</command> editor's <literal>DirDiff</literal> extension."
16353 msgstr ""
16355 #. type: Content of: <book><chapter><sect1><title>
16356 #: ../en/ch14-hgext.xml:406
16357 msgid ""
16358 "Cherrypicking changes with the <literal role=\"hg-ext\">transplant</literal> "
16359 "extension"
16360 msgstr "使用扩展 <literal role=\"hg-ext\">transplant</literal> 以挑选修改"
16362 #. type: Content of: <book><chapter><sect1><para>
16363 #: ../en/ch14-hgext.xml:409
16364 msgid "Need to have a long chat with Brendan about this."
16365 msgstr ""
16367 #. type: Content of: <book><chapter><sect1><title>
16368 #: ../en/ch14-hgext.xml:413
16369 msgid ""
16370 "Send changes via email with the <literal role=\"hg-ext\">patchbomb</literal> "
16371 "extension"
16372 msgstr ""
16373 "使用扩展 <literal role=\"hg-ext\">patchbomb</literal> 通过 email 发送修改"
16375 #. type: Content of: <book><chapter><sect1><para>
16376 #: ../en/ch14-hgext.xml:416
16377 msgid ""
16378 "Many projects have a culture of <quote>change review</quote>, in which people "
16379 "send their modifications to a mailing list for others to read and comment on "
16380 "before they commit the final version to a shared repository. Some projects "
16381 "have people who act as gatekeepers; they apply changes from other people to a "
16382 "repository to which those others don't have access."
16383 msgstr ""
16385 #. type: Content of: <book><chapter><sect1><para>
16386 #: ../en/ch14-hgext.xml:424
16387 msgid ""
16388 "Mercurial makes it easy to send changes over email for review or application, "
16389 "via its <literal role=\"hg-ext\">patchbomb</literal> extension. The "
16390 "extension is so named because changes are formatted as patches, and it's "
16391 "usual to send one changeset per email message. Sending a long series of "
16392 "changes by email is thus much like <quote>bombing</quote> the recipient's "
16393 "inbox, hence <quote>patchbomb</quote>."
16394 msgstr ""
16396 #. type: Content of: <book><chapter><sect1><para>
16397 #: ../en/ch14-hgext.xml:432
16398 msgid ""
16399 "As usual, the basic configuration of the <literal role=\"hg-ext\">patchbomb</"
16400 "literal> extension takes just one or two lines in your <filename role="
16401 "\"special\"> /.hgrc</filename>."
16402 msgstr ""
16404 #. type: Content of: <book><chapter><sect1><para>
16405 #: ../en/ch14-hgext.xml:437
16406 msgid ""
16407 "Once you've enabled the extension, you will have a new command available, "
16408 "named <command role=\"hg-ext-patchbomb\">email</command>."
16409 msgstr ""
16411 #. type: Content of: <book><chapter><sect1><para>
16412 #: ../en/ch14-hgext.xml:441
16413 msgid ""
16414 "The safest and best way to invoke the <command role=\"hg-ext-patchbomb"
16415 "\">email</command> command is to <emphasis>always</emphasis> run it first "
16416 "with the <option role=\"hg-ext-patchbomb-cmd-email-opt\">hg -n</option> "
16417 "option. This will show you what the command <emphasis>would</emphasis> send, "
16418 "without actually sending anything. Once you've had a quick glance over the "
16419 "changes and verified that you are sending the right ones, you can rerun the "
16420 "same command, with the <option role=\"hg-ext-patchbomb-cmd-email-opt\">hg -n</"
16421 "option> option removed."
16422 msgstr ""
16424 #. type: Content of: <book><chapter><sect1><para>
16425 #: ../en/ch14-hgext.xml:452
16426 msgid ""
16427 "The <command role=\"hg-ext-patchbomb\">email</command> command accepts the "
16428 "same kind of revision syntax as every other Mercurial command. For example, "
16429 "this command will send every revision between 7 and <literal>tip</literal>, "
16430 "inclusive."
16431 msgstr ""
16433 #. type: Content of: <book><chapter><sect1><para>
16434 #: ../en/ch14-hgext.xml:457
16435 msgid ""
16436 "You can also specify a <emphasis>repository</emphasis> to compare with. If "
16437 "you provide a repository but no revisions, the <command role=\"hg-ext-"
16438 "patchbomb\">email</command> command will send all revisions in the local "
16439 "repository that are not present in the remote repository. If you "
16440 "additionally specify revisions or a branch name (the latter using the <option "
16441 "role=\"hg-ext-patchbomb-cmd-email-opt\">hg -b</option> option), this will "
16442 "constrain the revisions sent."
16443 msgstr ""
16445 #. type: Content of: <book><chapter><sect1><para>
16446 #: ../en/ch14-hgext.xml:466
16447 msgid ""
16448 "It's perfectly safe to run the <command role=\"hg-ext-patchbomb\">email</"
16449 "command> command without the names of the people you want to send to: if you "
16450 "do this, it will just prompt you for those values interactively. (If you're "
16451 "using a Linux or Unix-like system, you should have enhanced "
16452 "<literal>readline</literal>-style editing capabilities when entering those "
16453 "headers, too, which is useful.)"
16454 msgstr ""
16456 #. type: Content of: <book><chapter><sect1><para>
16457 #: ../en/ch14-hgext.xml:474
16458 msgid ""
16459 "When you are sending just one revision, the <command role=\"hg-ext-patchbomb"
16460 "\">email</command> command will by default use the first line of the "
16461 "changeset description as the subject of the single email message it sends."
16462 msgstr ""
16464 #. type: Content of: <book><chapter><sect1><para>
16465 #: ../en/ch14-hgext.xml:479
16466 msgid ""
16467 "If you send multiple revisions, the <command role=\"hg-ext-patchbomb\">email</"
16468 "command> command will usually send one message per changeset. It will "
16469 "preface the series with an introductory message, in which you should describe "
16470 "the purpose of the series of changes you're sending."
16471 msgstr ""
16473 #. type: Content of: <book><chapter><sect1><sect2><title>
16474 #: ../en/ch14-hgext.xml:486
16475 msgid "Changing the behaviour of patchbombs"
16476 msgstr "修改 patchbomb 的行为"
16478 #. type: Content of: <book><chapter><sect1><sect2><para>
16479 #: ../en/ch14-hgext.xml:488
16480 msgid ""
16481 "Not every project has exactly the same conventions for sending changes in "
16482 "email; the <literal role=\"hg-ext\">patchbomb</literal> extension tries to "
16483 "accommodate a number of variations through command line options."
16484 msgstr ""
16486 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
16487 #: ../en/ch14-hgext.xml:494
16488 msgid ""
16489 "You can write a subject for the introductory message on the command line "
16490 "using the <option role=\"hg-ext-patchbomb-cmd-email-opt\">hg -s</option> "
16491 "option. This takes one argument, the text of the subject to use."
16492 msgstr ""
16494 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
16495 #: ../en/ch14-hgext.xml:500
16496 msgid ""
16497 "To change the email address from which the messages originate, use the "
16498 "<option role=\"hg-ext-patchbomb-cmd-email-opt\">hg -f</option> option. This "
16499 "takes one argument, the email address to use."
16500 msgstr ""
16502 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
16503 #: ../en/ch14-hgext.xml:506
16504 msgid ""
16505 "The default behaviour is to send unified diffs (see section <xref linkend="
16506 "\"sec.mq.patch\"/> for a description of the format), one per message. You "
16507 "can send a binary bundle instead with the <option role=\"hg-ext-patchbomb-cmd-"
16508 "email-opt\">hg -b</option> option."
16509 msgstr ""
16511 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
16512 #: ../en/ch14-hgext.xml:514
16513 msgid ""
16514 "Unified diffs are normally prefaced with a metadata header. You can omit "
16515 "this, and send unadorned diffs, with the <option role=\"hg-ext-patchbomb-cmd-"
16516 "email-opt\">hg --plain</option> option."
16517 msgstr ""
16519 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
16520 #: ../en/ch14-hgext.xml:520
16521 msgid ""
16522 "Diffs are normally sent <quote>inline</quote>, in the same body part as the "
16523 "description of a patch. This makes it easiest for the largest number of "
16524 "readers to quote and respond to parts of a diff, as some mail clients will "
16525 "only quote the first MIME body part in a message. If you'd prefer to send the "
16526 "description and the diff in separate body parts, use the <option role=\"hg-"
16527 "ext-patchbomb-cmd-email-opt\">hg -a</option> option."
16528 msgstr ""
16530 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
16531 #: ../en/ch14-hgext.xml:530
16532 msgid ""
16533 "Instead of sending mail messages, you can write them to an <literal>mbox</"
16534 "literal>-format mail folder using the <option role=\"hg-ext-patchbomb-cmd-"
16535 "email-opt\">hg -m</option> option. That option takes one argument, the name "
16536 "of the file to write to."
16537 msgstr ""
16539 #. type: Content of: <book><chapter><sect1><sect2><itemizedlist><listitem><para>
16540 #: ../en/ch14-hgext.xml:537
16541 msgid ""
16542 "If you would like to add a <command>diffstat</command>-format summary to each "
16543 "patch, and one to the introductory message, use the <option role=\"hg-ext-"
16544 "patchbomb-cmd-email-opt\">hg -d</option> option. The <command>diffstat</"
16545 "command> command displays a table containing the name of each file patched, "
16546 "the number of lines affected, and a histogram showing how much each file is "
16547 "modified. This gives readers a qualitative glance at how complex a patch is."
16548 msgstr ""