Skip to content
This repository was archived by the owner on Nov 17, 2023. It is now read-only.

Conversation

@marcoabreu
Copy link
Contributor

Reverts #12191

We reverted the underlying change and thus this PR is not necessary (and is no longer compatible)

@marcoabreu
Copy link
Contributor Author

@piyushghai @cclaus fyi

@haojin2
Copy link
Contributor

haojin2 commented Aug 17, 2018

Just wonder why are you also reverting a bunch of other un-related changes? (I'm taking a look at the commits part)

@marcoabreu
Copy link
Contributor Author

marcoabreu commented Aug 17, 2018

I just pressed the revert button, I don't know what GitHub is doing there ._.

Please have a look at the diff, it looks good to me

@marcoabreu
Copy link
Contributor Author

I'm only on my phone right now, so I can't make a revert with the command line. In the end, the commits will be squashed so it should not make much of a difference as long as the diff is good

@haojin2
Copy link
Contributor

haojin2 commented Aug 17, 2018

@marcoabreu Could you do a double-check please? Cause one of the commits on the list shows that it's reverting an important fix for the next release.

@piyushghai
Copy link
Contributor

The file diff looks good as it was the only change in that PR.
Not sure, why the other commits are showing up here.

@marcoabreu
Copy link
Contributor Author

If you click on the commits in this PR, you will see that they are all empty except the last one. Please feel free to make a proper revert with only one commit and open a new PR. I'm sorry that I can't do it myself right now.

@piyushghai
Copy link
Contributor

Check PR #12231 .
That includes just one commit required.
@marcoabreu Feel free to close this one.

@marcoabreu
Copy link
Contributor Author

Thank you!

@marcoabreu marcoabreu closed this Aug 17, 2018
@szha szha deleted the revert-12191-patch-2 branch August 24, 2018 23:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants