summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorKeiichi Kii <k-keiichi@bx.jp.nec.com>2007-10-26 10:51:44 +0400
committerGreg Kroah-Hartman <gregkh@suse.de>2007-10-31 07:52:33 +0300
commit5ab3bd5785774c4ae9dae87332d1d5bd6415c823 (patch)
treec2329692d6a20d2b121052ea93eb3593776b5dfb /Documentation
parent60b8cabd8e8a1d266aa8778957691cd925673083 (diff)
downloadlinux-5ab3bd5785774c4ae9dae87332d1d5bd6415c823.tar.xz
fix typo in SubmittingPatches
Fix typo. Signed-off-by: Keiichi Kii <k-keiichi@bx.jp.nec.com> Cc: Andy Whitcroft <apw@shadowen.org> Cc: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/SubmittingPatches4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index a30dd4480ad4..681e2b36195c 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -464,8 +464,8 @@ section Linus Computer Science 101.
Nuff said. If your code deviates too much from this, it is likely
to be rejected without further review, and without comment.
-Once significant exception is when moving code from one file to
-another in this case you should not modify the moved code at all in
+One significant exception is when moving code from one file to
+another -- in this case you should not modify the moved code at all in
the same patch which moves it. This clearly delineates the act of
moving the code and your changes. This greatly aids review of the
actual differences and allows tools to better track the history of