Lines Matching full:commit
101 commit mailing list (or commit it directly if applicable). Alternatively, some
103 tracker, but the commit list is the primary place for reviews and should
134 #. Code reviews are conducted by email on the relevant project's commit mailing
139 changes where the developer owns the component) can be reviewed after commit.
177 of code review plus post-commit review for trusted maintainers. Having both is
179 the right thing most of the time, and only commit patches without pre-commit
186 responsibility of a code owner is to ensure that a commit to their area of the
275 progress. The developer is welcome to re-commit the change after the problem has
280 Commit messages
283 Although we don't enforce the format of commit messages, we prefer that
297 * Separate the commit message into title, body and, if you're not the original
307 or "[OpenMP] ...". This helps email filters and searches for post-commit
327 * If the commit is a bug fix on top of another recently committed patch, or a
329 related commit. This could be as simple as "Revert rNNNN because it caused
336 Obtaining Commit Access
339 We grant commit access to contributors with a track record of submitting high
340 quality patches. If you would like commit access, please send an email to
343 #. The user name you want to commit with, e.g. "hacker".
356 Once you've been granted commit access, you should be able to check out an LLVM
358 anonymous URL of "http://llvm.org/...". The first time you commit you'll have
360 untrusted key; you can ignore this. To verify that your commit access works,
361 please do a test commit (e.g. change a comment or add a blank line). Your first
362 commit to a repository may require the autogenerated email to be approved by a
366 If you have recently been granted commit access, these policies apply:
368 #. You are granted *commit-after-approval* to all parts of LLVM. To get
371 you may commit it yourself.
373 #. You are allowed to commit patches without approval which you think are
379 #. You are allowed to commit patches without approval to those portions of LLVM
386 cause commit access to be revoked.
481 commit access may commit it for the author once appropriate (based on the
487 file describes higher-level contributions. If you commit a patch for someone
489 by the `commit messages`_ section. Overall, please do not add contributor names
492 Also, don't commit patches authored by others unless they have submitted the
495 etc.). The author should first submit them to the relevant project's commit
