From: Russ Allbery <eagle@eyrie.org>
To: Guy Harris <gharris@sonic.net>
Cc: Rich Felker <dalias@libc.org>, Ian Abbott via tz <tz@iana.org>,
musl@lists.openwall.com
Subject: [musl] Re: [tz] [musl] Re: Weird PST8PDT and EST5EDT behavior on Alpine Linux
Date: Tue, 05 Mar 2024 14:03:23 -0800 [thread overview]
Message-ID: <87r0gopc9g.fsf@hope.eyrie.org> (raw)
In-Reply-To: <BB11A375-58EC-421B-AAEA-B35B034146D0@sonic.net> (Guy Harris's message of "Tue, 5 Mar 2024 13:37:36 -0800")
Guy Harris <gharris@sonic.net> writes:
> On Mar 5, 2024, at 12:56 PM, Russ Allbery via tz <tz@iana.org> wrote:
>> but for the record, PST8PDT was for support for very old commercial
>> UNIXes where I believe that was the only recognized style of TZ
>> setting, and I'm pretty dubious that the POSIX-introduced :PST8PDT
>> syntax would work there.
> That TZ syntax dates back at least to System III:
> http://www.bitsavers.org/pdf/att/unix/System_III/UNIX_Users_Manual_Release_3_Jun80.pdf
> (see CTIME(3C)), which did not support anything tzdb-related, and didn't
> even support the more elaborate POSIX TZ syntax to include rules.
I don't see any reference to the leading colon in that documentation. Am
I just missing something? It seems to support what I said: PST8PDT was
supported, but :PST8PDT was not.
If an environment variable named TZ is present, asctime uses the
contents of the variable to override the default time zone. The value
of TZ must be a three-letter time zone name, followed by a number
representing the difference between local time and Greenwich time in
hours, followed by an optional three-letter name for a daylight time
zone. For example, the setting for New Jersey would be EST5EDT.
--
Russ Allbery (eagle@eyrie.org) <https://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2024-03-05 22:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87edcqv69m.fsf@hope.eyrie.org>
2024-03-05 3:52 ` [musl] Re: [tz] " Đoàn Trần Công Danh
2024-03-05 4:31 ` Paul Eggert
2024-03-05 20:12 ` Rich Felker
2024-03-05 20:56 ` Russ Allbery
2024-03-05 21:37 ` [musl] Re: [tz] [musl] " Guy Harris
2024-03-05 22:03 ` Russ Allbery [this message]
2024-03-05 22:12 ` Guy Harris
2024-03-05 22:31 ` Russ Allbery
2024-03-06 15:39 ` James Cloos
2024-03-08 17:46 ` [musl] Re: [tz] " Paul Eggert
2024-03-08 19:02 ` Rich Felker
2024-03-09 0:09 ` James Cloos
2024-03-09 1:57 ` [musl] Re: [tz] [musl] " Guy Harris
2024-03-08 18:39 ` Guy Harris
2024-03-08 19:05 ` [musl] Re: [tz] " Paul Eggert
2024-03-09 0:03 ` [musl] " James Cloos
2024-03-06 0:47 ` [musl] Re: [tz] " Paul Eggert
2024-03-06 1:54 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0gopc9g.fsf@hope.eyrie.org \
--to=eagle@eyrie.org \
--cc=dalias@libc.org \
--cc=gharris@sonic.net \
--cc=musl@lists.openwall.com \
--cc=tz@iana.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).