Skip to content

[release-0.5] Backport of #21069 #21080

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

Merged
merged 3 commits into from
May 3, 2017
Merged

Conversation

martinholters
Copy link
Member

No description provided.

@tkelman
Copy link
Contributor

tkelman commented Mar 18, 2017

cherry-pick with -x please

Backport of #21069.

(cherry picked from commit f65f273)
Backport of #21069.

(cherry picked from commit 038390b)
Backport of #21069.

(cherry picked from commit 1594692)
@martinholters
Copy link
Member Author

Like so?

@tkelman
Copy link
Contributor

tkelman commented Mar 20, 2017

yep. I'll want to run things through pkgeval before merging them to the release branch.

@martinholters
Copy link
Member Author

Sure, no hurries from my side.

@tkelman tkelman changed the base branch from release-0.5 to tk/backports-0.5.2 May 2, 2017 17:29
@tkelman tkelman force-pushed the tk/backports-0.5.2 branch 2 times, most recently from 172ff0d to 0d5acba Compare May 3, 2017 05:50
@tkelman tkelman merged commit c282224 into tk/backports-0.5.2 May 3, 2017
@tkelman tkelman deleted the mh/backport_21069 branch May 3, 2017 06:44
@tkelman
Copy link
Contributor

tkelman commented May 6, 2017

noting that this was reverted in #21684 since it may have caused performance regressions, if there will be a 0.5.3 it may be worth testing that again

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.

2 participants