#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):

 Oh, the reason it's invalid is that the system's timezone databases know
 when DST start and end in your timezone.  In fact, the time_t returned by
 mktime() is the same whether or not your current time is in DST. THis is
 not worded precisely, I'll try again:

 In other words, the time_t returned by mktime() called on the result of
 localtime() is always the GMT time plus your GMT offset IN STANDARD TIME.
 The system just interprets that differently (e.g. when you call ctime() on
 it) depending on whether your system's configured time zone is honoring
 DST or not at the specified time.

 I hope that makes sense, even as I fear it does not... :-)

 At the least, this is how it behaves on Linux.  I tried it on a couple of
 recent Ubuntu installs, as well as an older CentOS install.  I have no
 other Unixen to test on, sadly. :-(

--
Ticket URL: <https://dev.mutt.org/trac/ticket/3890#comment:7>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Reply via email to