[kmail2] [Bug 279115] Standard Mailing list doesn't thread properly

[Daniel Vrátil]

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

Daniel Vrátil <dvratil at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|                            |5.10.0
      Latest Commit|                            |https://commits.kde.org/mes
                   |                            |sagelib/dc4a7feb10f035be1a7
                   |                            |12e67d75daf7ebe859f33
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #12 from Daniel Vrátil <dvratil at kde.org> ---
Git commit dc4a7feb10f035be1a712e67d75daf7ebe859f33 by Daniel Vrátil, on behalf
of Jan Janssen.
Committed on 16/08/2018 at 22:02.
Pushed by dvratil into branch 'master'.

Thread messages with same reference ID together

Summary:
Thread messages with same reference ID together

Messages from github or bugzilla usually use In-Reply-To and References headers
with an ID that either doesn't actually exist or just isn't around in the
folder. In case of bugzilla, no threading happens in that case because subject
lines don't start with "Re:". github does do that, but oftentimes the subject
based threading is imprecise (by design).

Therefore create a sorted-by-date cache of messages similar to the subject
based cache and put any message we cannot perfectly thread to the very first
message with the same message ID.
What results is a flat but threaded messagelist similar to what thunderbird
does.

FIXED-IN: 5.10.0

Reviewers: dvratil

Reviewed By: dvratil

Subscribers: dvratil, bruns, kde-pim

Tags: #kde_pim

Differential Revision: https://phabricator.kde.org/D14883

M  +89   -4    messagelist/src/core/model.cpp
M  +9    -0    messagelist/src/core/model_p.h

https://commits.kde.org/messagelib/dc4a7feb10f035be1a712e67d75daf7ebe859f33

-- 
You are receiving this mail because:
You are the assignee for the bug.