Lines Matching full:commit
22 <li><a href="#commitaccess">Obtaining Commit Access</a></li>
159 commit.</li>
181 combination of code review plus post-commit review for trusted maintainers.
183 most people do the right thing most of the time, and only commit patches
184 without pre-commit review when they are confident they are right.</p>
190 The sole responsibility of a code owner is to ensure that a commit to their
319 making progress. The developer is welcome to re-commit the change after the
324 <h3><a name="commitaccess">Obtaining Commit Access</a></h3>
327 <p>We grant commit access to contributors with a track record of submitting high
328 quality patches. If you would like commit access, please send an email to
333 <li>The user name you want to commit with, e.g. "hacker".</li>
345 <p>Once you've been granted commit access, you should be able to check out an
347 normal anonymous URL of "http://llvm.org/...". The first time you commit
349 SVN about an untrusted key, you can ignore this. To verify that your commit
350 access works, please do a test commit (e.g. change a comment or add a blank
351 line). Your first commit to a repository may require the autogenerated email
355 <p>If you have recently been granted commit access, these policies apply:</p>
358 <li>You are granted <i>commit-after-approval</i> to all parts of LLVM. To get
361 When approved you may commit it yourself.</li>
363 <li>You are allowed to commit patches without approval which you think are
369 <li>You are allowed to commit patches without approval to those portions of
376 cause commit access to be revoked.</li>
483 contributions. If you commit a patch for someone else, please say "patch
484 contributed by J. Random Hacker!" in the commit message.</p>
