From 55f008e859b65ec04d6bd2131cb58618d9e277aa Mon Sep 17 00:00:00 2001 From: Jonathan Corbet Date: Thu, 8 Jan 2009 16:32:13 -0700 Subject: [PATCH] --- yaml --- r: 127867 b: refs/heads/master c: d5b524327b2a482dddae3839ced8f8825074730d h: refs/heads/master i: 127865: 140f3849f7f1c4abc6f4e2c0154119e7aac64eb1 127863: e8be41a01a1799c8f88a8c4fdb979447dbca12cc v: v3 --- [refs] | 2 +- trunk/Documentation/development-process/4.Coding | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/[refs] b/[refs] index 5431da7ec91b..a56a53f7d62c 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 2884f00b94be73a6a7875bada739bf9bb2f9a1b6 +refs/heads/master: d5b524327b2a482dddae3839ced8f8825074730d diff --git a/trunk/Documentation/development-process/4.Coding b/trunk/Documentation/development-process/4.Coding index 014aca8f14e2..a5a3450faaa0 100644 --- a/trunk/Documentation/development-process/4.Coding +++ b/trunk/Documentation/development-process/4.Coding @@ -375,10 +375,10 @@ say, this can be a large job, so it is best to be sure that the justification is solid. When making an incompatible API change, one should, whenever possible, -ensure that code which has not been updated is caught by the compiler. +ensure that code which has not been updated is caught by the compiler. This will help you to be sure that you have found all in-tree uses of that interface. It will also alert developers of out-of-tree code that there is a change that they need to respond to. Supporting out-of-tree code is not something that kernel developers need to be worried about, but we also do -not have to make life harder for out-of-tree developers than it it needs to -be. +not have to make life harder for out-of-tree developers than it needs to +be.