summaryrefslogtreecommitdiffstats
path: root/Documentation/intro-quick.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/intro-quick.txt')
-rw-r--r--Documentation/intro-quick.txt16
1 files changed, 9 insertions, 7 deletions
diff --git a/Documentation/intro-quick.txt b/Documentation/intro-quick.txt
index 25f5d5e44a..ae2e7e7110 100644
--- a/Documentation/intro-quick.txt
+++ b/Documentation/intro-quick.txt
@@ -138,10 +138,10 @@ Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 542 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
-remote:
+remote:
remote: New Changes:
remote: http://gerrithost:8080/68
-remote:
+remote:
To ssh://gerrithost:29418/RecipeBook.git
* [new branch] HEAD -> refs/for/master
----
@@ -209,10 +209,12 @@ Since we are the code reviewer, we're going to review the code. To do
this we can view it within the Gerrit web interface as either a
unified or side-by-side diff by selecting the appropriate option. In
the example below we've selected the side-by-side view. In either of
-these views you can add comments by double clicking on the line (or
-single click the line number) that you want to comment on. Once
-published these comments are viewable to all, allowing discussion
-of the change to take place.
+these views you can add inline comments by double clicking on the line
+(or single click the line number) that you want to comment on. Also you
+can add file comment by double clicking anywhere (not just on the
+"Patch Set" words) in the table header or single clicking on the icon
+in the line-number column header. Once published these comments are
+viewable to all, allowing discussion of the change to take place.
.Side By Side Patch View
image::images/intro-quick-review-line-comment.jpg[Adding a Comment]
@@ -375,7 +377,7 @@ able to post review scores as well as submitting the change by clicking
a single button. If you choose just to publish comments at this point then
the score will be stored but the change won't yet be accepted into the code
base. In this case there will be a _Submit Patch Set X_ button on the
-main screen. Just as Code Review and Verify are different operations
+main screen. Just as Code-Review and Verify are different operations
that can be done by different users, Submission is a third operation
that can be limited down to another group of users.