Message 77592 - Python tracker

➜

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	loewis
Recipients	akuchling, loewis
Date	2008-12-11.06:38:41
SpamBayes Score	4.567666e-08
Marked as misclassified	No
Message-id	<4940B56F.9000305@v.loewis.de>
In-reply-to	<1228961494.72.0.824759677299.issue4259@psf.upfronthosting.co.za>

Content
> Committed to 2.5 in rev. 67693. > > Do I need to 'svnmerge block' this revision to prevent > future merges from attempting to apply it to trunk? I don't fully understand the question (did you wonder whether to invoke the block on the trunk, or on the branch?). I think this answer is "no": we neither merge from the trunk to the 2.5 branch, nor vice versa, using svnmerge.

> Committed to 2.5 in rev. 67693.
> 
> Do I need to 'svnmerge block' this revision to prevent
> future merges from attempting to apply it to trunk?

I don't fully understand the question (did you wonder
whether to invoke the block on the trunk, or on the
branch?). I think this answer is "no": we neither merge
from the trunk to the 2.5 branch, nor vice versa, using
svnmerge.

History
Date	User	Action	Args
2008-12-11 06:38:42	loewis	set	recipients: + loewis, akuchling
2008-12-11 06:38:41	loewis	link	issue4259 messages
2008-12-11 06:38:41	loewis	create