Git: Difference between revisions
PaulePanter (talk | contribs) m (fix typo s/increading/increasing/) |
No edit summary |
||
| Line 1: | Line 1: | ||
= | = Gerrit = | ||
As part of our move to gerrit, git was introduced as primary SCM. | |||
== Register with gerrit == | |||
For authenticated access (to submit patches) you'll need a gerrit account which you can register at http://review.coreboot.org/. | |||
You also need to add your ssh keys (which are used for authenticating your connections to the repo) and your email addresses (used to match up signed-off-by: statements) to your gerrit user data at http://review.coreboot.org/#settings | |||
= Anonymous read access = | |||
Read-only access is available anonymously: | |||
git clone http://review.coreboot.org/p/coreboot | |||
git clone | = Authenticated read/write access = | ||
git clone ssh://<username>@review.coreboot.org:29418/coreboot | |||
Inside the checkout you should install the commit-msg hook which prepares commit messages to fit the style required by gerrit. This needs to happen only once per clone and can be done with | |||
wget -O .git/hooks/commit-msg http://review.coreboot.org/tools/hooks/commit-msg | |||
== pushing changes == | |||
When you committed your changes locally, you can push them to the server using | |||
git push origin HEAD:refs/for/master | |||
This will create a review request per commit on gerrit. | |||
For automating some aspects of patch submission (ie. simplify the command line), see the last paragraph of http://review.coreboot.org/Documentation/user-upload.html#push_create | |||
= Browsing = | = Browsing = | ||
You can browse the coreboot git repository on [http://code.coreboot.org/p/coreboot-git/source/tree/master/ code.coreboot.org], our indefero system. | There is no code browser that's properly synced with our gerrit instance at this time. This is a work in progress. | ||
<!-- You can browse the coreboot git repository on [http://code.coreboot.org/p/coreboot-git/source/tree/master/ code.coreboot.org], our indefero system. --> | |||
Revision as of 21:03, 4 June 2011
Gerrit
As part of our move to gerrit, git was introduced as primary SCM.
Register with gerrit
For authenticated access (to submit patches) you'll need a gerrit account which you can register at http://review.coreboot.org/. You also need to add your ssh keys (which are used for authenticating your connections to the repo) and your email addresses (used to match up signed-off-by: statements) to your gerrit user data at http://review.coreboot.org/#settings
Anonymous read access
Read-only access is available anonymously:
git clone http://review.coreboot.org/p/coreboot
Authenticated read/write access
git clone ssh://<username>@review.coreboot.org:29418/coreboot
Inside the checkout you should install the commit-msg hook which prepares commit messages to fit the style required by gerrit. This needs to happen only once per clone and can be done with
wget -O .git/hooks/commit-msg http://review.coreboot.org/tools/hooks/commit-msg
pushing changes
When you committed your changes locally, you can push them to the server using
git push origin HEAD:refs/for/master
This will create a review request per commit on gerrit.
For automating some aspects of patch submission (ie. simplify the command line), see the last paragraph of http://review.coreboot.org/Documentation/user-upload.html#push_create
Browsing
There is no code browser that's properly synced with our gerrit instance at this time. This is a work in progress.