doc: -u no longer needed in go get

I gather from golang #33102 that this no longer matters as much
as it once did, but that it is still considered best practice
not to use -u with go get after converting to go.mod.
I had the impression that there were more occurrences of -u in
our docs, but this is the only one I found.

Some folks like "go get", some prefer "gohack get", but at the
moment I like "git clone" and "go install".

Fixes #626.

Change-Id: I6a5be95417ee87c9bb0f487e8c7583b6396abe58
Reviewed-on: https://upspin-review.googlesource.com/c/upspin/+/19420
Reviewed-by: Andrew Gerrand <adg@golang.org>
1 file changed
tree: 17d5dd24ac81d7c44bde9cdf7978961aa224cba7
  1. .travis.yml
  2. AUTHORS
  3. CONDUCT.md
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. PATENTS
  8. README.binary
  9. README.md
  10. access/
  11. bind/
  12. cache/
  13. client/
  14. cloud/
  15. cmd/
  16. config/
  17. dir/
  18. doc/
  19. errors/
  20. factotum/
  21. flags/
  22. go.mod
  23. go.sum
  24. key/
  25. log/
  26. metric/
  27. pack/
  28. path/
  29. rpc/
  30. serverutil/
  31. shutdown/
  32. store/
  33. subcmd/
  34. test/
  35. transports/
  36. upbox/
  37. upspin/
  38. user/
  39. valid/
  40. version/
README.md

Upspin

Augie

Documentation: upspin.io

About the project

Upspin is an experimental project to build a framework for naming and sharing files and other data securely, uniformly, and globally: a global name system of sorts.

It is not a file system, but a set of protocols and reference implementations that can be used to join things like file systems and other storage services to the name space.

Performance is not a primary goal. Uniformity and security are.

Upspin is not an official Google product.

Status

Upspin has rough edges, and is not yet suitable for non-technical users.

Build Status

Contributing

The code repository lives at upspin.googlesource.com and is mirrored to GitHub.

Note that the Upspin project does not use GitHub pull requests, and that we use the issue tracker for bug reports and proposals only.

See the Contribution Guidelines for more information on contributing to the project.

Reporting issues

Please report issues through our issue tracker.

Community

All Upspin users should subscribe to the Upspin Announcements mailing list to receive critical information about the project.

Use the Upspin mailing list for discussion about Upspin use and development.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

The Upspin mascot is Copyright 2017 Renee French. All Rights Reserved.