Page History
...
To upload changes to Gerrit, you must first register and add an ssh key to your account. For For details on setting up your Gerrit account and sending patches, please see the Gerrit Gerrit documentation.
Gerrit can host many git repositories, and of course each of those repositories can contain many branches. For instance, these are some of the repositories on Gerrit today:
repo | description | status |
|---|---|---|
lustre | Mirror of Oracle's Lustre tree | No landings |
fs/lustre-release | Whamcloud's Lustre for new releases | Gatekeeping in effect |
| branch: b1_8 | for 1.8.6+ releases |
| branch: master | for 2.1.0+ releases |
fs/lustre-dev | A collection of development branches for Whamcloud developers | no gatekeeping |
tools/e2fsprogs | Mirror of kernel.org e2fsprogs, contains lustre branches | limited checkins |
| branch: master-lustre | for 1.41.90+ releases |
Managing Changes in Git
Whole books could be written about this topic, and there plenty of online tutorials on the web that explain this in more detail and suggest other methods of managing changes. However, this distilled version is (hopefully) enough to get started.
...
Now all git commits will use this name/email regardless of which repository the changes are being made in. If you want to specify a different name or email for a specific repository, it is possible to add the same information to the .git/config file in that specific repository.
...
An inspection request is created by pushing a change to a special branch on the gerrit Gerrit repository. For example, to create a request for a change against master on the main lustre repository, you do this your current working branch on your local branch for inspection:
...
Creating an inspection request for a change against master (assuming the remote alias has been added to ssh config):
| No Format |
|---|
git push ssh://review/fs/lustre-release HEAD:refs/for/master |
...
Overview
Content Tools