Comment 4 for bug 516180

Revision history for this message
Daniel Kulesz (kuleszdl) wrote :

I fully support the idea of adressing this issue in 1.3.1 :-)