> Thanks for the pointer but this patch is not even contained > in trunk yet and as far as I remember the patch is "only" an > optimization (compared to a bug that makes a functionality > unusable). So I would guess that it misses the boat for 2.2.5.
The patch is not an optimization--it fixes a bug in an optimization. It is true though that the bug and the bug fix only affect performance, not functionality.
