Lines Matching refs:patches

10 If anything in this document becomes out of date, please send in patches
99     patches if these rules are followed, and many people will only
109     Following these rules will not guarantee success (as all patches are
113     Other excellent descriptions of how to create patches properly are:
152   Documentation/applying-patches.txt
223   - 4.x -git kernel patches
224   - subsystem specific kernel trees and patches
234     Linus, usually the patches that have already been included in the
237     can be found at http://git-scm.com/) but plain patches are also just
240     only patches that do not include new features that could affect the
245     is being added.  git can be used to send patches to Linus after -rc1
246     is released, but the patches need to also be sent to a public
288 4.x -git patches
291 git repository (hence the name.) These patches are usually released
296 Subsystem Specific kernel trees and patches
316 revisions to it, and maintainers can mark patches as under review,
407 If you add patches to your mail, make sure they are plain readable text
409 want to deal with attachments or compressed patches; they may want
433 to be able to take criticism and comments about your patches, evaluate
434 them at a technical level and either rework your patches or provide
470     - "Here is a series of small patches that..."
519 1) Small patches increase the likelihood that your patches will be
526    Small patches also make it very easy to debug when something goes
527    wrong.  It's much easier to back out patches one by one than it is
531 2) It's important not only to send small patches, but also to rewrite
532    and simplify (or simply re-order) patches before submitting them.
554 Also realize that it is not acceptable to send patches for inclusion
561 Along with breaking up your patches, it is very important for you to let
569 When sending in your patches, pay special attention to what you say in