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: get -v missing from usage #16719

Closed
JesseWeinstein opened this issue Aug 16, 2016 · 3 comments
Closed

cmd/go: get -v missing from usage #16719

JesseWeinstein opened this issue Aug 16, 2016 · 3 comments
Milestone

Comments

@JesseWeinstein
Copy link

On go version go1.5.1 linux/amd64, the first line of go get --help is: usage: get [-d] [-f] [-fix] [-insecure] [-t] [-u] [build flags] [packages] which doesn't mention the -v flag, even though it does work, and so should be documented. The function of -v appears to be to make the output more verbose.

This was originally reported by @epitron, here #12197 (comment) -- but no-one seems to have made the requested separate bug till now.

@bradfitz bradfitz added this to the Go1.8 milestone Aug 16, 2016
@gopherbot
Copy link

CL https://golang.org/cl/27118 mentions this issue.

@JesseWeinstein
Copy link
Author

JesseWeinstein commented Aug 17, 2016

Nice quick response! I'm not sure I fully agree with documenting the flag both in the list of build flags, and in the detailed list on go get (but not on clean, install, list, run or test) -- but since this bug is now closed, I guess that's another issue, and one I don't feel like opening. :-/

I think documenting the list of build flags in each of the commands that accept them, and referring to go help build for the detailed descriptions, would be better. But, like you said, "docs are hard".

@rakyll
Copy link
Contributor

rakyll commented Oct 3, 2016

I am thinking about writing a proposal for reorganizing the flags. Current way of mentioning build tags and delegating users to go help build is not working especially for the new comers.

@golang golang locked and limited conversation to collaborators Oct 3, 2017
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

4 participants