#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 derekmartin):
Replying to [comment:3 vinc17]:
> Replying to [comment:2 derekmartin]:
> I agree. But I suppose that by saying "set 'TZ' back", the manual
implicitly means to
restore the TZ status (i.e. unset it if it was unset, else set it to the
old value).
Sure... But it's a detail that could get overlooked, so I wanted to call
it out explicitly.
> Instead of "GMT", shouldn't "GMT0" (for compatibility with old systems)
or "UTC0" be used?
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..
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3890#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
