Lines Matching full:patches
31 contributing one-off patches can do so in an informal way by sending them to the
40 always welcome `one-off patches`_ from people who do not routinely contribute to
72 .. _one-off patches:
85 #. Similarly, patches should be submitted soon after they are generated. Old
86 patches may not apply correctly if the underlying code changes between the
89 #. Patches should be made with ``svn diff``, or similar. If you use a
148 the right thing most of the time, and only commit patches without pre-commit
151 The trick to this is that the project has to guarantee that all patches that are
164 patches that are committed are actually reviewed.
254 quality patches. If you would like commit access, please send an email to
285 #. You are allowed to commit patches without approval which you think are
288 obviously broken patches, documentation/comment changes, any other minor
291 #. You are allowed to commit patches without approval to those portions of LLVM
302 encouraged to review other peoples' patches as well, but you aren't required
338 patches. We have a strong dislike for huge changes or long-term development
