[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 61891] Threading by subject and duplicates
From:       Marek Wawrzyczny <marekw1977 () yahoo ! com ! au>
Date:       2004-08-02 0:15:26
Message-ID: 20040802001526.24768.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=61891      




------- Additional Comments From marekw1977 yahoo com au  2004-08-02 02:15 -------
Quote:
"...it would make much more sense to add the "Re: foo" message below the "foo" \
message which has the most recent date compared to the date of the "Re: foo" message. \
  
 Example: 
 That's how it should be: 
 + foo          2003-07-30 
 +-- Re: foo   2003-07-31 
 ... 
 + foo          2003-05-05 
 +-- Re: foo   2003-05-07 ..."

I disagree. The thread should always have the date of the last message posted. In \
fact any tree should have the last posted message so that the entire thread is pushed \
up to the top of the list. In the example below if the current date is 2003-07-31 I \
will be able to see my thread (if the thread is collapsed) in the list as I have \
received a new message today. If we display foo's date then since it's 2002-09-11 I \
will not be able to see the message in the list unless I scroll down to messages \
circa that date. So, the thread should not show the original message in question, it \
should become a sort of a marker or summary/digest for the entire thread, but most \
importantly, it has to always point to the freshest message in the thread.

 + foo          2003-07-31  
 +--- Re: foo   2003-07-31 
 +--- Re: foo   2003-01-01
      +--- Re: foo 2003-01-01
      +--- Re: foo 2002-09-23 
 +--- Re: foo   2002-09-12 
 +--- foo   2002-09-11
_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel


[prev in list] [next in list] [prev in thread] [next in thread]