Geoff Clare via austin-group-l at The Open Group wrote in <ZeCd873Er0Y1st1v@localhost>: |Steffen Nurpmeso wrote, on 26 Feb 2024: |>|https://austingroupbugs.net/view.php?id=1797 |> ... |>| (0006689) eblake (manager) - 2024-02-26 19:32 |>| https://austingroupbugs.net/view.php?id=1797#c6689 |> ... |>|[.]inconsistent with existing practice where some implementations \ |>|set it to |>|"GMT"[.] |> |> The TZ project itself as such changed just recently GMT to UTC. |> Hm, 50df7d69f3af5dbb210326b0b25257e48d11983b as of 2022-07-19 |> already, how time flies. I remembered what P. Eggert said, |> however |> |> POSIX is being revised to require this. |> |> Ie this could be some hen and egg, and i think the standard was |> right to go to UTC given GMT is no longer publically used afaik. |> Therefore ... |> So i do not think that GMT should be used in any future wording. | |The main decision point on this was, I think, when it came to light |that the standard explicitly allows "date -u" to write either UTC or |GMT. There are systems where "date -u" writes GMT. | |It came down to a choice of disallowing GMT for "date -u" or allowing |GMT for gmtime() (or making no change) and we felt that if the issue |had come to light during work on bug 1533 (which added tm_zone) we |would likely have allowed both UTC and GMT for gmtime() at that time. | |We didn't want to force anyone to change an existing "GMT" string to |"UTC".
Thanks for the explanation. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
