Ezio Melotti <ezio.melo...@gmail.com> added the comment: - $ hg clone py3k py3.2 - $ cd py3.2 - $ hg update 3.2 + $ hg clone py3k py3.2 -u 3.2
While the second command is more concise, I find the first easier to understand, so maybe you could leave both the first time (proposing the concise one as an alternative), and then use just the second. It's also possible to do "hg clone py3k#3.2 py3.2". There are a few differences between the process you describe and the one I personally use (e.g. I first commit on 2.7, export/import on 3.2, merge with 3.3). Also since I cloned 2.7 using py3k#2.7, I don't think I would be able to graft a py3 changeset in 2.7 (but it should work the other way around). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14468> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
