| Age | Commit message (Collapse) | Author |
|---|
|
Change-Id: Ieff4883f98129407be1b3faa2610253aef5c1f33
Reviewed-on: https://go-review.googlesource.com/c/proposal/+/494335
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Auto-Submit: Ian Lance Taylor <iant@golang.org>
|
|
Traditionally, Go design docs linked to the corresponding mailing list
thread for discussion. In the new world, discussion happens on the
GitHub issue. This is easier to get to because the name of the design
doc implies the GitHub issue, but this requires both knowledge of this
convention and additional effort on the reader's part.
Add a direct link to the discussion in the design doc template to make
it easy to find the discussion with no additional knowledge or effort.
Change-Id: Ie76dd85551bc33dff7d981fbd0a28e664947b005
Reviewed-on: https://go-review.googlesource.com/15290
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
|
|
Change-Id: I6fc2ebd570be36399e66869160f8bbbea364bcf0
Reviewed-on: https://go-review.googlesource.com/12887
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
|
|
Change-Id: Ib00364d8644bda892a142bd3ef439d3b6b68f205
Reviewed-on: https://go-review.googlesource.com/12885
Reviewed-by: Rob Pike <r@golang.org>
|
|
Change-Id: I8c303d27c096ee431eb72e5f04b58318b55cabce
Reviewed-on: https://go-review.googlesource.com/12882
Reviewed-by: Russ Cox <rsc@golang.org>
Reviewed-by: Rob Pike <r@golang.org>
|
