changeset 822:fd2e83ffb165

Add paragraph tags

--- a/en/appA-svn.xml	Tue Apr 28 23:10:43 2009 -0700
+++ b/en/appA-svn.xml	Tue Apr 28 23:14:14 2009 -0700
@@ -75,7 +75,7 @@
       <filename>.hg/shamap</filename> inside the target
       repository.</para>
 
-    <para>When you want to start making changes using Mercurial, it's
+    <para id="x_707">When you want to start making changes using Mercurial, it's
       best to clone the tree in which you are doing your conversions,
       and leave the original tree for future incremental conversions.
       This is the safest way to let you pull and merge future commits
@@ -85,7 +85,7 @@
     <sect2>
       <title>Converting multiple branches</title>
 
-      <para>The <command>hg convert</command> command given above
+      <para id="x_708">The <command>hg convert</command> command given above
 	converts only the history of the <literal>trunk</literal>
 	branch of the Subversion repository.  If we instead use the
 	URL <literal>http://python-nose.googlecode.com/svn</literal>,
@@ -95,7 +95,7 @@
 	usually use, and it will import each as a separate Mercurial
 	branch.</para>
 
-      <para>By default, each Subversion branch imported into Mercurial
+      <para id="x_709">By default, each Subversion branch imported into Mercurial
 	is given a branch name.  After the conversion completes, you
 	can get a list of the active branch names in the Mercurial
 	repository using <command>hg branches -a</command>. If you
@@ -104,7 +104,7 @@
 	  convert.hg.usebranchnames=false</option> option to
 	<command>hg convert</command>.</para>
 
-      <para>Once you have converted your tree, if you want to follow
+      <para id="x_70a">Once you have converted your tree, if you want to follow
 	the usual Mercurial practice of working in a tree that
 	contains a single branch, you can clone that single branch
 	using <command>hg clone -r mybranchname</command>.</para>
@@ -183,7 +183,7 @@
     <sect2>
       <title>Improving Subversion conversion performance</title>
 
-      <para>You will often need several attempts before you hit the
+      <para id="x_70b">You will often need several attempts before you hit the
 	perfect combination of user map, file map, and other
 	conversion parameters.  Converting a Subversion repository
 	over an access protocol like <literal>ssh</literal> or
@@ -192,7 +192,7 @@
 	network delays.  This can make tuning that perfect conversion
 	recipe very painful.</para>
 
-      <para>The <ulink
+      <para id="x_70c">The <ulink
 	  url="http://svn.collab.net/repos/svn/trunk/notes/svnsync.txt"><command>svnsync</command></ulink> 
 	command can greatly speed up the conversion of a Subversion
 	repository.  It is a read-only mirroring program for
@@ -200,41 +200,41 @@
 	mirror of your Subversion tree, then convert the mirror into a
 	Mercurial repository.</para>
 
-      <para>Suppose we want to convert the Subversion repository for
+      <para id="x_70d">Suppose we want to convert the Subversion repository for
 	the popular Memcached project into a Mercurial tree.  First,
 	we create a local Subversion repository.</para>
 
       <screen><prompt>$</prompt> <userinput>svnadmin create memcached-mirror</userinput></screen>
 
-      <para>Next, we set up a Subversion hook that
+      <para id="x_70e">Next, we set up a Subversion hook that
 	<command>svnsync</command> needs.</para>
 
       <screen><prompt>$</prompt> <userinput>echo '#!/bin/sh' > memcached-mirror/hooks/pre-revprop-change</userinput>
 <prompt>$</prompt> <userinput>chmod +x memcached-mirror/hooks/pre-revprop-change</userinput></screen>
 
-      <para>We then initialize <command>svnsync</command> in this
+      <para id="x_70f">We then initialize <command>svnsync</command> in this
 	repository.</para>
 
       <screen><prompt>$</prompt> <userinput>svnsync --init file://`pwd`/memcached-mirror \
   http://code.sixapart.com/svn/memcached</userinput></screen>
 
-      <para>Our next step is to begin the <command>svnsync</command>
+      <para id="x_710">Our next step is to begin the <command>svnsync</command>
 	mirroring process.</para>
 
       <screen><prompt>$</prompt> <userinput>svnsync sync file://`pwd`/memcached-mirror</userinput></screen>
 
-      <para>Finally, we import the history of our local Subversion
+      <para id="x_711">Finally, we import the history of our local Subversion
 	mirror into Mercurial.</para>
 
       <screen><prompt>$</prompt> <userinput>hg convert memcached-mirror</userinput></screen>
       
-      <para>We can use this process incrementally if the Subversion
+      <para id="x_712">We can use this process incrementally if the Subversion
 	repository is still in use.  We run <command>svnsync</command>
 	to pull new changes into our mirror, then <command>hg
 	  convert</command> to import them into our Mercurial
 	tree.</para>
 
-      <para>There are two advantages to doing a two-stage import with
+      <para id="x_713">There are two advantages to doing a two-stage import with
 	<command>svnsync</command>.  The first is that it uses more
 	efficient Subversion network syncing code than <command>hg
 	  convert</command>, so it transfers less data over the