Fixes #3420.
        Part of issue 3424.

R=golang-dev, cldorian, adg, r
CC=golang-dev
https://golang.org/cl/5958046

        Fixes #3427.
        Part of issue 3424.

R=golang-dev, bradfitz, r
CC=golang-dev
https://golang.org/cl/5959045

        Part of issue 3424

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5955049

This is now known as code.google.com/p/go.crypto/ssh/terminal.

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5970044

"go1" dominates. Delete the text about weekly and release.
We can revisit this once the situation changes.

R=golang-dev, rsc
CC=golang-dev
https://golang.org/cl/5969043

Orignally published on The Go Programming Language, September 21, 2011.

http://blog.golang.org/2011/09/go-image-package.html

Update #2547

R=adg, nigeltao
CC=golang-dev
https://golang.org/cl/5933049

R=golang-dev
CC=golang-dev
https://golang.org/cl/5937049

R=golang-dev, r
CC=golang-dev, hcwfrichter
https://golang.org/cl/5934046

R=golang-dev, dsymonds
CC=golang-dev
https://golang.org/cl/5940050

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5937048

R=golang-dev, gri, rsc
CC=golang-dev
https://golang.org/cl/5921045

Not a complete fix for issue 3342, but fixes the trivial case.
There may still be a race in the instants before and after
a scavenger-induced garbage collection.

Intended to be "obviously safe": a call to runtime·gosched
before main.main is no different than a call to runtime.Gosched
at the beginning of main.main, and it is (or had better be)
safe to call runtime.Gosched at any point during main.

Update #3342.

R=iant
CC=golang-dev
https://golang.org/cl/5919052

Another attempt at https://golang.org/cl/5754088.

Before, we only consulted $GOBIN for source code
found in $GOROOT, but that's confusing to explain
and less useful.  The new behavior lets users set
GOBIN=$HOME/bin and have all go-compiled binaries
installed there.

Tested a few cases in test.bash.

Ran all.bash with and without $GOBIN and it works.
Even so, I expect it to break the builders,
like it did last time, we can debug from there.

Fixes #3269 (again).
Fixes #3396.
Fixes #3397.

R=golang-dev, bradfitz
CC=golang-dev
https://golang.org/cl/5927051

When we find a package in DIR/src/foo, we only let it
be known as foo if there is no other foo in an earlier
GOPATH directory or the GOROOT directory.
The GOROOT check was looking in GOROOT/src/foo
instead of GOROOT/src/pkg/foo, which meant that
the import paths "lib9", "libbio", "libmach", and so
on were unavailable, and the import paths "math",
"errors", and so on were available.  Correct this.

Fixes #3390.

R=golang-dev, minux.ma
CC=golang-dev
https://golang.org/cl/5927050

Issue 3207 was caused by setting GOPATH=GOROOT.
This is a common mistake, so diagnose it at command start
and also correct the bug that it caused in get (downloading
to GOROOT/src/foo instead of GOROOT/src/pkg/foo).

Issue 3268 was caused by recognizing 'packages' that
had installed binaries but no source.  This behavior is not
documented and causes trouble, so remove it.  We can
revisit the concept of binary-only packages after Go 1.

Fixes #3207.
Fixes #3268.

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5930044

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5924050

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5924051

Fixes #3384.

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5915044

R=golang-dev, rsc
CC=golang-dev
https://golang.org/cl/5928043

R=golang-dev, r, r
CC=golang-dev
https://golang.org/cl/5919048

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5924044

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5916046

Fixes #3395.

R=rsc, dsymonds
CC=golang-dev
https://golang.org/cl/5905063

Breaks closure test when GOMAXPROCS=2 or more.

««« original CL description
runtime: restore deadlock detection in the simplest case.

Fixes #3342.

R=iant, r, dave, rsc
CC=golang-dev, remy
https://golang.org/cl/5844051

»»»

R=rsc
CC=golang-dev
https://golang.org/cl/5924045

hg cat -r 11846 src/cmd/goinstall/tag_test.go >tag_test.go
No changes.

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5919047

Fixes #3313

go-mode-backward-skip-comments is probably due for a more ambitious refactoring --- it repeats guard conditions after every nearly every movement of point.

R=sameer, r
CC=golang-dev
https://golang.org/cl/5844063

R=golang-dev, dsymonds
CC=ben.fried, golang-dev
https://golang.org/cl/5869043

Fixes #3342.

R=iant, r, dave, rsc
CC=golang-dev, remy
https://golang.org/cl/5844051

The Makefile target was broken due to the rename of the HTML file.

R=golang-dev
CC=golang-dev
https://golang.org/cl/5918045

Fixes #3400.

R=golang-dev, rsc
CC=golang-dev
https://golang.org/cl/5926043

Originally published on The Go Programming Language Blog, Abril 27, 2010.

http://blog.golang.org/2010/04/json-rpc-tale-of-interfaces.html

R=adg, r
CC=golang-dev
https://golang.org/cl/5920044

R=golang-dev, rsc
CC=golang-dev
https://golang.org/cl/5920043

Fixes #3347.

R=golang-dev, aram, r, rsc
CC=golang-dev
https://golang.org/cl/5918043

Update #3400

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5921044

For example, /ref and /doc/reference.html now both redirect to /ref/.

Fixes #3401.

R=golang-dev, rsc
CC=golang-dev
https://golang.org/cl/5916044

Fixes #3399.

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5919044

Fixes #3402.

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5923043

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/5921043