[pypy-dev] change of strategy for the py3k branch?
Amaury Forgeot d'Arc
amauryfa at gmail.com
Wed May 30 11:23:02 CEST 2012
2012/5/30 Antonio Cuni <anto.cuni at gmail.com>
> 2) start a completely new repository which contains only the code for py3k.
How is this different from the current py3k branch?
We could also just decide to never merge the default branch,
or merge only after a release of the main PyPy version.
--
Amaury Forgeot d'Arc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20120530/2d649cfe/attachment.html>
More information about the pypy-dev
mailing list