From: James Cloos <cloos@jhcloos.com>
To: Rich Felker <dalias@libc.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, musl@lists.openwall.com, tz@iana.org
Subject: Re: [musl] Re: [tz] Weird PST8PDT and EST5EDT behavior on Alpine Linux
Date: Fri, 08 Mar 2024 19:09:03 -0500 [thread overview]
Message-ID: <m3frx06zc0.fsf@nitrogen.jhcloos.org> (raw)
In-Reply-To: <20240308190243.GP4163@brightrain.aerifal.cx> (Rich Felker's message of "Fri, 8 Mar 2024 14:02:44 -0500")
>>>>> "PE" == Paul Eggert writes:
>>>>> "RF" == Rich Felker writes:
PE> EST5EDT,M3.2.0,M11.1.0
RF> Yes, this i the form I've used in the past before we had zoneinfo
RF> support.
now that i think about it (it has been >5 years since i got that clock)
i ended up with that form, too. but then changed the setting to match
the manufacturer's subsequent recommendation.
(it was long enough ago that i had to ssh into the clock and grep(1) /etc
to remind myself of its tz configuration...)
-JimC
--
James Cloos <cloos@jhcloos.com>
OpenPGP: https://jhcloos.com/0x997A9F17ED7DAEA6.asc
next prev parent reply other threads:[~2024-03-09 0:09 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 ` Đ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
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 [this message]
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=m3frx06zc0.fsf@nitrogen.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=dalias@libc.org \
--cc=eggert@cs.ucla.edu \
--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).