X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=Documentation%2Fstable_kernel_rules.txt;h=c815c5206e8401e7f1f7c188bdd4b70beb27d787;hb=97bf2856c6014879bd04983a3e9dfcdac1e7fe85;hp=e409e5d0748601db721967bbaf631a87e3020832;hpb=76828883507a47dae78837ab5dec5a5b4513c667;p=linux-2.6.git diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt index e409e5d07..c815c5206 100644 --- a/Documentation/stable_kernel_rules.txt +++ b/Documentation/stable_kernel_rules.txt @@ -4,7 +4,7 @@ Rules on what kind of patches are accepted, and which ones are not, into the "-stable" tree: - It must be obviously correct and tested. - - It can not be bigger than 100 lines, with context. + - It cannot be bigger than 100 lines, with context. - It must fix only one thing. - It must fix a real bug that bothers people (not a, "This could be a problem..." type thing). @@ -14,7 +14,7 @@ Rules on what kind of patches are accepted, and which ones are not, into the critical. - No "theoretical race condition" issues, unless an explanation of how the race can be exploited is also provided. - - It can not contain any "trivial" fixes in it (spelling changes, + - It cannot contain any "trivial" fixes in it (spelling changes, whitespace cleanups, etc). - It must be accepted by the relevant subsystem maintainer. - It must follow the Documentation/SubmittingPatches rules. @@ -50,7 +50,7 @@ Review cycle: Contact the kernel security team for more details on this procedure. -Review committe: +Review committee: - This is made up of a number of kernel developers who have volunteered for this task, and a few that haven't.