design/2981: clean up before sending to golang-dev
Change-Id: Ied7dff46a48a08e5c6281abca90432b05af7ec31
Reviewed-on: https://go-review.googlesource.com/16000
Reviewed-by: Minux Ma <minux@golang.org>
diff --git a/design/2981-go-test-json.md b/design/2981-go-test-json.md
index 1654aaf..3c3b4b5 100644
--- a/design/2981-go-test-json.md
+++ b/design/2981-go-test-json.md
@@ -4,7 +4,7 @@
_With initial input by Russ Cox, Caleb Spare, Andrew Gerrand and Minux Ma._
-Last updated: 2015-10-07
+Last updated: 2015-10-16
Discussion at https://golang.org/issue/2981.
@@ -278,8 +278,7 @@
to print to stdout, so we can avoid the problem for now.
If we add more output to `build.go` in future, we can add
- `BuildOutput string` field to `TestResult` in `cmd/go/test.go` for arbitrary
- `build.go` output.
+ `BuildOutput string` field to `TestResult` for arbitrary `build.go` output.
I propose not to add `BuildOutput` now because `-n` affects `go test` too.
For example, `go test -n` prints a command to run the test binary, which
