@Andy, unless I'm mistaken, a fix for this was committed on 2011-10-28 and is being currently in the release cycle. So it _has_ been fixed.
@Andy, unless I'm mistaken, a fix for this was committed on 2011-10-28 and is being currently in the release cycle. So it _has_ been fixed.