Lines Matching full:patch

13 It is a rare patch which is so good at its first posting that there is no
25 A patch of any significance will result in a number of comments from other
31  - If you have explained your patch well, reviewers will understand its
57 from happening.  When you get review comments on a patch, take the time to
86 raised issues and how you dealt with them; the patch changelog is a good
107 If a patch is considered to be a good thing to add to the kernel, and once
121 patch.  Now other developers working with that tree will get the patch by
127 What may also happen at this point, depending on the nature of your patch,
129 case, heavy patch conflicts can result in some work being put on the back
138 Some day, if all goes well, you'll log on and see that your patch has been
144 To begin with, the visibility of your patch has increased yet again.  There
146 the patch before.  It may be tempting to ignore them, since there is no
157 The worst sort of bug reports are regressions.  If your patch causes a
160 unable to fix the regression (and nobody else does it for you), your patch
162 negating all of the work you have done to get your patch into the mainline,
163 having a patch pulled as the result of a failure to fix a regression could
176 up a version of the kernel containing your patch, etc.  Continuing to
180 after it's merged.  The next time you post a patch, they will be evaluating
189 a patch to your code.  That is one of the advantages of having your code
190 out there in the open, after all.  If you agree with the patch, you can
196 If you disagree with the patch, send a polite response explaining why.  If
197 possible, tell the author what changes need to be made to make the patch
208 somebody else's patch displaces yours and gets into the mainline, there is
212 long after they have forgotten whose patch actually got merged.