mleku/go
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cmd/go: fix two typos in helpdoc.go

Browse Source 
Change-Id: Ib750438107db6c82020cfb4abbab52435012b7fc
GitHub-Last-Rev: 3fa9b8c7bc70965c1ec9082b00c9b5a7af9751ef
GitHub-Pull-Request: golang/go#71082
Reviewed-on: https://go-review.googlesource.com/c/go/+/639217
Auto-Submit: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Michael Matloob <matloob@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Sam Thanawalla <samthanawalla@google.com>
This commit is contained in:
linmaolin
2025-01-02 21:05:21 +00:00
committed by Gopher Robot
parent 0afd7e85e5
commit 4b652e9f5f
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/cmd/go/alldocs.go
View File

@@ -2181,7 +2181,7 @@
// fields of all events to reconstruct the text format output, as it would // fields of all events to reconstruct the text format output, as it would
// have appeared from go build without the -json flag. // have appeared from go build without the -json flag.
// //
// Note that there may also be non-JSON error text on stdnard error, even // Note that there may also be non-JSON error text on standard error, even
// with the -json flag. Typically, this indicates an early, serious error. // with the -json flag. Typically, this indicates an early, serious error.
// Consumers should be robust to this. // Consumers should be robust to this.
// //
@@ -2616,7 +2616,7 @@
// Example: Data // Example: Data
// //
// If the server responds with any 4xx code, the go command will write the // If the server responds with any 4xx code, the go command will write the
// following to the programs' stdin: // following to the program's stdin:
// Response = StatusLine { HeaderLine } BlankLine . // Response = StatusLine { HeaderLine } BlankLine .
// StatusLine = Protocol Space Status '\n' . // StatusLine = Protocol Space Status '\n' .
// Protocol = /* HTTP protocol */ . // Protocol = /* HTTP protocol */ .

4
src/cmd/go/internal/help/helpdoc.go
View File

@@ -1034,7 +1034,7 @@ command
Example: Data Example: Data
If the server responds with any 4xx code, the go command will write the If the server responds with any 4xx code, the go command will write the
following to the programs' stdin: following to the program's stdin:
Response = StatusLine { HeaderLine } BlankLine . Response = StatusLine { HeaderLine } BlankLine .
StatusLine = Protocol Space Status '\n' . StatusLine = Protocol Space Status '\n' .
Protocol = /* HTTP protocol */ . Protocol = /* HTTP protocol */ .
@@ -1102,7 +1102,7 @@ Furthermore, as with TestEvent, parsers can simply concatenate the Output
fields of all events to reconstruct the text format output, as it would fields of all events to reconstruct the text format output, as it would
have appeared from go build without the -json flag. have appeared from go build without the -json flag.
Note that there may also be non-JSON error text on stdnard error, even Note that there may also be non-JSON error text on standard error, even
with the -json flag. Typically, this indicates an early, serious error. with the -json flag. Typically, this indicates an early, serious error.
Consumers should be robust to this. Consumers should be robust to this.
`, `,