diff options
author | Jeremiah Mahler <jmmahler@gmail.com> | 2014-05-22 03:04:26 -0400 |
---|---|---|
committer | Jiri Kosina <jkosina@suse.cz> | 2014-06-19 09:28:56 -0400 |
commit | 305af08c5398bab6c7029da53eb15d85a53eef0e (patch) | |
tree | 8fcbf05d8272161e4a10ebe97963ffa72180d3bc /Documentation/SubmittingPatches | |
parent | fe786f61f32367e31d11a1b236aff29992d19a57 (diff) |
doc: replace "practise" with "practice" in Documentation
To keep the Documentation consistent either
"practise" or "practice" should be used.
Since there are 3 lines with "practise"
~/linux/Documentation$ grep -r practise * | wc -l
3
and 108 lines with "practice"
~/linux/Documentation$ grep -r practice * | wc -l
108
this patch converts "practise" to "practice".
Signed-off-by: Jeremiah Mahler <jmmahler@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/SubmittingPatches')
-rw-r--r-- | Documentation/SubmittingPatches | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 26b1e31d5a13..04c1eddb78aa 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches | |||
@@ -369,13 +369,13 @@ you are responsible for last-minute changes. Example : | |||
369 | [lucky@maintainer.example.org: struct foo moved from foo.c to foo.h] | 369 | [lucky@maintainer.example.org: struct foo moved from foo.c to foo.h] |
370 | Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org> | 370 | Signed-off-by: Lucky K Maintainer <lucky@maintainer.example.org> |
371 | 371 | ||
372 | This practise is particularly helpful if you maintain a stable branch and | 372 | This practice is particularly helpful if you maintain a stable branch and |
373 | want at the same time to credit the author, track changes, merge the fix, | 373 | want at the same time to credit the author, track changes, merge the fix, |
374 | and protect the submitter from complaints. Note that under no circumstances | 374 | and protect the submitter from complaints. Note that under no circumstances |
375 | can you change the author's identity (the From header), as it is the one | 375 | can you change the author's identity (the From header), as it is the one |
376 | which appears in the changelog. | 376 | which appears in the changelog. |
377 | 377 | ||
378 | Special note to back-porters: It seems to be a common and useful practise | 378 | Special note to back-porters: It seems to be a common and useful practice |
379 | to insert an indication of the origin of a patch at the top of the commit | 379 | to insert an indication of the origin of a patch at the top of the commit |
380 | message (just after the subject line) to facilitate tracking. For instance, | 380 | message (just after the subject line) to facilitate tracking. For instance, |
381 | here's what we see in 2.6-stable : | 381 | here's what we see in 2.6-stable : |