On 7/28/2026 10:14 AM, Tim Parenti via tz wrote:
On Tue, 28 Jul 2026 at 05:03, Derick Rethans via tz <[email protected]> wrote:

    I see this changes Thule as well. As that's part of Greenland
    (Denmark)
    — are you confident they're going to along with this change?


"Confident" is very much the wrong adjective for this speculative patch.  On the contrary, as is stated in the commentary, this diff is somewhat intentionally maximalist so that folks can prepare for potential changes to the most zones that might be affected by this bill and its potential knock-on effects if other jurisdictions follow suit.  In some cases this is just abbreviations switching to numeric, but in many others assumptions have been made for the sake of exposition.  Many other end-state configurations are possible and, indeed, likelier.

I am reading this speculative patch as a worst case scenario that would allow downstream programmers to test what would happen IF this patch was put into "production". There are several elements that certainly will not happen (for example, an effective date of August 7th, the senate will not act that fast). Break it all in test and see what needs to be fixed in POSIX and other downstreams.

As for Thule Air Force Base (now operating as Pituffik Space Base) the base itself is controlled by the US government and runs on Atlantic Standard / Atlantic Daylight Time. Always one hour advanced of Washington DC. The surrounding town follows base time, separate from the time that would be specified by Greenland or Denmark. It is "possible" that America/Thule would change to a Greenland based time zone but I would not expect it. Nevertheless, for the speculative scenario it might as well be included.

The same for the US states and territories currently not observing daylight time (Puerto Rico, Arizona, Hawaii, Samoa, Guam). I speculate that they will opt out of "permanent DST" - but no change from current isn't a test - they might as well be included.

Reply via email to