Skip to content

Commit 71ed71b

Browse files
ianlancetaylorgopherbot
authored andcommitted
README: don't recommend go get
These days people will just import the packages and the go tool will do the right thing. We don't need to explain it. Add a pointer to the git repo, though. For golang/go#62645 Change-Id: I8b1e4a877bd83fe6891688a44d27a6c7902c8979 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/624155 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: Ian Lance Taylor <iant@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> Auto-Submit: Ian Lance Taylor <iant@google.com> Reviewed-by: Roland Shoemaker <roland@golang.org>
1 parent 750a45f commit 71ed71b

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

README.md

+5-8
Original file line numberDiff line numberDiff line change
@@ -2,20 +2,17 @@
22

33
[![Go Reference](https://pkg.go.dev/badge/golang.org/x/crypto.svg)](https://pkg.go.dev/golang.org/x/crypto)
44

5-
This repository holds supplementary Go cryptography libraries.
6-
7-
## Download/Install
8-
9-
The easiest way to install is to run `go get -u golang.org/x/crypto/...`. You
10-
can also manually git clone the repository to `$GOPATH/src/golang.org/x/crypto`.
5+
This repository holds supplementary Go cryptography packages.
116

127
## Report Issues / Send Patches
138

149
This repository uses Gerrit for code changes. To learn how to submit changes to
15-
this repository, see https://golang.org/doc/contribute.html.
10+
this repository, see https://go.dev/doc/contribute.
11+
12+
The git repository is https://go.googlesource.com/crypto.
1613

1714
The main issue tracker for the crypto repository is located at
18-
https://github.com/golang/go/issues. Prefix your issue with "x/crypto:" in the
15+
https://go.dev/issues. Prefix your issue with "x/crypto:" in the
1916
subject line, so it is easy to find.
2017

2118
Note that contributions to the cryptography package receive additional scrutiny

0 commit comments

Comments
 (0)