On Mon, Nov 22, 2010 at 4:29 PM, Anand Avati <anand.avati at gmail.com> wrote: > This bug was also fixed post 3.1.0 in commit > 413b2a5f9b77fd3d7f3b26c848482ec7b914102f I see... I downgraded to 3.0.5, as 3.1 was giving me too much trouble... But I'll keep testing the new and QA releases, since I appreciate so much this work :) > Avati - []'s Hugo www.devin.com.br
