VM

Activity log for bug #995324

Date Who What changed Old value New value Message
2012-05-06 02:18:02 Uday Reddy bug added bug
2012-05-06 19:55:13 Uday Reddy description Here is a pretty intricate problem. Assume a folder contains messages M1: Subject A M2: Subject A and subject threading has grouped M1 and M2 together. If M2's parent (say P) with a different subject B gets inserted into the folder, VM's threading database becomes inconsistent. M2's thread-list is reset. However, M1's thread-subtree still contains M2. The subject node for "A" seems to retain M2 as well. Here is a pretty intricate problem. Assume a folder contains messages   M1: Subject A         M2: Subject A and subject threading has grouped M1 and M2 together. If M2's parent (say P) with a different subject B gets inserted into the folder, VM's threading database becomes inconsistent. Essentially, both M1's thread and P's thread claim ownership of M2. M2's thread-list is reset. However, M1's thread-subtree still contains M2. The subject node for "A" seems to retain M2 as well.
2012-05-06 19:57:49 Uday Reddy vm: status Triaged In Progress
2012-05-30 07:43:19 Launchpad Janitor branch linked lp:vm