[Python-checkins] devguide (hg_transition): Improve wording and remove obsolete XXX

antoine.pitrou python-checkins at python.org
Tue Mar 1 21:17:09 CET 2011


http://hg.python.org/devguide/rev/b2c4d9cb4463
changeset:   360:b2c4d9cb4463
branch:      hg_transition
user:        Antoine Pitrou <solipsis at pitrou.net>
date:        Tue Mar 01 21:17:06 2011 +0100
summary:
  Improve wording and remove obsolete XXX

files:
  committing.rst

diff --git a/committing.rst b/committing.rst
--- a/committing.rst
+++ b/committing.rst
@@ -229,7 +229,7 @@
 If you want to work on a feature long-term (perhaps you're implementing a
 PEP), you will probably want to publish your work in a dedicated repository.
 The following instructions will help you do so on `hg.python.org
-<http://hg.python.org>`_'s infrastructure without requiring a lot of upstream
+<http://hg.python.org>`_'s infrastructure without requiring a lot of upload
 bandwidth.
 
 Go to the main repository's Web page (http://hg.python.org/cpython/); there
@@ -266,7 +266,7 @@
       $ hg pull http://hg.python.org/cpython
       $ hg update
 
-It is recommended that you create a new named branch for your work, so as
+It is recommended that you create a new `named branch`_ for your work, so as
 to easily track changes.  That named branch will exist in your feature
 repository, but not in the main repository::
 
@@ -280,10 +280,11 @@
 
 When you push them, they will land in the public repository at
 ``ssh://hg@hg.python.org/features/mywork`` (or
-``http://hg.python.org/features/mywork`` for the read-only URL).
+``http://hg.python.org/features/mywork`` for the read-only URL).  Other
+people can clone the public repository and work on the code too.
 
-When you want to synchronize your changes, you can pull from the main
-repository, either from its remote URL::
+When you want to synchronize with CPython's upstream changes, you can pull
+from the main repository, either from its remote URL::
 
    $ hg pull http://hg.python.org/cpython
 
@@ -299,10 +300,7 @@
    $ hg merge default
 
 
-.. XXX: since the initial "hg push" can be quite long on asymmetric
-   connections, we could offer a way for people to make a remote-to-remote
-   clone (like SVN allows creating branches by remote copying).
-   hg currently doesn't support that.
+.. _named branch: http://mercurial.selenic.com/wiki/NamedBranches
 
 
 Uploading a patch for review

-- 
Repository URL: http://hg.python.org/devguide


More information about the Python-checkins mailing list