That's more than fair. I can keep an eye on when this code gets into an
actual release, and some time after that, comment here that things are
looking good (or that they're not).
The risk I was attempting to minimize was the behavioral change. If
people relied on the current behavior, then applying this fix to stable
would be problematic. I'm arguing that that concern doesn't apply.
As far as the risk of this fix introducing some other bug or otherwise
having adverse affects, I'll defer entirely to your judgment. Seeing
how this plays out upstream before making any changes to stable makes
perfect sense.
