Get also accepts build flags to control the installation. See 'go help build'.
+When checking out a new package, get creates the target directory
+GOPATH/src/<import-path>. If the GOPATH contains multiple entries,
+get uses the first one. See 'go help gopath'.
+
When checking out or updating a package, get looks for a branch or tag
that matches the locally installed version of Go. The most important
rule is that if the local installation is running version "go1", get
when go get checks out or updates a Git repository,
it also updates any git submodules referenced by the repository.
+Get never checks out or updates code stored in vendor directories.
+
For more about specifying packages, see 'go help packages'.
For more about how 'go get' finds source code to
Get also accepts build flags to control the installation. See 'go help build'.
+When checking out a new package, get creates the target directory
+GOPATH/src/<import-path>. If the GOPATH contains multiple entries,
+get uses the first one. See 'go help gopath'.
+
When checking out or updating a package, get looks for a branch or tag
that matches the locally installed version of Go. The most important
rule is that if the local installation is running version "go1", get
when go get checks out or updates a Git repository,
it also updates any git submodules referenced by the repository.
+Get never checks out or updates code stored in vendor directories.
+
For more about specifying packages, see 'go help packages'.
For more about how 'go get' finds source code to