Lines Matching refs:with

3 At this point, you have followed the guidelines given so far and, with the
8 with, possibly, quite a bit of work yet to be done.
13 code.  You, as the author of that code, will be expected to work with the
22 developers as they review the code.  Working with reviewers can be, for
30    like to maintain a kernel with this code in it five or ten years later?
58 Note that you do not have to agree with every change suggested by
64 agree with the reviewer, take some time to think things over again.  It can
82 raised issues and how you dealt with them; the patch changelog is a good
84 through list archives to familiarize themselves with what was said last
97 in mind, of course, that he may not agree with you either.
116 patch.  Now other developers working with that tree will get the patch by
123 is that conflicts with work being done by others turn up.  In the worst
126 Other times, conflict resolution will involve working with the other
139 To begin with, the visibility of your patch has increased yet again.  There
161 After any regressions have been dealt with, there may be other, ordinary
162 bugs to deal with.  The stabilization period is your best opportunity to
166 for; you can start creating cool new patches once any problems with the old
176 it with the assumption that you will not be around to maintain it
184 out there in the open, after all.  If you agree with the patch, you can
190 If you disagree with the patch, send a polite response explaining why.  If
204 get on with your work.  Having one's work shoved aside in this manner can