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.

Sign up for GitHub

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

Jump to bottom

in GMime 4.0, timestamps should use some sort of robust/native GLib representations #73

Open
dkg opened this issue Dec 9, 2019 · 0 comments
Open

in GMime 4.0, timestamps should use some sort of robust/native GLib representations #73

dkg opened this issue Dec 9, 2019 · 0 comments

Comments

@dkg
Copy link
Contributor

dkg commented Dec 9, 2019

This is an API change recommendation for GMime 4.0. Rather than relying on the problematic time_t legacy, GMime should take advantage of GLib's native forms of timestamping when representing signatures, expirations, etc.

Anyone using GMime is already using GLib, so GMime should let GLib do the heavy lifting here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dkg