Github user fhueske commented on the issue:
https://github.com/apache/flink/pull/2704
Thanks for the fix @Makman2!
Merging
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
ena
Github user Makman2 commented on the issue:
https://github.com/apache/flink/pull/2704
Feel free to cherry-pick my commit into your branch and close this PR :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your projec
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/2704
I keep an `_minutiae` branch and push that every few months, typically
after a release. There are fixed costs at each level of Flink's ticketing /
pull request / verify / commit process.
---
Github user Makman2 commented on the issue:
https://github.com/apache/flink/pull/2704
Though I wouldn't fix more than this one (except I stumble over some typos
again) :3
Is there already a larger ticket? @greghogan
---
If your project is set up for it, you can reply to this ema
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/2704
I'd recommend collecting typographical and grammatical errors within
comments into a larger ticket and pull request.
---
If your project is set up for it, you can reply to this email and have your
