summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--Documentation/tutorial/part2.md11
1 files changed, 4 insertions, 7 deletions
diff --git a/Documentation/tutorial/part2.md b/Documentation/tutorial/part2.md
index e5322186f9..3009e28167 100644
--- a/Documentation/tutorial/part2.md
+++ b/Documentation/tutorial/part2.md
@@ -157,10 +157,10 @@ commit, you wish to make changes to it, running `git commit --amend` allows
you to take back your commit and amend it.
When you are done with your commit, run `git push` to push your commit to
-coreboot.org. **Note:** To submit as a draft, use
-`git push origin HEAD:refs/drafts/master`. Submitting as a draft means that
-your commit will be on coreboot.org, but is only visible to those you add
-as reviewers.
+coreboot.org. **Note:** To submit as a private patch, use
+`git push origin HEAD:refs/for/master%private`. Submitting as a private patch
+means that your commit will be on review.coreboot.org, but is only visible to
+yourself and those you add as reviewers.
This has been a quick primer on how to submit a change to Gerrit for review
using git. You may wish to review the [Gerrit code review workflow
@@ -227,9 +227,6 @@ explained in the extended description.
When ready, select 'Commit' again. Once all errors have been satisfied
and the commit succeeds, move to the command line and run `git push`.
-**Note:** To submit as a draft, use `git push origin HEAD:refs/drafts/master`.
-Submitting as a draft means that your commit will be on coreboot.org, but is
-only visible to those you add as reviewers.
## Part 5: Getting your commit reviewed