Lines Matching full:upload
53 <p>Before you can upload to Gerrit, you need to establish a password that
95 <h2 id="upload-to-gerrit">Upload to gerrit</h2>
96 <p>Once you have committed your change to your personal history, upload it to gerrit with</p>
97 <pre><code>$ repo upload
99 <p>If you have started multiple branches in the same repository, you will be prompted to select which one(s) to upload.</p>
100 <p>After a successful upload, repo will provide you the URL of a new page on
110 <p>When you upload the amended patch, it will replace the original on gerrit and in your local git history.</p>
122 <p>After either automatic or manual rebase is complete, run <code>repo upload</code> to submit your rebased patch.</p>
182 <a href="/source/code-lines.html">Codelines, Branches, and Releases</a>. For most projects under <code>external/</code>, changes should be made upstream and then the Android maintainers informed of the new upstream release containing these changes. It may also be useful to upload patches that move us to track a new upstream release, though these can be difficult changes to make if the project is widely used within Android like most of the larger ones mentioned below, where we tend to upgrade with every release.</p>
