Re: Time zone bug

2017-05-01 Thread Brian Inglis
On 2017-05-01 09:25, cyg Simple wrote: > On 4/30/2017 7:19 PM, Steven Penny wrote: >> On Sun, 30 Apr 2017 17:37:00, Ken Brown wrote: >>> As a result of a failing emacs test, I came across the following: >>> >>> $ TZ='NZST-12NZDT,M9.5.0,M4.1.0/3' date -d@0 +'%Y-%m-%d %H:%M:%S %z (%Z)' >>> 1970-01-01

Re: Time zone bug

2017-05-01 Thread cyg Simple
On 4/30/2017 7:19 PM, Steven Penny wrote: > On Sun, 30 Apr 2017 17:37:00, Ken Brown wrote: >> As a result of a failing emacs test, I came across the following: >> >> $ TZ='NZST-12NZDT,M9.5.0,M4.1.0/3' date -d@0 +'%Y-%m-%d %H:%M:%S %z (%Z)' >> 1970-01-01 12:00:00 +1200 (NZST) >> >> The same command

Re: Time zone bug

2017-04-30 Thread Steven Penny
On Sun, 30 Apr 2017 17:37:00, Ken Brown wrote: As a result of a failing emacs test, I came across the following: $ TZ='NZST-12NZDT,M9.5.0,M4.1.0/3' date -d@0 +'%Y-%m-%d %H:%M:%S %z (%Z)' 1970-01-01 12:00:00 +1200 (NZST) The same command on Linux yields "1970-01-01 13:00:00 +1300 (NZDT)", which

Time zone bug

2017-04-30 Thread Ken Brown
As a result of a failing emacs test, I came across the following: $ TZ='NZST-12NZDT,M9.5.0,M4.1.0/3' date -d@0 +'%Y-%m-%d %H:%M:%S %z (%Z)' 1970-01-01 12:00:00 +1200 (NZST) The same command on Linux yields "1970-01-01 13:00:00 +1300 (NZDT)", which is correct according to Paul Eggert (https://li