-
Notifications
You must be signed in to change notification settings - Fork 697
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
Make a release (buildable with GHC-8.10.1) #6799
Comments
I think it would be great if the patch #6623 would be backported. Sorry if I am being pushy and annoying regarding this :/ |
The hack for #5119 should definitely be backported |
why that hack cannot be turned into a proper fix. I don’t like the idea of indefinitely backporting hack. Please make a PR to master with a commit to master who it should be fixed and why it cannot be fixed now. It’s annoying but not deadly.
No long-lived hacks, Please.
… On 22. May 2020, at 14.58, Francesco Gazzetta ***@***.***> wrote:
The hack for #5119 should definitely be backported
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I released Therefore closing. |
The 3.2 branch is buildable with GHC-8.10.1 so we should make a release.
At the moment this is the only issue in 3.2.1.0 milestone. But if we need something backported, please speak up!
The text was updated successfully, but these errors were encountered: