#3890: mutt_mktime is ambiguous near DST change
---------------------+----------------------
Reporter: vinc17 | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: mutt | Version: 1.7.1
Resolution: | Keywords:
---------------------+----------------------
Comment (by vinc17):
Replying to [comment:4 derekmartin]:
> Honestly I'm unsure if GMT0 is better than GMT or not... It's been a
long while now since I regularly had occasion to access a wide variety of
Unix flavors, but s far as I was aware, "GMT" was the older, longer
supported value, and seemed more likely to work everywhere to me for that
reason. But if you think GMT0 is widely adopted, go with that. If either
turns out to cause problems it's easy enough to fix later. Timezone
values was one of those annoyingly non-standard things on older Unix
systems, but I thought GMT always worked..
Well, according to https://www.postgresql.org/message-
id/[email protected] "GMT" does not
work on Tru64 Unix. It is said: "In particular, where Linux accepts GMT
and reads it to be GMT0, under Tru64 Unix the correct behaviour _requires_
the use of GMT0."
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3890#comment:5>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
