aboutsummaryrefslogtreecommitdiff
path: root/src/os/exec/exec.go
diff options
context:
space:
mode:
authorHana (Hyang-Ah) Kim <hyangah@gmail.com>2019-11-23 12:06:21 -0500
committerHyang-Ah Hana Kim <hyangah@gmail.com>2019-11-27 18:42:33 +0000
commitf1c8e2c14ad3e9d0fa62a4698163138e6fb9f7a4 (patch)
treed2d2a0336cb5335e8ed14269a367f654a62eb725 /src/os/exec/exec.go
parentb11d02ef740091d15671a647f876142018613aa4 (diff)
downloadgo-f1c8e2c14ad3e9d0fa62a4698163138e6fb9f7a4.tar.xz
cmd/go: enable -x in go mod download
Lack of logging hinders debugging. Like many other go commands, let's allow users to inspect what is going on underneath. Example: $ GO111MODULE=on GOPROXY=direct GOPATH=`mktemp -d` go mod download -x golang.org/x/tools/gopls@latest mkdir -p /var/folders/bw/6r6k9d113sv1_vvzk_1kfxbm001py5/T/tmp.ykhTiXaS/pkg/mod/cache/vcs # git3 https://go.googlesource.com/tools ... Update #35849 Change-Id: I5577e683ae3c0145b11822df255b210ad9f60c87 Reviewed-on: https://go-review.googlesource.com/c/go/+/208558 Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
Diffstat (limited to 'src/os/exec/exec.go')
0 files changed, 0 insertions, 0 deletions