Lines Matching full:they

26 developers as they review the code.  Working with reviewers can be, for
42    they see the same mistakes being made over and over again.  If you get a
49    be working on the kernel years from now, but they understand that their
50    employer could change.  They truly are, almost without exception,
51    working toward the creation of the best kernel they can; they are not
62 you need to pay attention to the technical observations that they are
85 One fatal mistake is to ignore review comments in the hope that they will
86 go away.  They will not go away.  If you repost code without having
96 time; if you help them get a running start, they will be in a better mood
97 when they revisit your code.
143 Now they can be resolved at leisure, before the merge window opens.
187 after it's merged.  The next time you post a patch, they will be evaluating
219 long after they have forgotten whose patch actually got merged.