M.-A. Lemburg wrote: > Benjamin Peterson wrote: >> After I tag 2.7 this Saturday, I will effect the following changes in >> the repository: >> - I will make the 2.7 maintenance branch. >> - I will remove svnmerge from trunk -> py3k. >> - I will initialize svnmerge from py3k -> 2.7maint. >> - The trunk will be officially closed. I suggest you just delete your >> trunk working copies (or switch them anyway) because a commit hook >> will be in place to prevent commits to it. > > Wouldn't it be better to make the py3k branch the new trunk by > removing the 2.7 code and moving the Python3 code into that > directory ?
With "that directory" I meant trunk/, i.e. along the lines of: svn remove trunk svn move branches/py3k trunk -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jul 02 2010) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2010-07-19: EuroPython 2010, Birmingham, UK 16 days to go ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers