Lines Matching +full:work +full:- +full:around

9 developers can make is to conclude that their work is now done.  In truth,
11 with, possibly, quite a bit of work yet to be done.
16 code.  You, as the author of that code, will be expected to work with the
23 ----------------------
31  - If you have explained your patch well, reviewers will understand its
35    Many of the changes you may be asked to make - from coding style tweaks
36    to substantial rewrites - come from the understanding that Linux will
37    still be around and under development a decade from now.
39  - Code review is hard work, and it is a relatively thankless occupation;
47  - Similarly, code reviewers are not trying to promote their employers'
54  - Be prepared for seemingly silly requests for coding style changes
58    to get around a problem actually needs to become a generalized
83 around.
92 around.  So it is always a good idea to remind reviewers of previously
112 -----------------
118 things.  In particular, there may be more than one tree - one, perhaps,
120 longer-term work.
124 being -mm.  Patches which affect multiple subsystems can also end up going
125 through the -mm tree.
129 default.  Subsystem trees typically feed linux-next as well, making their
135 is that conflicts with work being done by others turn up.  In the worst
136 case, heavy patch conflicts can result in some work being put on the back
140 everything applies cleanly.  This work can be a pain, but count your
141 blessings: before the advent of the linux-next tree, these conflicts often
169 negating all of the work you have done to get your patch into the mainline,
171 well make it harder for you to get work merged in the future.
184 respond to these reports is a matter of basic pride in your work.  If that
188 it with the assumption that you will not be around to maintain it
193 -----------------------------
200 your own), or send an Acked-by: response back and let the original poster
207 far.  If you are seen as needlessly blocking good work, those patches will
208 eventually flow around you and get into the mainline anyway.  In the Linux
217 get on with your work.  Having one's work shoved aside in this manner can