Marcus Brinkmann <[EMAIL PROTECTED]> writes:

> Is it okay to check in the below workaround until you got around to do it
> proper? The current code is certainly bogus and is the cause of a
> reproducible bug. The below patch just restores the situation as it was
> before the breakage.

I just checked in a proper fix.

Reply via email to