Lines Matching full:your
33 initialize your build environment</a>, <a
67 repository. The branch NAME is local to your workspace and will not be included
69 <h2 id="make-your-change">Make your change</h2>
71 the changes to your local repository:</p>
75 <p>Provide a detailed description of the change in your commit message. This
84 more detailed description of your patch,
95 <p>A unique change ID and your name and email as provided during <code>repo init</code> will be automatically added to your commit message. </p>
97 <p>Once you have committed your change to your personal history, upload it to gerrit with</p>
103 your patch on the review server, add comments, or request specific reviewers
104 for your patch.</p>
106 <p>Suppose a reviewer has looked at your patch and requested a small modification. You can amend your commit within git, which will result in a new patch on gerrit with the same change ID as the original.</p>
107 <p><em>Note that if you have made other commits since uploading this patch, you will need to manually move your git HEAD.</em></p>
111 <p>When you upload the amended patch, it will replace the original on gerrit and in your local git history.</p>
113 <p>If other patches are submitted to the source tree that conflict with yours, you will need to rebase your patch on top of the new HEAD of the source repository. The easy way to do this is to run</p>
116 <p>This command first fetches the updates from the source server, then attempts to automatically rebase your HEAD onto the new remote HEAD.</p>
123 <p>After either automatic or manual rebase is complete, run <code>repo upload</code> to submit your rebased patch.</p>
154 <p>Patch the change into your local client using one of the Download commands.</p>
178 <p>To add an inline comment, double-click the relevant line of the code and write your comment in the text box that opens. When you click Save, only you can see your comment.</p>
179 <p>To publish your comments so that others using Gerrit will be able to see them, click the Publish Comments button. Your comments will be emailed to all relevant parties for this change, including the change owner, the patch set uploader (if different from the owner), and all current reviewers.</p>
