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

fix regression on issue #320 #435



Copy link

commented Aug 29, 2019

Looks like the relevant changes got left behind in a merge request or similar, so I cherry-picked it.

emcconville and others added 30 commits Aug 2, 2019

This comment has been minimized.

Copy link

commented Aug 30, 2019

Thanks for the effort, but it looks like this is the sum of the next release (still in development) being merged down to the maintenance branch. This gets handled automatically by the release cycle, and doesn't require a merge-request.


This comment has been minimized.

Copy link

commented Aug 30, 2019

ah, that makes sense. Sorry about the giant merge request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.