https://bugs.kde.org/show_bug.cgi?id=310887

Christian Mollekopf <chrig...@fastmail.fm> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED
      Latest Commit|                            |http://commits.kde.org/kdep
                   |                            |imlibs/d0cd431fbc433f9bdcd4
                   |                            |64340027140a737647ca
      Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep
                   |imlibs/d0cd431fbc433f9bdcd4 |imlibs/05738951d9b1a78b9832
                   |64340027140a737647ca        |be5eda3c1b0fe99f12bd

--- Comment #9 from Christian Mollekopf <chrig...@fastmail.fm> ---
Git commit d0cd431fbc433f9bdcd464340027140a737647ca by Christian Mollekopf.
Committed on 10/12/2013 at 09:09.
Pushed by cmollekopf into branch 'master'.

Made the socketTimer a bit simpler and more robust.

There is no need for the code to not be a little more forgiving, and we can
easily get into a situation
with the timer already running on startNext. e.g. due to socketActivity of due
to unhandled data (BYE).

This will hopefully fix the ASSERT people were running into.

M  +6    -14   kimap/session.cpp

http://commits.kde.org/kdepimlibs/d0cd431fbc433f9bdcd464340027140a737647ca

--- Comment #10 from Christian Mollekopf <chrig...@fastmail.fm> ---
Git commit 05738951d9b1a78b9832be5eda3c1b0fe99f12bd by Christian Mollekopf.
Committed on 10/12/2013 at 10:22.
Pushed by cmollekopf into branch 'master'.

Handle BYE.

M  +12   -0    kimap/session.cpp

http://commits.kde.org/kdepimlibs/05738951d9b1a78b9832be5eda3c1b0fe99f12bd

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

Reply via email to