diff options
| author | Andrew Gerrand <adg@golang.org> | 2013-11-01 11:33:51 +1100 |
|---|---|---|
| committer | Andrew Gerrand <adg@golang.org> | 2013-11-01 11:33:51 +1100 |
| commit | 1d78c868971effacde64e9c9a8d1ae1bea13be17 (patch) | |
| tree | b4850dde65de99115c71335086fc3954fc4ffc53 | |
| parent | 28c1081208f1afd9c2a699ab812a9b14b15ae558 (diff) | |
| download | go-1d78c868971effacde64e9c9a8d1ae1bea13be17.tar.gz go-1d78c868971effacde64e9c9a8d1ae1bea13be17.zip | |
[release-branch.go1.2] doc/go1.2.html: delete repeated word
««« CL 19840043 / 938b64b0f608
doc/go1.2.html: delete repeated word
TBR=rsc
R=golang-dev
CC=golang-dev
https://golang.org/cl/19840043
»»»
R=golang-dev
CC=golang-dev
https://golang.org/cl/20240044
| -rw-r--r-- | doc/go1.2.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/go1.2.html b/doc/go1.2.html index 67291e388a..7189045205 100644 --- a/doc/go1.2.html +++ b/doc/go1.2.html @@ -182,7 +182,7 @@ Before Go 1.2, it was too easy for a runaway recursion to consume all the memory <p> <em>Updating</em>: The increased minimum stack size may cause programs with many goroutines to use -more memory. There is no workaround, but future plans for future releases +more memory. There is no workaround, but plans for future releases include new stack management technology that should address the problem better. </p> |