public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug time/29951] daylight variable not set correctly if last DST change coincides with offset change Date: Thu, 05 Jan 2023 17:43:38 +0000 [thread overview] Message-ID: <bug-29951-131-7AszJ81OjF@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29951-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29951 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Target Milestone|--- |2.37 Resolution|--- |FIXED --- Comment #2 from Florian Weimer <fweimer at redhat dot com> --- Fixed via: commit 35141f304e319109c322f797ae71c0b9420ccb05 Author: Florian Weimer <fweimer@redhat.com> Date: Thu Jan 5 18:21:25 2023 +0100 time: Set daylight to 1 for matching DST/offset change (bug 29951) The daylight variable is supposed to be set to 1 if DST is ever in use for the current time zone. But __tzfile_read used to do this: __daylight = rule_stdoff != rule_dstoff; This check can fail to set __daylight to 1 if the DST and non-DST offsets happen to be the same. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-01-05 17:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-02 9:51 [Bug time/29951] New: " fweimer at redhat dot com 2023-01-02 9:51 ` [Bug time/29951] " fweimer at redhat dot com 2023-01-02 11:19 ` fweimer at redhat dot com 2023-01-05 17:43 ` fweimer at redhat dot com [this message]
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=bug-29951-131-7AszJ81OjF@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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).