<div dir="ltr"><div><div>For the immediate question:<br><br>> I'm not
quite sure what 'goback' and 'goahead' are supposed to do.<br><br></div>"goback" indicates that there's a 400-year pattern to the stuff at the start of the transition table that can be extrapolated backward through time; "goahead" indicates that there's a 400-year pattern to the stuff at the end that can be extrapolated forward. When a table generated from an environment variable does indeed cover 400 years, both goahead and goback should be set.<br><br></div> @dashdashado<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 11, 2017 at 3:55 PM, Paul Eggert <span dir="ltr"><<a href="mailto:eggert@cs.ucla.edu" target="_blank">eggert@cs.ucla.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 01/11/2017 11:39 AM, Arthur David Olson wrote:<br>
<br>
> for such environment variables, in what year should application of<br>
> daylight saving start (or should it apply to all years, no matter how<br>
> far in the past)?<br>
<br>
</span>Surely it should apply to all years. POSIX doesn't require this (POSIX<br>
specifies only behavior starting in 1970) but it would be odd for a<br>
permanent rule to spring into action only after 1969.<br>
<br>
The attached proposed patch does that, and fixes the problem for Kees<br>
Dekker's case. Does this look like the right thing in general? I'm not<br>
quite sure what 'goback' and 'goahead' are supposed to do.<br>
<br>
</blockquote></div><br></div>