On Fri, Feb 4, 2011 at 1:17 PM, Jesus Cea <j...@jcea.es> wrote: > "Up-porting" CAN'T be forgotten because it is done "automagically" vía > mercurial merges. That is the point...
So developer A checks in a fix on 2.7, then gets sidetracked before forward porting it. When does it make it to 3.2 or the main development branch? Does everyone doing a forward merge from the maintenance branches run the risk of being landed with the task of doing a bulk merge of any forgotten forward ports before they can forward port the fix they're actually trying to implement? Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
