<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 25 Feb 2019, at 3:42 AM, Paul Eggert wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">"New" relative to what? The data entries for Asia/Dushanbe itself haven't changed since 2016-08-21.<br></span></blockquote></div><br><div> My apologies, relative to back when initial creation, and was tz list bug reporting (iana just took over tz).</div><div>This was not your mistake! </div><div>This was my error handling "new" timezone formats, relative to when you did not use literals/rule based "FORMAT"s</div><div>with std/dst packed, and numeric values in that field.</div><div> Again, my bad, I'm sorry. Thanks for spotting my bug.</div></body></html>