On Feb 25, 2011, at 01:50 AM, Raymond Hettinger wrote: > >On Feb 25, 2011, at 12:09 AM, Martin v. Löwis wrote: > >> I think I would have liked the strategy of the PEP better (i.e. >> create clones for feature branches, rather than putting all >> in a single repository). > >In my brief tests, the single repository has been easy to work with. >If they were separate, it would complicate backporting patches >and merges. So, I'm happy with how George and Benjamin put this together.
The way I work with the Subversion branches is to have all the active branches checked out into separate directories under a common parent, e.g. ~/projects/python/py26 ~/projects/python/py27 ~/projects/python/trunk ~/projects/python/py31 ~/projects/python/py32 ~/projects/python/py3k This makes it very easy to just cd, svn up, make distclean, configure, make to test things. How can I do this with the hg clone when all the branches are in the single repository, but more or less hidden? After doing the 'hg clone' operation specified by Antoine, I'm left with a single cpython directory containing (iiuc) the contents of the 'default' branch. I'm sure I'm not the only one who works this way with Subversion. IWBN to cover this in the devguide (or is it there and I missed it?). Cheers, -Barry
signature.asc
Description: PGP signature
_______________________________________________ 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
