Comment # 3 on bug 1178624 from
FWIW, this patch fixes the problem indeed.


You are receiving this mail because: