hgbook
diff en/ch13-hgext.xml @ 710:8613844dd2cf
Update po files with source xml files
author | Dongsheng Song <songdongsheng@live.cn> |
---|---|
date | Sat Apr 18 10:09:11 2009 +0800 (2009-04-18) |
parents | 1c13ed2130a7 |
children |
line diff
1.1 --- a/en/ch13-hgext.xml Mon Mar 30 16:23:33 2009 +0800 1.2 +++ b/en/ch13-hgext.xml Sat Apr 18 10:09:11 2009 +0800 1.3 @@ -99,7 +99,7 @@ 1.4 the background and receives notifications from the 1.5 <literal>inotify</literal> subsystem. It also listens for 1.6 connections from a regular Mercurial command. The extension 1.7 - modifies Mercurial's behaviour so that instead of scanning the 1.8 + modifies Mercurial's behavior so that instead of scanning the 1.9 filesystem, it queries the daemon. Since the daemon has perfect 1.10 information about the state of the repository, it can respond 1.11 with a result instantaneously, avoiding the need to scan every 1.12 @@ -249,7 +249,7 @@ 1.13 <para id="x_520">When you're using the <literal 1.14 role="hg-ext">inotify</literal> extension, you should notice 1.15 <emphasis>no difference at all</emphasis> in Mercurial's 1.16 - behaviour, with the sole exception of status-related commands 1.17 + behavior, with the sole exception of status-related commands 1.18 running a whole lot faster than they used to. You should 1.19 specifically expect that commands will not print different 1.20 output; neither should they give different results. If either of 1.21 @@ -481,7 +481,7 @@ 1.22 purpose of the series of changes you're sending.</para> 1.23 1.24 <sect2> 1.25 - <title>Changing the behaviour of patchbombs</title> 1.26 + <title>Changing the behavior of patchbombs</title> 1.27 1.28 <para id="x_53b">Not every project has exactly the same conventions for 1.29 sending changes in email; the <literal 1.30 @@ -501,7 +501,7 @@ 1.31 option. This takes one argument, the email address to 1.32 use.</para> 1.33 </listitem> 1.34 - <listitem><para id="x_53e">The default behaviour is to send unified diffs 1.35 + <listitem><para id="x_53e">The default behavior is to send unified diffs 1.36 (see <xref linkend="sec:mq:patch"/> for a 1.37 description of the 1.38 format), one per message. You can send a binary bundle