misc/cgo/testso: use bash to run test.bash

R=golang-dev, minux.ma, capnm9
CC=golang-dev
https://codereview.appspot.com/9717043
log/syslog: fix deadlock in test
The problem was that server handlers block on done<-,
the goroutine that reads from done blocks on count<-,
and the main goroutine that is supposed to read from count
waits for server handlers to exit.
Fixes issue 5547.

R=golang-dev, dave, bradfitz
CC=golang-dev
https://codereview.appspot.com/9722043
A+C: Gerasimos Dimitriadis (individual CLA)

Generated by addca.

R=gobot
CC=golang-dev
https://codereview.appspot.com/9734043
asn1: Stricter checks for DER encoded booleans

According to X.690, only 0 and 255 are allowed as values
for encoded booleans. Also added some test for parsing
booleans

R=golang-dev, agl, r
CC=golang-dev
https://codereview.appspot.com/9692043

Committer: Adam Langley <agl@golang.org>
path/filepath: Skip TestEvalSymlinks. Plan 9 doesn't have symlinks.

R=golang-dev, r
CC=golang-dev
https://codereview.appspot.com/9713044

Committer: Rob Pike <r@golang.org>
cmd/cov: delete
It doesn't work, it's not portable, it's not part of the released
binaries, and a better tool is due.

Fixes issue 1319.
Fixes issue 4621.

R=golang-dev, bradfitz, dave, rsc
CC=golang-dev
https://codereview.appspot.com/9681044
crypto/x509: harmonise error prefixes.

crypto/x509 has ended up with a variety of error formats. This change makes them all start with "x509: ".

R=golang-dev, r
CC=golang-dev
https://codereview.appspot.com/9736043
doc: start go 1.2 notes

This is a file of hints, not a file of polished text.
Let's not try to do polished text until we start the
release process.

R=golang-dev, gri
CC=golang-dev
https://codereview.appspot.com/9750043
build: fix make.rc on Plan 9

Set $status as null to prevent rc from exiting
on the last --no-banner argument checking when
used with rc -e. It allows all.rc to not exit
before executing run.rc

R=golang-dev, lucio.dere, rsc
CC=golang-dev
https://codereview.appspot.com/9611045

Committer: Rob Pike <r@golang.org>
fmt.Printf: introduce notation for random access to arguments.
This text is added to doc.go:

        Explicit argument indexes:

        In Printf, Sprintf, and Fprintf, the default behavior is for each
        formatting verb to format successive arguments passed in the call.
        However, the notation [n] immediately before the verb indicates that the
        nth one-indexed argument is to be formatted instead. The same notation
        before a '*' for a width or precision selects the argument index holding
        the value. After processing a bracketed expression [n], arguments n+1,
        n+2, etc. will be processed unless otherwise directed.

        For example,
                fmt.Sprintf("%[2]d %[1]d\n", 11, 22)
        will yield "22, 11", while
                fmt.Sprintf("%[3]*[2].*[1]f", 12.0, 2, 6),
        equivalent to
                fmt.Sprintf("%6.2f", 12.0),
        will yield " 12.00". Because an explicit index affects subsequent verbs,
        this notation can be used to print the same values multiple times
        by resetting the index for the first argument to be repeated:
                fmt.Sprintf("%d %d %#[1]x %#x", 16, 17)
        will yield "16 17 0x10 0x11".

The notation chosen differs from that in C, but I believe it's easier to read
and to remember (we're indexing the arguments), and compatibility with
C's printf was never a strong goal anyway.

While we're here, change the word "field" to "arg" or "argument" in the
code; it was being misused and was confusing.

R=rsc, bradfitz, rogpeppe, minux.ma, peter.armitage
CC=golang-dev
https://codereview.appspot.com/9680043