aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonathan Amsterdam <jba@google.com>2023-07-11 17:12:33 -0400
committerJonathan Amsterdam <jba@google.com>2023-07-11 21:30:51 +0000
commitaf8f94e3c5885647d6f85d2d5227b5fc6b637c52 (patch)
tree208cc6a60c517a43f81098611ee770734e977ccd
parent3eaee3d5dd55dabf9da571be7a6a4fa05f9dbf29 (diff)
downloadgo-af8f94e3c5885647d6f85d2d5227b5fc6b637c52.tar.gz
go-af8f94e3c5885647d6f85d2d5227b5fc6b637c52.zip
src/README.vendor: s/latest/master/
Update the README to specify the module query "@master" instead of "@latest". Vendoring the highest tagged version is unlikely to be right. Usually one wants to vendor the module at HEAD. Change-Id: Id00d23523a13fd3dcd73d6eacefdf50bcdbfa26e Reviewed-on: https://go-review.googlesource.com/c/go/+/508823 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Jonathan Amsterdam <jba@google.com> Reviewed-by: Bryan Mills <bcmills@google.com>
-rw-r--r--src/README.vendor2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/README.vendor b/src/README.vendor
index 4b6bdb8e74..43821b2900 100644
--- a/src/README.vendor
+++ b/src/README.vendor
@@ -38,7 +38,7 @@ The vendor directory may be updated with 'go mod vendor'.
A typical sequence might be:
cd src
- go get golang.org/x/net@latest
+ go get golang.org/x/net@master
go mod tidy
go mod vendor