3 Commits

Include renames

Author	SHA1	Message	Date
Ian Lance Taylor	71ed71b4fa	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>	2024-11-04 00:10:25 +00:00
Julie Qiu	5f87f3452a	README.md: add badge to pkg.go.dev ... A badge linking to https://pkg.go.dev/golang.org/x/crypto is added. Change-Id: Ifa07c0c04e3dd30503f196179f6883cc569e7908 Reviewed-on: https://go-review.googlesource.com/c/crypto/+/275873 Trust: Julie Qiu <julie@golang.org> Run-TryBot: Julie Qiu <julie@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org>	2020-12-08 17:14:46 +00:00
Kevin Burke	4d70248d17	README: add improvements ... Move the README to README.md so Gerrit can render it; currently Gerrit only renders files named exactly "README.md" (for example at https://go.googlesource.com/go). Add more links to the README explaining how to file issues, how to submit code changes, where to download the code to and how to get it. Hopefully this should help people who go to https://go.googlesource.com/crypto or https://github.com/golang/crypto figure out how to get started with development. Change-Id: I5406d0e6a562ef4a4146b66edc53a6fba7a9c3ee Reviewed-on: https://go-review.googlesource.com/49811 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>	2017-07-19 14:12:01 +00:00