Am 02.07.2010 09:53, schrieb M.-A. Lemburg:
M.-A. Lemburg wrote:
Benjamin Peterson wrote:
After I tag 2.7 this Saturday, I will effect the following changes in the repository: trunk working copies (or switch them anyway) because a commit hook
- 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
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
While that would be logical if we continued to use SVN, it's probably not worth it when we switch to Hg anyway a short time later, so avoiding the potential confusion is better.
Georg
-- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.