Lines Matching refs:patch
3773 the form of a "patch", i. e. a context diff against a certain (latest
3776 But before you submit such a patch, please verify that your modifi-
5130 Send patch file to the U-Boot email list;
5186 When you send a patch, please include the following information with
5189 * For bug fixes: a description of the bug and how your patch fixes
5191 patch actually fixes something.
5196 * A CHANGELOG entry as plaintext (separate from the patch)
5204 * If your patch adds new configuration options, don't forget to
5207 * The patch itself. If you are using git (which is *strongly*
5208 recommended) you can easily generate the patch using the
5209 "git format-patch". If you then use "git send-email" to send it to
5219 your patch includes sufficient directory information for the
5226 files, all these changes shall be submitted in a SINGLE patch file.
5229 submitted as SEPARATE patches, one patch per changeset.
5234 * Before sending the patch, run the buildman script on your patched
5238 * Keep your modifications to the necessary minimum: A patch