hgbook

diff en/ch03-concepts.xml @ 702:18131160f7ee

New IDs
author Bryan O'Sullivan <bos@serpentine.com>
date Mon May 04 23:53:21 2009 -0700 (2009-05-04)
parents 477d6a3e5023
children
line diff
     1.1 --- a/en/ch03-concepts.xml	Mon May 04 23:52:38 2009 -0700
     1.2 +++ b/en/ch03-concepts.xml	Mon May 04 23:53:21 2009 -0700
     1.3 @@ -116,7 +116,7 @@
     1.4  	Mercurial tracks hasn't changed between two changesets, the
     1.5  	entry for that file in the two revisions of the manifest will
     1.6  	point to the same revision of its filelog<footnote>
     1.7 -	  <para>It is possible (though unusual) for the manifest to
     1.8 +	  <para id="x_725">It is possible (though unusual) for the manifest to
     1.9  	    remain the same between two changesets, in which case the
    1.10  	    changelog entries for those changesets will point to the
    1.11  	    same revision of the manifest.</para>
    1.12 @@ -746,7 +746,7 @@
    1.13  
    1.14        <itemizedlist>
    1.15  	<listitem>
    1.16 -	  <para>When Mercurial checks the state of a file in the
    1.17 +	  <para id="x_726">When Mercurial checks the state of a file in the
    1.18  	    working directory, it first checks a file's modification
    1.19  	    time against the time in the dirstate that records when
    1.20  	    Mercurial last wrote the file. If the last modified time
    1.21 @@ -755,7 +755,7 @@
    1.22  	    need to check any further.</para>
    1.23  	</listitem>
    1.24  	<listitem>
    1.25 -	  <para>If the file's size has changed, the file must have
    1.26 +	  <para id="x_727">If the file's size has changed, the file must have
    1.27  	    been modified.  If the modification time has changed, but
    1.28  	    the size has not, only then does Mercurial need to
    1.29  	    actually read the contents of the file to see if it has
    1.30 @@ -763,7 +763,7 @@
    1.31  	</listitem>
    1.32        </itemizedlist>
    1.33  
    1.34 -      <para>Storing the modification time and size dramatically
    1.35 +      <para id="x_728">Storing the modification time and size dramatically
    1.36  	reduces the number of read operations that Mercurial needs to
    1.37  	perform when we run commands like <command>hg status</command>.
    1.38  	This results in large performance improvements.</para>