Georg> If you don't change repo configuration after these commands, "hg
Georg> pull" in the 3.2 repo will pull from the local cpython repo. I'd
Georg> advise to set the "default" entry in each of the clones' .hg/hgrc
Georg> file to http://hg.python.org/cpython (as a committer you should
Georg> be using ssh://h...@hg.python.org/cpython BTW).
Thanks. That's not what the dev guide says in its intro here:
http://docs.python.org/devguide/setup.html#getting-the-source-code
(That is, the dev guide has a new sub-audience other than just people new to
Python core development. It also now has to cater a little to people like
me with little Mercurial experience.)
Georg> This way, "hg push" and "hg pull" communicate with the remote
Georg> repo.
I don't like that at all.
Georg> You can still exchange commits with the other local clones by
Georg> using, for example, "hg push ../3.2". (You can also add another
Georg> entry in the .hgrc's [paths] section if you want to give
Georg> nicknames to these path names).
That seems better.
Thx,
Skip
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
