Lines Matching refs:commit

317    $ git commit -am "[Diagnostic] Clarify -Winfinite-recursion message"
320 There is a unwritten convention of using tag for your commit. Tags
322 the tags for your modules, you can look at the commit history :
333 Changes can be reviewed by anyone in the LLVM community who has commit
360 This creates a review for your change, comparing your current commit
361 with the previous commit. You will be prompted to fill in the review
362 details. Your commit message is already there, so just add cfe-commits
415 As this is your first change, you won't have access to commit it
419    Thanks @somellvmdev. I don't have commit access, can you land this
420    patch for me? Please use "My Name my@email" to commit the change.
455 about getting commit access yourself. It's probably a good idea if:
464 Getting commit access
469 document <https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access>`__.
486 commit. Things to do first:
489    single commit. LLVM prefers commits to match the code that was
490    reviewed. (If you created one commit and then used "arc diff", you're
508 At this point git show should show a single commit on top of
511 Now you can push your commit with
522 Post-commit errors
547 | If post-commit error logs confuse you, do not worry too much -