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

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

Plus automatic package<->project association script.
(This is just a helper script for now. I intend to fully automate
the associations further down the track.)

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

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

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

Fixes #961.
Fixes #962.

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

Fixes #963.
Fixes #964.

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

Fixes #959.

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

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

Fixes #954.

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

Release 2010-04-27. runtime: rename cgo2c, *.cgo to goc2c, *.goc
to avoid confusion with real cgo.

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

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

Fixes #953.

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

Fixes #812.

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

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

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

Fixes #948.

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

R=golang-dev, brainman
CC=golang-dev
https://golang.org/cl/1899041

Fixes #921.

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

R=rsc, Joe Poirier, PeterGo
CC=golang-dev
https://golang.org/cl/1872045

- TARG had extra space at the end;
- it should be set before "all" target.

R=rsc, Joe Poirier
CC=golang-dev
https://golang.org/cl/1846042

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

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

This CL basically applies the same changes as

	http://code.google.com/p/go/source/detail?r=5e0a29014e8e

but for bytes package.

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

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

undo workaround in gc

Fixes #943.

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

bug introduced in https://golang.org/cl/1886043

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

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

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

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

Fixes #937.
Fixes #938.
Fixes #939.
Fixes #940.

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

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

Goroutine 1:
  Call Read on read half of pipe, entering pipeHalf.rw.
  Check ioclosed field, which is false.
  Send data to p.c1
  Wait for response on p.c2.

Goroutine 2:
  Call Close on read half of pipe, entering pipeHalf.close.
  Set closed field.
  Send error to p.cclose.
  Set ioclosed field.
  Send 1 to p.done.
  Return and exit goroutine.

Goroutine 3:
  This is the goroutine running pipe.run, and for some reason
  it has started late.
  Read error from p.rclose; set rerr and continue.
  Read 1 from p.done; increment ndone and continue.
  Read data from r1 (sent by goroutine 1); set r1 = nil and continue

Now goroutine 1 is waiting for a response, and goroutine 3 is
waiting for something else to happen.

This patch fixes the race by having the runner check whether
the read half is closed when it is asked for read data, and
similarly for the corresponding race on the write half.

This patch also fixes the similar race in which ndone gets
bumped up to 2 while there is a reader or writer waiting.

There is still another race to fix.  It is possible for the
read half and the write half to both be closed, and for the
runner goroutine to exit, all before the runner goroutine sees
the request from a reader.  E.g., in the above, have goroutine
2 also close the write half, and have goroutine 3 see both
done messages before it sees the request from goroutine 1.

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

For the Windows version of syscall Errstr, set the
FORMAT_MESSAGE_IGNORE_INSERTS value of the FormatMessage
Flags argument when there are no values to insert.

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

SNI (Server Name Indication) is a way for a TLS client to
indicate to the server which name it knows the server by. This
allows the server to have several names and return the correct
certificate for each (virtual hosting).

PeerCertificates returns the list of certificates presented by
server.

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

        OCSP is the preferred X.509 revocation mechanism. X.509 certificates
        can contain a URL from which can be fetched a signed response saying
        "this certificate is valid until $x" (where $x is usually 7 days in the
        future). These are called OCSP responses and they can also be included
        in the TLS handshake itself ("OCSP stapling")

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

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

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

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

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