[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1193807505-3821-5-git-send-email-gregkh@suse.de>
Date: Tue, 30 Oct 2007 22:11:44 -0700
From: Greg Kroah-Hartman <gregkh@...e.de>
To: linux-kernel@...r.kernel.org
Cc: Keiichi Kii <k-keiichi@...jp.nec.com>,
Andy Whitcroft <apw@...dowen.org>,
Randy Dunlap <randy.dunlap@...cle.com>,
Greg Kroah-Hartman <gregkh@...e.de>
Subject: [PATCH 5/6] fix typo in SubmittingPatches
From: Keiichi Kii <k-keiichi@...jp.nec.com>
Fix typo.
Signed-off-by: Keiichi Kii <k-keiichi@...jp.nec.com>
Cc: Andy Whitcroft <apw@...dowen.org>
Cc: Randy Dunlap <randy.dunlap@...cle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@...e.de>
---
Documentation/SubmittingPatches | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index a30dd44..681e2b3 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
--
1.5.3.4
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists