On Tue, Nov 16, 2010 at 10:25 PM, Steve Holden 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
relea
On Tue, Nov 16, 2010 at 9:01 AM, Georg Brandl wrote:
..
> those of you who choose to observe commit freezes may now
> again commit to trunk.
I assume you meant "to the py3k branch."
___
python-committers mailing list
python-committers@python.org
http://
On 11/16/2010 9:17 AM, Alexander Belopolsky wrote:
> On Tue, Nov 16, 2010 at 9:01 AM, Georg Brandl wrote:
> ..
>> those of you who choose to observe commit freezes may now
>> again commit to trunk.
>
> I assume you meant "to the py3k branch."
> ___
An
On Wed, Nov 17, 2010 at 1:43 AM, Jesus Cea 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 wrote:
>>>
>>> Any why wouldn't the py3k branch now be trunk?
>>
>> If you meant, why would't the py3
-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 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 s