Summary | second sorting column for message list |
Queue | IMP |
Queue Version | HEAD |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | vilius (at) lnk (dot) lt |
Created | 08/25/2004 (7700 days ago) |
Due | |
Updated | 08/25/2004 (7700 days ago) |
Assigned | |
Resolved | 08/25/2004 (7700 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
to me because it would create "jumps" when you browse through the
message of a mailbox sorted this way. I can't see any benefit from
such a sorting order.
*ascending* and sorting by date *descending*. Now it is possible only
to sort by thread and by date BOTH in one direction.
State ⇒ Resolved
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ second sorting column for message list
Queue ⇒ IMP
thought why not have this in IMP. For example now it is not possible
to sort messages by thread ascending, and by date descending.