You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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".
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.
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.
The text was updated successfully, but these errors were encountered: