GNUBoot
/
coreboot-kgpe-d16
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation: Clarify workflow for cloning coreboot from Gerrit. 

Documentation that was there seems to reference and older version.

Signed-off-by: Michael Bacarella <michael.bacarella@gmail.com>
Change-Id: I3709613ae065153123d00801ea1b4ff86b100264
Reviewed-on: https://review.coreboot.org/c/30025
Reviewed-by: Angel Pons <th3fanbus@gmail.com>
Reviewed-by: Patrick Georgi <pgeorgi@google.com>
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
This commit is contained in:
Michael Bacarella 2018-12-03 11:36:06 -08:00 committed by Patrick Georgi
parent 24c0b6abd6
commit be1907a513
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
Documentation/lessons/lesson2.md
View File

@ -60,12 +60,13 @@ just generated.
## Part 3: Clone coreboot and configure it for submitting patches ## Part 3: Clone coreboot and configure it for submitting patches
Go to the **Projects** tab in the upper left corner and select **List**. On Gerrit, click on the **Browse** tab in the upper left corner and select
From the dropdown menu that appears, select "coreboot". **Repositories**. From the listing, select the "coreboot" repo. You may have
to click the next page arrow at the bottom a few times to find it.
If you are using SSH keys, select **ssh** from the tabs under "Project coreboot" If you are using SSH keys, select **ssh** from the tabs under "Project
and run the command that appears. This should prompt you for your id_rsa passphrase, coreboot" and run the clone with commit-msg hook command that's provided. This
if you previously set one. should prompt you for your id_rsa passphrase, if you previously set one.
If you are using HTTP, instead, select **http** from the tabs under "Project coreboot" If you are using HTTP, instead, select **http** from the tabs under "Project coreboot"
and run the command that appears and run the command that appears
@ -278,4 +279,4 @@ next to checkout by clicking **Copy to clipboard**. Then, run the copied
command in your coreboot repository. Now, the last commit should be the most command in your coreboot repository. Now, the last commit should be the most
recent commit to that patch; to update it, make your desired changes, stage recent commit to that patch; to update it, make your desired changes, stage
the files, then amend and push the commit using the instructions in the above the files, then amend and push the commit using the instructions in the above
paragraph. paragraph.