http://bugs.kde.org/show_bug.cgi?id=86423
--- Comment #76 from Thomas McGuire <mcguire kde org> 2009-01-15 16:42:25 --- > With your kind permission: the easiest and fastest way to stop this > discussion is by replying to above Comment #68. I don't believe that, but here you go: > Why is the bug tagged NEW? Because there is only UNCONFIRMED and NEW, and it is not UNCONFIRMED. NEW really means CONFIRMED in the bug tracker. > Why is the priority set to NOR? Because we usually don't use the priority system. Believe me, I know this bug is important. > Why is severity set to wishlist? Because it is only a bug when some code doesn't work as it should. Since there is actually no code to preserve the HTML structure, this is a wish. I know this is a very developer-centric way, but this makes it easier for us to deal with it. > What are the chances of having this bug fixed in the foreseeable future? Is a > bugfix scheduled for KDE 4.2 or 4.3? Definitly not 4.2, that is feature-frozen already. I hope I can find time to do something about it before 4.3 -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
