RE: Thread date problems... 2.0a21

From: Paul Haldane <Paul.Haldane_at_newcastle.ac.uk_at_hypermail-project.org>
Date: Mon, 17 May 1999 14:46:15 +0100 (GMT)
Message-ID: <Pine.GSO.3.95-960729.990517133628.19236A-100000_at_carr6.ncl.ac.uk>

OK - I see the problem (I think). When I read the dates from old messages when adding a new message to the archive I'm interpreting the ISO format times not as UTC times (which is what they are), but as if they're in the current zone's non-daylight saving variant. This means that I didn't see the problem as I'm working in GMT0BST.

I've got a fix for this which I'll commit to the CVS server later today.

Paul

On Fri, 14 May 1999, Tom von Alten wrote:

...
> With hm_reverse = 1, the thread and date indexes show the newest message at
> the bottom of the stack, with the rest in proper reverse order. So, for
> the first 5 messages (none of them replies), the order goes:
>
> 0 0 1 2 3
> 1 0 1 2
> 2 0 1
> 3 0
> 4
>
> This was true for 2a20, also. With the simpler date format, the following
> jumped out at me, with 4 messages sent in the course of 3 minutes just
> before 1pm local time (MDT, 6 hours behind UTC):
>
> Third message 14 May 1999 19:56:28
> Second message 14 May 1999 19:55:18
> Start over with 2a21 14 May 1999 19:54:56
> 4th message 14 May 1999 12:56:50
>
> When the 5th message arrives, the 4th message date gets converted to BST (!
> I can understand UTC, but BST? Seems quite strange, with my system sitting
> in Idaho) and the stack is:
>
> 4th message 14 May 1999 19:56:50
> Third message 14 May 1999 19:56:28
> Second message 14 May 1999 19:55:18
> Start over with 2a21 14 May 1999 19:54:56
> 5th message 14 May 1999 13:03:42
... Received on Tue 18 May 1999 12:12:48 PM GMT