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
@bradfitz requested issue #18468 to be considered for backport to the next 1.10 minor release.
Edit: I just saw the 1.11 milestone, how can I have access to this fix before the release? You could patch it in and recompile Go if it's urgent. But I suppose we could also backport it to Go 1.10.x if we do another one. @gopherbot, please backport.
Edit: I just saw the 1.11 milestone, how can I have access to this fix before the release?
You could patch it in and recompile Go if it's urgent.
But I suppose we could also backport it to Go 1.10.x if we do another one.
@gopherbot, please backport.
The text was updated successfully, but these errors were encountered:
This doesn't seem like a serious issue without any workarounds, so I'm going to reject this cherry pick candidate. @bradfitz lmk if you disagree since you created the original backport request.
Sorry, something went wrong.
I don't care about Go 1.10 now that Go 1.11 is out.
No branches or pull requests
@bradfitz requested issue #18468 to be considered for backport to the next 1.10 minor release.
The text was updated successfully, but these errors were encountered: