aboutsummaryrefslogtreecommitdiff
path: root/_content/doc/modules/managing-dependencies.md
diff options
context:
space:
mode:
authorRoger Peppe <rogpeppe@gmail.com>2022-10-06 17:38:44 +0100
committerroger peppe <rogpeppe@gmail.com>2022-10-06 23:34:32 +0000
commitba3d5cf5ff8abac0ae00c452c85efeea6bba6f20 (patch)
tree5b24c4f1e6fbf2da6c007bf4602791998babbb8e /_content/doc/modules/managing-dependencies.md
parent6438748656032e812b5e2c94f837f2a6c86e3c35 (diff)
downloadgo-x-website-ba3d5cf5ff8abac0ae00c452c85efeea6bba6f20.tar.xz
_content/{ref,doc}: remove -d from go get examples
The `-d` flag to `go get` in module mode is a no-op, as witness the following comment from the code: // TODO(#43684): in the future (Go 1.20), warn that -d is a no-op. if !*getD { base.Fatalf("go: -d flag may not be disabled") } Thus it's misleading, so remove it. Change-Id: I0cf61d61b561d010d00f6044a5c07ca8f3bd117f Reviewed-on: https://go-review.googlesource.com/c/website/+/439695 Reviewed-by: Ian Lance Taylor <iant@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Ian Lance Taylor <iant@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
Diffstat (limited to '_content/doc/modules/managing-dependencies.md')
-rw-r--r--_content/doc/modules/managing-dependencies.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/_content/doc/modules/managing-dependencies.md b/_content/doc/modules/managing-dependencies.md
index 7752dd83..802e9c35 100644
--- a/_content/doc/modules/managing-dependencies.md
+++ b/_content/doc/modules/managing-dependencies.md
@@ -166,7 +166,7 @@ Go guarantees that the following strings won't be used in package names.
- `test` -- You can use `test` as a module path prefix for a module whose code
is designed to locally test functions in another module.
-
+
Use the `test` path prefix for modules that are created as part of a test.
For example, your test itself might run `go mod init test` and then set up
that module in some particular way in order to test with a Go source code
@@ -370,7 +370,7 @@ to ensure that requirements described by the file remain consistent:
```
$ go mod edit -replace=example.com/theirmodule@v0.0.0-unpublished=../theirmodule
-$ go get -d example.com/theirmodule@v0.0.0-unpublished
+$ go get example.com/theirmodule@v0.0.0-unpublished
```
**Note:** When you use the replace directive, Go tools don't authenticate