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
64 from happening.  When you get review comments on a patch, take the time to
93 raised issues and how you dealt with them; the patch changelog is a good
114 If a patch is considered to be a good thing to add to the kernel, and once
128 patch.  Now other developers working with that tree will get the patch by
134 What may also happen at this point, depending on the nature of your patch,
136 case, heavy patch conflicts can result in some work being put on the back
145 Some day, if all goes well, you'll log on and see that your patch has been
151 To begin with, the visibility of your patch has increased yet again.  There
153 the patch before.  It may be tempting to ignore them, since there is no
164 The worst sort of bug reports are regressions.  If your patch causes a
167 unable to fix the regression (and nobody else does it for you), your patch
169 negating all of the work you have done to get your patch into the mainline,
170 having a patch pulled as the result of a failure to fix a regression could
183 up a version of the kernel containing your patch, etc.  Continuing to
187 after it's merged.  The next time you post a patch, they will be evaluating
196 a patch to your code.  That is one of the advantages of having your code
197 out there in the open, after all.  If you agree with the patch, you can
203 If you disagree with the patch, send a polite response explaining why.  If
204 possible, tell the author what changes need to be made to make the patch
215 somebody else's patch displaces yours and gets into the mainline, there is
219 long after they have forgotten whose patch actually got merged.