Lines Matching full:developers
13 for kernel developers are left to Documentation/process/handling-regressions.rst.
51 it happens by accident, developers that caused it are expected to quickly fix
63 Note the "practical use case" in the first sentence of this section: developers
144 Developers of the affected code area should try to locate the culprit on their
150 run additional tests afterwards to pinpoint the exact root cause. Developers
180 something might break. This is in the interest of the kernel developers to make
186 Additionally, the kernel developers want to make it simple and appealing for
198 Exceptions to this rule are extremely rare; in the past developers almost always
220 Developers should fix any reported regression as quickly as possible, to provide
222 running into the issue; nevertheless developers need to take enough time and
256 Luckily this middling almost always can be avoided, as key developers for the
268 developers of the affected code area should look into the issue to find a fix
297 It does, but only for practical usage: the Linux developers want to be free to
318 The staging developers nevertheless often adhere to the "no regressions" rule,
326 Because the Linux kernel developers sometimes integrate changes known to cause
432 Regzbot supports a few other commands primarily used by developers or people
444 please use "The Linux kernel developers" for author attribution and link