Michael Bacarella has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/30054
Change subject: Documentation/lessons/lesson2.md: fix the git push command ......................................................................
Documentation/lessons/lesson2.md: fix the git push command
The current git push will fail because it tries to push to master directly. Also provide a blurb explaining how to make better use of Gerrit.
Signed-off-by: Michael Bacarella michael.bacarella@gmail.com Change-Id: I5a7e58600bb1527c3e407921f7984bf94bff8d58 --- M Documentation/lessons/lesson2.md 1 file changed, 10 insertions(+), 5 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/54/30054/1
diff --git a/Documentation/lessons/lesson2.md b/Documentation/lessons/lesson2.md index a95dd80..052599d 100644 --- a/Documentation/lessons/lesson2.md +++ b/Documentation/lessons/lesson2.md @@ -143,11 +143,16 @@ 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. +When you are done with your commit, run 'git push HEAD:refs/for/master' 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. + +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 +documentation, especially if you plan to work on multiple changes at the same +time. See +https://gerrit-review.googlesource.com/Documentation/intro-user.html#code-re...
## Part 4b: Using git cola to stage and submit a commit