From: Han-Wen Nienhuys Date: Fri, 14 Jul 2017 21:38:49 +0000 (-0600) Subject: doc/contribute: avoid using the word "change list". X-Git-Tag: go1.9rc1~64 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=d5da104294cd449a6588dac26c52f221a60357ff;p=gostls13.git doc/contribute: avoid using the word "change list". Neither the Gerrit UI nor its docs use the term CL or changelist. Change-Id: Ic19fddc660ec4f008f10fd207e4ac6349431ff5d Reviewed-on: https://go-review.googlesource.com/48595 Reviewed-by: Brad Fitzpatrick --- diff --git a/doc/contribute.html b/doc/contribute.html index e3f69580dd..f204b06e65 100644 --- a/doc/contribute.html +++ b/doc/contribute.html @@ -496,7 +496,7 @@ Fixes #159

The commented section of the file lists all the modified files in your client. -It is best to keep unrelated changes in different change lists, +It is best to keep unrelated changes in different commits, so if you see a file listed that should not be included, abort the command and move that file to a different branch.

@@ -656,7 +656,7 @@ $ git mail

Unless explicitly told otherwise, such as in the discussion leading -up to sending in the change list, it's better not to specify a reviewer. +up to sending in the change, it's better not to specify a reviewer. All changes are automatically CC'ed to the golang-codereviews@googlegroups.com mailing list. If this is your first ever change, there may be a moderation @@ -704,7 +704,7 @@ You must respond to review comments through the web interface. When you have revised the code and are ready for another round of review, stage those changes and use git change to update the commit. -To send the update change list for another round of review, +To send the updated change for another round of review, run git mail again.