Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(327)

Issue 170770043: code review 170770043: cmd/go: fix minor typo

Can't Edit
Can't Publish+Mail
Start Review
Created:
10 years, 11 months ago by natefinch
Modified:
10 years, 10 months ago
Reviewers:
shurcooL, bradfitz
CC:
golang-codereviews, bradfitz
Visibility:
Public.

Description

cmd/go: fix minor typo

Patch Set 1 #

Patch Set 2 : diff -r 0a4d2a8b7e6787d8643c19cb2278d93babdb9bea https://code.google.com/p/go #

Patch Set 3 : diff -r 0a4d2a8b7e6787d8643c19cb2278d93babdb9bea https://code.google.com/p/go #

Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -1 line) Patch
M src/cmd/go/doc.go View 1 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 7
natefinch
Hello golang-codereviews@googlegroups.com, I'd like you to review this change to https://code.google.com/p/go
10 years, 11 months ago (2014-10-30 14:28:43 UTC) #1
bradfitz
LGTM On Thu, Oct 30, 2014 at 11:28 AM, <nate.finch@gmail.com> wrote: > Reviewers: golang-codereviews, > ...
10 years, 11 months ago (2014-10-30 14:48:08 UTC) #2
bradfitz
You don't appear to have submitted a CLA. On Thu, Oct 30, 2014 at 11:28 ...
10 years, 11 months ago (2014-10-30 14:49:41 UTC) #3
natefinch
Oops, huh, I thought I'd done that a long time ago. Done now, anyway. On ...
10 years, 11 months ago (2014-10-30 17:41:49 UTC) #4
bradfitz
*** Submitted as https://code.google.com/p/go/source/detail?r=bb82d18ac07a *** cmd/go: fix minor typo LGTM=bradfitz R=golang-codereviews, bradfitz CC=golang-codereviews https://codereview.appspot.com/170770043 Committer: ...
10 years, 11 months ago (2014-10-30 20:20:46 UTC) #5
shurcooL
Hehe, this is a good example of how comments like // DO NOT EDIT THIS ...
10 years, 10 months ago (2014-12-02 19:57:49 UTC) #6
natefinch
10 years, 10 months ago (2014-12-03 21:26:25 UTC) #7
On 2014/12/02 19:57:49, shurcooL wrote: > Hehe, this is a good example of how comments like > > // DO NOT EDIT THIS FILE. GENERATED BY mkdoc.sh. > > are not the best way to communicate which files are generated (I don't know of a > better way yet, but I'll be thinking about it). ummm... oops :) Seems like there should be a tool to check for this on submission (i.e., rerun the mkdoc.sh and ensure the output is the same as what is getting checked in).
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b