Comment 2:

I don't really want the subrepos to be very special.
We should play by the same rules everyone else does.

Comment 3:

That's fair, but I want them to be special to us in our day-to-day hacking so we know
ahead of time when we're about to break code that we as a group maintain.
I could do the previously-discussed shell script too I guess.

Comment 4:

I don't.  I don't want to think about them in my day-to-day
hacking - part of the point was to speed the builds -  and I am
happy to fix them after the fact.  Remember that we're not breaking
them for Go 1 users: we're breaking them for people living
at Go tip, who should expect breakages anyway.
We have a TODO to gather a collection of external code that
will form a Go 1 compatibility suite.  Maybe the right thing is
to make those the initial members of that suite.  If you had a
file listing go command package patterns, say external.txt
    code.google.com/p/go.crypto/...
    code.google.com/p/go.net/...
    &c
then external.bash can be just
    go get $(cat external.txt)
    go test $(cat external.txt)
(I plan to make patterns work in go get.)
Russ

Comment 5:

Status changed to WorkingAsIntended.