Any pointers to where in the code base I should start looking/hacking if I wanted to try and write such a patch?
As I'm the main one arguing for this improvement, I'm willing to at least try and solve it :) -- Pull me down under... On Fri, Sep 3, 2010 at 1:27 PM, Brian Fox <bri...@infinity.nu> wrote: > Seems logical to me, not sure how much work that is to fix, but > patches would be a good way to ensure this gets in. Certainly I could > see this being a problem that's worth trying to address prior to M3.0 > if it's not risky. >
