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

Fixes on LAST-MODIFIED and DTSTAMP #944

Merged
merged 4 commits into from
Sep 13, 2018

Conversation

DeepDiver1975
Copy link
Member

  • Update LAST-MODIFIED property on each and every change
  • Update DTSTAMP property together with LAST-MODIFIED
  • Use UTC on LAST-MODIFIED, DTSTAMP and CREATED

- Update DTSTAMP property together with LAST-MODIFIED
- Use UTC on LAST-MODIFIED, DTSTAMP and CREATED
@DeepDiver1975 DeepDiver1975 force-pushed the bugfix/set-dtstamp-and-last-modified-correctly branch from db76664 to eba232a Compare September 12, 2018 20:16
@DeepDiver1975 DeepDiver1975 force-pushed the bugfix/set-dtstamp-and-last-modified-correctly branch from f2158b1 to e476f27 Compare September 13, 2018 11:14
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.1%) to 52.931% when pulling e476f27 on bugfix/set-dtstamp-and-last-modified-correctly into 154c3f9 on master.

@DeepDiver1975
Copy link
Member Author

calendar.tar.gz

@Julian1998
Copy link
Contributor

Does it also fix #943 ?

@DeepDiver1975
Copy link
Member Author

Does it also fix #943 ?

yes - fixes #943

@DeepDiver1975 DeepDiver1975 merged commit 2e78877 into master Sep 13, 2018
@DeepDiver1975 DeepDiver1975 deleted the bugfix/set-dtstamp-and-last-modified-correctly branch September 13, 2018 14:25
@DeepDiver1975 DeepDiver1975 mentioned this pull request Sep 19, 2018
@Aceto1
Copy link

Aceto1 commented Oct 29, 2018

This probably fixes #659 too, right?

@DeepDiver1975
Copy link
Member Author

This probably fixes #659 too, right?

indeed - thx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants