Comment 7 for bug 1041315

An easy, albeit brutal way is to do a reverse bisect between 3.0 and 3.2: Mark every good commit as bad and every bad commit as good and git bisect will happily tell you which commit fixed a bug (git bisect isn't using a symmetric and so needs a few tricks to figure out where a bugfix instead of a regression is).

Looking at f47166d2 I don't have any idea what could a candidate for backporting to 3.0 from 3.2.