I just noticed this bug was targeted to 1.4.0. Is
the intention to get this new patch in?

andrew

Reply via email to