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

Properly parse carddav address-data #1025

Merged
merged 1 commit into from Jan 19, 2018
Merged

Properly parse carddav address-data #1025

merged 1 commit into from Jan 19, 2018

Conversation

DeepDiver1975
Copy link
Member

fixes #1017

Copy link
Member

@staabm staabm left a comment

Choose a reason for hiding this comment

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

Lgtm

@mbiebl
Copy link
Contributor

mbiebl commented Jan 19, 2018

@DeepDiver1975 seems to work fine. Thanks!

Since the 3.2 and 3.3 branch are also affected, could you please pull that fix into those branches as well?
Even more awesome would be, if there was a new 3.2.3 release with that fix.

@DeepDiver1975
Copy link
Member Author

could you please pull that fix into those branches as well?

pull requests are already open

Even more awesome would be, if there was a new 3.2.3 release with that fix.

we need to release - there are other fixes which need to be shipped.
I'll be looking into this these days.

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.

Woops, something's gone wrong! The CardDAV server returned the http status code 500.
3 participants