23 Apr
2007
23 Apr
'07
5:31 p.m.
On Sun, 22 Apr 2007, Dave Horsfall wrote:
I tested and verified that this error has been fixed since the 2.3.32 release. If you upgrade, you should not encounter this problem in the future.
Thanks, Quanah; I'll look at upgrading on the morrow.
I confirm that 2.3.35 indeed fixes the problem.
Is there any reason why 2.3.35 has not been flagged as STABLE? I see I'm not the only one bound by policy :-)
Of course, if there's bugs in 2.3.35 then I'd like to know about them...
--
Dave Horsfall DTM VK2KFU daveh@ci.com.au Ph: +61 2 9552-5509 (d) -5500 (sw)
Corinthian Eng'ng P/L, Ste 54 Jones Bay Whf, 26-32 Pirrama Rd, Pyrmont 2009, AU