Dear fellow committers,
those of you who choose to observe commit freezes may now again commit to trunk.
Thanks, Georg
On 11/16/2010 9:17 AM, Alexander Belopolsky wrote:
On Tue, Nov 16, 2010 at 9:01 AM, Georg Brandl <g.brandl@gmx.net> wrote: ..
those of you who choose to observe commit freezes may now again commit to trunk.
I assume you meant "to the py3k branch."
Any why wouldn't the py3k branch now be trunk?
regards Steve
Steve Holden +1 571 484 6266 +1 800 494 3119 PyCon 2011 Atlanta March 9-17 http://us.pycon.org/ See Python Video! http://python.mirocommunity.org/ Holden Web LLC http://www.holdenweb.com/
On Tue, Nov 16, 2010 at 10:25 PM, Steve Holden <steve@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.
-- Senthil
-----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@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. God, it is about time :-).
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBTOKml5lgi5GaxT1NAQL+ggQAnog3CAUufiL7zg57kcaHNp/+66yBgSXa rTw6w+23GVarKBgdTt+92f0B0EXxzUIP05GcmWkTThiEreYj38s7PVU6RJKWFevC SCK2LFcRpoTPN9q4HBcPmyxqv/wZ2m2UM64j3KhAvkmD0tGCMg+cgNy4q3F4onYb zHRDLrBWK5w= =IoNr -----END PGP SIGNATURE-----
On Wed, Nov 17, 2010 at 1:43 AM, Jesus Cea <jcea@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@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 :)
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (6)
-
Alexander Belopolsky -
Georg Brandl -
Jesus Cea -
Nick Coghlan -
Senthil Kumaran -
Steve Holden