aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2010-01-13 16:44:40 -0800
committerRuss Cox <rsc@golang.org>2010-01-13 16:44:40 -0800
commitc6336155f1718bd0485be8800d6cebedfe920073 (patch)
treed8067c93422ab295e85682faf06a2830b67b5417
parent6c2e0fe1f9e3bf0e164a23162bb5bdf2dd28600e (diff)
downloadgo-c6336155f1718bd0485be8800d6cebedfe920073.tar.gz
go-c6336155f1718bd0485be8800d6cebedfe920073.zip
contribute.html: suggest hg mail instead of hg upload
R=r CC=golang-dev https://golang.org/cl/186145
-rw-r--r--doc/contribute.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/contribute.html b/doc/contribute.html
index 3b0c12569a..044a880f6d 100644
--- a/doc/contribute.html
+++ b/doc/contribute.html
@@ -416,15 +416,15 @@ When you have revised the code and are ready for another round of review, run
</p>
<pre>
-$ hg upload 99999
+$ hg mail 99999
</pre>
-<p>to upload the latest copy.
+<p>again to upload the latest copy and send mail asking the reviewers to please take another look
+(<code>PTAL</code>).
You might also visit the code review web page and reply to the comments,
letting the reviewer know that you've addressed them or explain why you
haven't. When you're done replying, click &ldquo;Publish and Mail comments&rdquo;
to send the line-by-line replies and any other comments.
-A common acronym in such mails is <code>PTAL</code>: please take another look.
</p>
<p>
The reviewer can comment on the new copy, and the process repeats.