Barry Warsaw wrote: > On Feb 03, 2011, at 08:54 AM, Nick Coghlan wrote: > >> I suspect this problem with the preferred DVCS workflow is going to >> cut fairly heavily into the number of bug fixes applied to the >> maintenance branches. > > I'd be really surprised if it *has* to be that way. Just how painful is it in > Mercurial to apply to newest branch first and back port?
Another question: Wouldn't it be easier to apply the patch to the mainline branch and the apply it to all release branches from there (and regardless of the order) ? I don't think "up-porting" patches works well for Python, since you usually have to adapt new patches to make them fit older releases (not the other way around). -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Feb 03 2011) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
