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

syscall: Go Build Fails on Windows With Long Paths [1.10 backport] #25292

Closed
gopherbot opened this issue May 8, 2018 · 2 comments
Closed

syscall: Go Build Fails on Windows With Long Paths [1.10 backport] #25292

gopherbot opened this issue May 8, 2018 · 2 comments

Comments

@gopherbot
Copy link

@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.

@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label May 8, 2018
@gopherbot gopherbot added this to the Go1.10.3 milestone May 8, 2018
@FiloSottile FiloSottile modified the milestones: Go1.10.3, Go1.10.4 Jun 7, 2018
@andybons andybons modified the milestones: Go1.10.4, Go1.10.5 Aug 24, 2018
@katiehockman katiehockman removed the CherryPickCandidate Used during the release process for point releases label Oct 30, 2018
@katiehockman
Copy link
Contributor

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.

@bradfitz
Copy link
Contributor

I don't care about Go 1.10 now that Go 1.11 is out.

@golang golang locked and limited conversation to collaborators Oct 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants