Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed leap year handling by reworking upb_mktime() -> upb_timegm(). #6693

Closed
wants to merge 1 commit into from

Conversation

haberman
Copy link
Member

The new function name also better reflects the semantics of the
function. Like timegm(), this function always converts to/from
UTC, not local time.

The new function name also better reflects the semantics of the
function.  Like timegm(), this function always converts to/from
UTC, not local time.
Copy link
Contributor

@TeBoring TeBoring left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also add some conformance test?

@TeBoring
Copy link
Contributor

Could you send a change to 3.10.x?

@haberman
Copy link
Member Author

I'm happy to add conformance tests later, but this is a data loss bug that I want to fix now. We can add conformance tests after.

@haberman
Copy link
Member Author

Here is a PR against 3.10.x: #6695

@TeBoring
Copy link
Contributor

Since the other PR has been merged to 3.10.x which will be merged back to master, this is no longer necessary.

@TeBoring TeBoring closed this Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants