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

cmd/go: "v1.x.y is not a tag" when .gitconfig sets log.decorate to full [1.17 backport] #51351

Open
gopherbot opened this issue Feb 24, 2022 · 0 comments
Labels
CherryPickCandidate GoCommand
Milestone

Comments

@gopherbot
Copy link

@gopherbot gopherbot commented Feb 24, 2022

@bcmills requested issue #51312 to be considered for backport to the next 1.17 minor release.

@gopherbot, please backport to Go 1.16 and 1.17. This causes erroneous error messages (which may be confusing for users), and the underlying cause is not easy to diagnose.

@gopherbot gopherbot added the CherryPickCandidate label Feb 24, 2022
@gopherbot gopherbot added this to the Go1.17.8 milestone Feb 24, 2022
@dmitshur dmitshur added the GoCommand label Feb 24, 2022
@bcmills bcmills changed the title cmd/go: unexpected "v1.x.y is not a tag" after update to Go 1.16.14 [1.17 backport] cmd/go: "v1.x.y is not a tag" when .gitconfig sets log.decorate to full [1.17 backport] Feb 24, 2022
@cagedmantis cagedmantis removed this from the Go1.17.8 milestone Mar 3, 2022
@cagedmantis cagedmantis added this to the Go1.17.9 milestone Mar 3, 2022
@dmitshur dmitshur removed this from the Go1.17.9 milestone Apr 12, 2022
@dmitshur dmitshur added this to the Go1.17.10 milestone Apr 12, 2022
@heschi heschi removed this from the Go1.17.10 milestone May 10, 2022
@heschi heschi added this to the Go1.17.11 milestone May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CherryPickCandidate GoCommand
Projects
None yet
Development

No branches or pull requests

4 participants