Lines Matching full:who

30 patches which are known to be half-baked, but those who do will come in
110    users who are engaging in the noble work of tracking down problems.
144    enough for a reader who sees it with no other context to figure out the
165 These include subsystem maintainers and reviewers who need to decide
169 chasing, users who want to know how the kernel has changed, and more.  A
183 general, the more you can put yourself into the shoes of everybody who will
225 Another kind of tag is used to document who was involved in the development of
256  - Reported-by: names a user who reported a problem which is fixed by this
258    people who test our code and let us know when things do not work
304 When mailing patches, it is important to send copies to anybody who might
313  - Other developers who have been working in the same area - especially
314    those who might be working there now.  Using git to see who else has
329 When selecting recipients for a patch, it is good to have an idea of who
333 subsystem maintainers who watch over specific parts of the kernel.  Usually