On Wed, Nov 26, 2008 at 4:19 PM, Gustavo De Nardin <span dir="ltr"><<a href="mailto:gustavodn@gmail.com">gustavodn@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> The cases are specified through 2038 (the maximum year associated with a signed, 32-bit time_t value).<br>
> After that (through year "max") the rules say that DST ends the third Sunday of February every year; this is wrong by a week in some cases but is better than nothing.<br>
<br>
Just a note.. personally I don't think a knowingly wrong rule is<br>
"better than nothing", it forces the sysadmin to fix the clock 2<br>
times. I think when there's no good rule "forever", make it apply only<br>
for the known cases and leave it alone so the admin can easily handle<br>
it on his own if needed. Not gonna happen anytime soon in this case,<br>
but happened almost every year in Brazil before this new rule.</blockquote><div><br>I second that.<br><br><br>Rodrigo Severo<br><br></div></div><br>