aboutsummaryrefslogtreecommitdiff
path: root/Documentation/SubmittingPatches
diff options
context:
space:
mode:
authorPavel Roskin <proski@gnu.org>2006-07-09 03:44:30 -0400
committerJunio C Hamano <junkio@cox.net>2006-07-09 02:42:41 -0700
commitaddf88e455f85bc6cfe0284b70aaad10b6d3486e (patch)
tree704e8b6de26fde0bff86618e363dbde9f70e1393 /Documentation/SubmittingPatches
parent88f0d5d7d95f815d2e8a36a8ceb7459dbd90992c (diff)
downloadgit-addf88e455f85bc6cfe0284b70aaad10b6d3486e.tar.gz
git-addf88e455f85bc6cfe0284b70aaad10b6d3486e.tar.xz
Assorted typo fixes
Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/SubmittingPatches')
-rw-r--r--Documentation/SubmittingPatches2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 8601949e8..90722c21f 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -49,7 +49,7 @@ People on the git mailing list need to be able to read and
comment on the changes you are submitting. It is important for
a developer to be able to "quote" your changes, using standard
e-mail tools, so that they may comment on specific portions of
-your code. For this reason, all patches should be submited
+your code. For this reason, all patches should be submitted
"inline". WARNING: Be wary of your MUAs word-wrap
corrupting your patch. Do not cut-n-paste your patch; you can
lose tabs that way if you are not careful.