Lines Matching full:patch
17 <li><a href="#patches">Making a Patch</a></li>
104 <h3><a name="patches">Making a Patch</a></h3>
107 <p>When making a patch for review, the goal is to make it as easy for the
111 <li>Make your patch against the Subversion trunk, not a branch, and not an old
112 version of LLVM. This makes it easy to apply the patch. For information
118 time the patch was created and the time it is applied.</li>
126 a separate patch from the rest of your changes.</li>
129 <p>When sending a patch to a mailing list, it is a good idea to send it as an
131 message. This ensures that your mailer will not mangle the patch when it
134 <p><em>For Thunderbird users:</em> Before submitting a patch, please open
164 <li>Code review can be an iterative process, which continues until the patch
171 feedback on a patch, but only people with Subversion write access can approve
188 assume someone else will review it, allowing the patch to go unreviewed. To
355 approval, submit a <a href="#patches">patch</a> to
479 contributions. If you commit a patch for someone else, please say "patch
