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

Indigo backports #1143

Merged
merged 1 commit into from
Aug 21, 2017
Merged

Indigo backports #1143

merged 1 commit into from
Aug 21, 2017

Conversation

wjwwood
Copy link
Member

@wjwwood wjwwood commented Aug 21, 2017

@wjwwood
Copy link
Member Author

wjwwood commented Aug 21, 2017

Actually #1139 doesn't make sense (it didn't apply cleanly, but I tried to fix it up). I will drop it from the backports.

@dhood
Copy link
Contributor

dhood commented Aug 21, 2017

Oops, I didn't check if there'd been refactoring before putting the 'needs back port' label on 1139. I'll just put that label on trivial back ports in the future, yeah?

@wjwwood
Copy link
Member Author

wjwwood commented Aug 21, 2017

@dhood if you think the fix is worth the more complex back porting you're welcome to try and do it. I was just grabbing the trivial ones. It might be appropriate to put the label on non-trivial backports if they are important.

@wjwwood wjwwood merged commit 88e9aa1 into indigo-devel Aug 21, 2017
@wjwwood wjwwood deleted the indigo-backports branch August 21, 2017 20:54
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