Fix timezone issues#1018
Closed
binaryfire wants to merge 3 commits into
Closed
Conversation
dosubot
Bot
added
size:XS
Author
|
Hi @dr5hn. Would it be possible to take a look at this when you have time? There are more fixes required for TZ data but I'm waiting till this gets merged. I'll submit a second PR with the other corrections. |
Owner
|
Changes has been merged in #1022 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @dr5hn
Please ignore the change I submitted via the CSC Update Tool. PRs are more convenient for me.
Summary of changes:
Europe/KievtoEurope/KyivEurope/UzhgorodandEurope/ZaporozhyePacific/EnderburytoPacific/KantontzNameentries ending with(North America[1,[3,[4and[6fromtzNameentriesUTC±00withUTC±00:00so allgmtOffsetNameentries are consistentResolves issues:
#1017
#1016
#1015