[python-committers] trunk is open
ncoghlan at gmail.com
Wed Nov 17 12:51:41 CET 2010
On Wed, Nov 17, 2010 at 1:43 AM, Jesus Cea <jcea at jcea.es> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 16/11/10 15:36, Senthil Kumaran wrote:
>> On Tue, Nov 16, 2010 at 10:25 PM, Steve Holden <steve at holdenweb.com> wrote:
>>> Any why wouldn't the py3k branch now be trunk?
>> If you meant, why would't the py3k branch be renamed to trunk, then I
>> think, it was do with svn properties and tracking of merges.
>> We use svnmerge to backport py3k to release31-maint and
>> release27-maint. In 2.x series, we used to port 2.x trunk code to py3k
>> and then from py3k to release31-maint. In the current scenario, the
>> second case remains intact.
> All these will be meaningless after we finish the mercurial migration.
Which would be the other reason we didn't bother renaming the py3k branch :)
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
More information about the python-committers