Your message dated Wed, 1 Aug 2012 21:47:14 +0200
with message-id <20120801194714.GA13224@x201s>
and subject line Re: Bug#506997: icedove: date ordering of threaded messages is
by newest message in thread not oldest
has caused the Debian Bug report #506997,
regarding icedove: date ordering of threaded messages is by newest message in
thread not oldest
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
506997: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506997
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: icedove
Version: 2.0.0.17-1
Severity: normal
I have noticed that in the 2.0.0.16 or 2.0.0.17 upgrade, the behaviour
of date-ordered threaded messages has changed.
Previously, choosing ascending date-ordering with threading had the
messages sorted by the oldest message in each thread.
Now the ordering appears to be by the date of the newest message in each
thread.
I prefered the original ordering. If the new ordering is now default,
please at least make the old ordering method a run-time user-selectable
option.
Arthur.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.27 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages icedove depends on:
ii debianutils 2.30 Miscellaneous utilities specific t
ii fontconfig 2.6.0-3 generic font configuration library
ii libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii libc6 2.7-16 GNU C Library: Shared libraries
ii libcairo2 1.6.4-6.1 The Cairo 2D vector graphics libra
ii libfontconfig1 2.6.0-3 generic font configuration library
ii libfreetype6 2.3.7-2 FreeType 2 font engine, shared lib
ii libgcc1 1:4.3.2-1 GCC support library
ii libglib2.0-0 2.16.6-1 The GLib library of C routines
ii libgtk2.0-0 2.12.11-4 The GTK+ graphical user interface
ii libhunspell-1.2-0 1.2.6-1 spell checker and morphological an
ii libjpeg62 6b-14 The Independent JPEG Group's JPEG
ii libnspr4-0d 4.7.1-4 NetScape Portable Runtime Library
ii libnss3-1d 3.12.0-5 Network Security Service libraries
ii libpango1.0-0 1.20.5-3 Layout and rendering of internatio
ii libpng12-0 1.2.27-2 PNG library - runtime
ii libstdc++6 4.3.2-1 The GNU Standard C++ Library v3
ii libx11-6 2:1.1.5-2 X11 client-side library
ii libxft2 2.1.12-3 FreeType-based font drawing librar
ii libxinerama1 2:1.0.3-2 X11 Xinerama extension library
ii libxrender1 1:0.9.4-2 X Rendering Extension client libra
ii libxt6 1:1.0.5-3 X11 toolkit intrinsics library
ii psmisc 22.6-1 Utilities that use the proc filesy
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
icedove recommends no packages.
Versions of packages icedove suggests:
pn icedove-gnome-support <none> (no description available)
ii latex-xft-fonts 0.1-8 Xft-compatible versions of some La
ii libthai0 0.1.9-4 Thai language support library
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 3.0.5-1
Hello Arthur,
the ordering in the thread view is since several version in your wished
date-order as default. So I close this bug.
Please feel free to reopen or open a new bug if something is'nt working
well on icedove.
Regards
Carsten
On Thu, Nov 27, 2008 at 07:52:57AM +1030, Arthur Marsh wrote:
> Package: icedove
> Version: 2.0.0.17-1
> Severity: normal
>
>
> I have noticed that in the 2.0.0.16 or 2.0.0.17 upgrade, the behaviour
> of date-ordered threaded messages has changed.
>
> Previously, choosing ascending date-ordering with threading had the
> messages sorted by the oldest message in each thread.
>
> Now the ordering appears to be by the date of the newest message in each
> thread.
>
> I prefered the original ordering. If the new ordering is now default,
> please at least make the old ordering method a run-time user-selectable
> option.
>
> Arthur.
>
--- End Message ---
