.. | .. |
---|
5 | 5 | |
---|
6 | 6 | This is a short document describing the preferred (or made up, depending |
---|
7 | 7 | on who you ask) management style for the linux kernel. It's meant to |
---|
8 | | -mirror the process/coding-style.rst document to some degree, and mainly written to |
---|
9 | | -avoid answering [#f1]_ the same (or similar) questions over and over again. |
---|
| 8 | +mirror the :ref:`process/coding-style.rst <codingstyle>` document to some |
---|
| 9 | +degree, and mainly written to avoid answering [#f1]_ the same (or similar) |
---|
| 10 | +questions over and over again. |
---|
10 | 11 | |
---|
11 | 12 | Management style is very personal and much harder to quantify than |
---|
12 | 13 | simple coding style rules, so this document may or may not have anything |
---|
.. | .. |
---|
226 | 227 | out of it. |
---|
227 | 228 | |
---|
228 | 229 | Then make the developer who really screwed up (if you can find them) know |
---|
229 | | -**in_private** that they screwed up. Not just so they can avoid it in the |
---|
| 230 | +**in private** that they screwed up. Not just so they can avoid it in the |
---|
230 | 231 | future, but so that they know they owe you one. And, perhaps even more |
---|
231 | 232 | importantly, they're also likely the person who can fix it. Because, let's |
---|
232 | 233 | face it, it sure ain't you. |
---|