This is such a glaring bug, to not patch it is to say we DO NOT support POP3 file storage support (and would need to announce that very loudly since this is the configuration out of the box). I think it's great the code is more scalable, cleaner, better documented, but this has been such a glaring bug for so long. Heck, it's just one of those poorly thought out "features" of Avalon, and it wouldn't take much work to just copy the code and undo the change that broke this. Ok, it'd be a little more work to be backwards compatible, but still, really not that much.
Can we vote to let me patch this? (or show me the previous vote so I can appeal to however blocked it... I've searched the archives for the bug # and can't find it).
--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com
Danny Angus wrote:
James in in a code freeze pending release of version 2.1 I can't say when the release is likely to happen, but it is unlikely that this issue is going to be addressed before then.The reason for it not being fixed before now is because we inherit it from Avalon. We are intending to replace that with our own filesystem code in the next cycle. d.-----Original Message----- From: Dejan Nenov [mailto:[EMAIL PROTECTED]] Sent: 19 December 2002 07:44 To: [EMAIL PROTECTED] Subject: There is no active development on James To any committers / active contributors to James development out there - can you please review and verify bug 15460 - unless no one else can reproduce the problem - it seems to be making James totally unusable! Thank you, Dejan
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
