Lines Matching full:your
14 to merge your work into the main branch. If you are looking for ideas,
15 please let us know about your interest and skills and we will be happy
26 We now describe how to set up your development environment and submit
29 Setting up your Environment
43 which gives Google a royalty-free unlimited license to use your
58 creates `Change-Id: ...` lines in your commits.
68 5. Configure your Gerrit password with a ``.netrc`` (Mac and Linux)
78 same as your Gerrit login.
80 * Click ``Allow access`` when the page requests access to your
96 e.g. ``C:\Users\username`` where ``username`` is your user
103 1. Make your changes against master or whatever branch you
104 like. Commit your changes as one patch. When you commit, the Gerrit
107 Make sure that your commit message is formatted in the `50/72 style
110 2. Push your changes to the Ceres Gerrit instance:
124 modifying the code in your ``git`` instance, *don't make a new
133 patch and your updates as a single commit. You will have a chance
138 with the new one. The review interface retains your original patch,
141 Publish your responses to the comments, and wait for a new round
