From: "Cygwin tzcode/tzdata Maintainer" <Brian.Inglis@Shaw.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: tzcode, tzdata 2023c
Date: Tue, 28 Mar 2023 17:19:47 -0600 [thread overview]
Message-ID: <20230328171947.44552-1-Brian.Inglis@Shaw.ca> (raw)
The following packages have been upgraded in the Cygwin distribution:
* tzcode 2023c
* tzdata 2023c
The Time Zone Database (often called tz, tzdb, or zoneinfo) contains
data that represents the history of local time for many locations around
the world, and supports conversion of UTC time to local time at those
locations to allow display of those local times. It is updated
periodically to reflect changes made by political bodies to summer
daylight saving time rules, UTC offsets, and time zone boundaries.
The tzcode package provides the tzselect, zdump, and zic utilities.
For more information, see the project home page:
https://www.iana.org/time-zones
For more details on changes, see the announcement or below:
https://mm.icann.org/pipermail/tz-announce/2023-March/000079.html
Release 2023c 2023-03-28
* This release's code and data are identical to 2023a and reverts all
changes made in 2023b. Lebanon's spring-forward transition was
previously scheduled for March 25/26. Then Lebanon's government
announced that the spring-forward transition would be delayed until
April 20. Then after the weekend reverted the change. So other than
commentary, all changes are reverted, as that appears to be the best
of a bad set of short-notice choices for modeling this week's daylight
saving chaos in Lebanon.
reply other threads:[~2023-03-28 23:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230328171947.44552-1-Brian.Inglis@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).