I don't know that we'll actually try to fix this for 2.1, but it does seem like a small valid fix. We may punt and just roll it all into 2.2, but I'll fix it targeting 2.1 and we can decide whether its worth a release there.
I don't know that we'll actually try to fix this for 2.1, but it does seem like a small valid fix. We may punt and just roll it all into 2.2, but I'll fix it targeting 2.1 and we can decide whether its worth a release there.