summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Zanin <bzanin+bitbucket@gmail.com>2018-02-23 03:48:05 +0000
committerOwen Jacobson <owen.jacobson@grimoire.ca>2018-02-23 03:48:05 +0000
commit19a5c224cf45e888772cb5c5e9d34019e35349c6 (patch)
treeb9b947375fc66deee40450d3e601f94969c9c14c
parent8abae6ead2ff1127c090963c07dcc2d8f3db41a9 (diff)
parent822d48a271b39f48fc0a70cffd2afbd0b236713a (diff)
Merged in gnomon-/grimoire.ca/typofix/dev-go (pull request #5)
Two trivial typos ("repsect", "disasterous")
-rw-r--r--wiki/dev/go.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/wiki/dev/go.md b/wiki/dev/go.md
index 05c2a96..33fce8b 100644
--- a/wiki/dev/go.md
+++ b/wiki/dev/go.md
@@ -40,7 +40,7 @@ I can't speak for Go's genesis within Google, but outside of Google, this undera
`go get` is a disappointing abdication of responsibility. Packaging boundaries are communications boundaries, and the Go team's response of "vendor everything" amounts to refusing to help developers communicate with one another about their code.
-I can repsect the position the Go team has taken, which is that it's not their problem, but that puts them at odds with every other major language. Considering the disasterous history of attempts at package management for C libraries and the existence of Autotools as an example of how this can go very wrong over a long-enough time scale, it's very surprising to see a language team in this century washing their hands of the situation.
+I can respect the position the Go team has taken, which is that it's not their problem, but that puts them at odds with every other major language. Considering the disastrous history of attempts at package management for C libraries and the existence of Autotools as an example of how this can go very wrong over a long-enough time scale, it's very surprising to see a language team in this century washing their hands of the situation.
## GOPATH