public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: "Cygwin tzcode/tzdata Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: tzcode, tzdata 2022e
Date: Sat, 15 Oct 2022 13:06:02 -0600	[thread overview]
Message-ID: <20221015130602.6129-1-Brian.Inglis@SystematicSW.ab.ca> (raw)

The following packages have been upgraded in the Cygwin distribution:

* tzcode	2022e
* tzdata	2022e

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/2022-October/000074.html


Release 2022e	2022-10-11

Briefly:

* Jordan and Syria switch from +02/+03 with DST to year-round +03.

Changes to future timestamps

* Jordan and Syria are abandoning the DST regime and are changing to
  permanent +03, so they will not fall back from +03 to +02 on
  2022-10-28.

Changes to past timestamps

* On 1922-01-01 Tijuana adopted standard time at 00:00, not 01:00.

Changes to past time zone abbreviations and DST flags

* The temporary advancement of clocks in central Mexico in summer
  1931 is now treated as daylight saving time, instead of as two
  changes to standard time.


                 reply	other threads:[~2022-10-15 19:08 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=20221015130602.6129-1-Brian.Inglis@SystematicSW.ab.ca \
    --to=brian.inglis@systematicsw.ab.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).