Since I was originally hoping this would have been fixed before the 1.1.0 release went out, definitely a +1 from me on getting it into a quick maintenance release.

Thanks,
Jeremy

Reply via email to