okay, i think we should consider just disabling this error message
entirely, as long as we're applying the system timezonedb patch.
after all, isn't the point of the patch that we *can* trust the local
timezone database?

thoughts?

        sean

Attachment: signature.asc
Description: Digital signature

Reply via email to