This bug was present in 0.5.2-9, silently fixed in 0.5.2-10, but came
back in 0.5.3-1!  I wish I knew what changed to break it again.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to