Add a read-only mirror and remove the techincal arguments

pep-0481.txt

@@ -110,21 +110,6 @@ in comparison to Mercurial. However, git has grown to support Windows as a
 first class citizen. In addition to that, for Windows users who are not well
 aquanted with the Windows command line, there are GUI options as well.
 
-On a techincal level git and Mercurial are fairly similar, however the git
-branching model is signifcantly better than Mercurial "Named Branches" for
-non-comitter contributors. Mercurial does have a "Bookmarks" extension, however
-this isn't quite as good as git's branching model. All bookmarks live in the
-same namespace so it requires individual users to ensure that they namespace
-the branchnames themselves lest the risk collision. It also is an extension
-which requires new users to first discover they need an extension at all, and
-then figure out what they need to do in order to enable that extension. Since,
-in contrast to the branching feature in git, this feature is a Mercurial
-extension, in general, its support outside the Mercurial core is less
-extensive. Finally, users who are not used to Mercurial are unlikely to
-discover bookmarks on their own, instead they will likely attempt to use
-Mercurial's "Named Branches" which, given the fact they live "forever", are not
-often what a project wants their contributors to use.
-
 
 Why Github?
 -----------
@@ -240,6 +225,9 @@ In particular this will include:
   each push.
 * Migrate any issues for these projects to their respective bug tracker on
   Github.
+* Use hg-git to provide a read-only mirror on hg.python.org which will enable
+  read-only uses of the hg.python.org instances of the specified repositories
+  to remain the same.
 
 This will restore these repositories to similar functionality as they currently
 have. In addition to this the migration will also include enabling testing for