From afc097786c68d3279cdc91bb3f0e9e43642b228c Mon Sep 17 00:00:00 2001 From: Linus Nilsson Date: Sat, 21 Jul 2007 17:49:06 +0200 Subject: [PATCH] --- yaml --- r: 62760 b: refs/heads/master c: f56d35e7aa78ac56a93ff43da90e8d90a37a1362 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/SubmittingPatches | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 99687e81981a..f308a52d74ce 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: e3202262eccf9b5669abea848303e79bd84dc1bb +refs/heads/master: f56d35e7aa78ac56a93ff43da90e8d90a37a1362 diff --git a/trunk/Documentation/SubmittingPatches b/trunk/Documentation/SubmittingPatches index 3f9a7912e69b..d6b45a9b29b4 100644 --- a/trunk/Documentation/SubmittingPatches +++ b/trunk/Documentation/SubmittingPatches @@ -122,7 +122,7 @@ then only post say 15 or so at a time and wait for review and integration. Check your patch for basic style violations, details of which can be found in Documentation/CodingStyle. Failure to do so simply wastes -the reviewers time and will get your patch rejected, probabally +the reviewers time and will get your patch rejected, probably without even being read. At a minimum you should check your patches with the patch style