➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author benjamin.peterson
Recipients benjamin.peterson, christian.heimes, gvanrossum
Date 2008-03-25.21:19:43
SpamBayes Score 0.5597516
Marked as misclassified No
Message-id <1afaf6160803251419n34a33b6dtb65204cd76bdc4ec@mail.gmail.com>
In-reply-to <1206479872.3.0.0786242030248.issue2390@psf.upfronthosting.co.za>
Content 
On Tue, Mar 25, 2008 at 4:17 PM, Christian Heimes <report@bugs.python.org>
wrote:

>
> Christian Heimes <lists@cheimes.de> added the comment:
>
> For the record
>
> You don't have to merge changes from 2.6 to 3.0 manually. In fact you
> mustn't unless you explicitly block the revision with svnmerge.py. In
> general you submit a change to 2.6 and it gets merged into 3.0 later.

Thanks for the heads up. Should I block the revision then?

>
>
> __________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue2390>
> __________________________________
>
Files
File name Uploaded
unnamed benjamin.peterson, 2008-03-25.21:19:42
History
Date User Action Args
2008-03-25 21:19:44benjamin.petersonsetspambayes_score: 0.559752 -> 0.5597516
recipients: + benjamin.peterson, gvanrossum, christian.heimes
2008-03-25 21:19:43benjamin.petersonlinkissue2390 messages
2008-03-25 21:19:43benjamin.petersoncreate