Lines Matching defs:patch

89 When making a patch for review, the goal is to make it as easy for the reviewer
92 #. Make your patch against git main, not a branch, and not an old version
93    of LLVM.  This makes it easy to apply the patch.  For information on how to
98    time the patch was created and the time it is applied.
100 #. Once you have created your patch, create a
433 * If the commit is a bug fix on top of another recently committed patch, or a
434   revert or reapply of a patch, include the git commit hash of the prior
438 * If the patch has been reviewed, add a link to its review page, as shown
440   If the patch fixes a bug in GitHub Issues, we encourage adding a reference to
467 * Remember, it is normal and healthy to have patches reverted.  Having a patch
469 * We encourage explicitly thanking the person who reverted the patch for doing
472   original commit thread with the reverting patch author.
479   fixed patch - possibly after another round of review if warranted.
497   problematic patch will be reverted and we can return to it at our next
508   the proper patch or set of patches is being reverted.
509 * The commit message for the reverting commit should explain why patch
513   patch was reverted, and helps others following llvm-commits track context.
518   patch; documenting the reasons for others who might be following along
521   provide a means for the patch author to debug the root issue.  If a situation
523   requires hardware patch author doesn't have access to, sharp regression in
525   proactive about working with the patch author to debug and test candidate
534 * When re-applying a reverted patch, the commit message should be updated to
565    information on how to get approval for a patch, please see :doc:`CodeReview`.
680 When contributors submit a patch to an LLVM project, other developers with
687 file describes higher-level contributions. If you commit a patch for someone
693 patch to the project or you have been authorized to submit them on their behalf
697 a patch privately, encourage them to submit it to the appropriate list first.
770   other patch.
840 their patch with every possible configuration.
994 4. The initial patch should add documentation, maintainers, and triple support in
996    the target and lower instructions to assembly. The final patch must show that