--- Comment #5 from Henri Verbeet hverbeet@gmail.com ---
On first sight, this looks similar to the issue fixed by commit
b1c84499544354e75505cc366352c72c010d735e. Does this still happen with current
git?
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.