summaryrefslogtreecommitdiffstats
path: root/SubmittingPatches.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2018-07-18 13:16:48 -0700
committerJunio C Hamano <gitster@pobox.com>2018-07-18 13:16:48 -0700
commitea1ac8d6d6d8856d448e1f6e2d941f7663dc9ecd (patch)
tree50a7bda536235313b6288988e779c75bc53970e5 /SubmittingPatches.txt
parentec40f134aa677499a0c1bf7ea6133b7b5fe348c4 (diff)
downloadgit-htmldocs-ea1ac8d6d6d8856d448e1f6e2d941f7663dc9ecd.tar.gz
Autogenerated HTML docs for v2.18.0-232-gb7bd94
Diffstat (limited to 'SubmittingPatches.txt')
-rw-r--r--SubmittingPatches.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/SubmittingPatches.txt b/SubmittingPatches.txt
index 248854440..b44fd51f2 100644
--- a/SubmittingPatches.txt
+++ b/SubmittingPatches.txt
@@ -298,7 +298,7 @@ smaller project it is a good discipline to follow it.
The sign-off is a simple line at the end of the explanation for
the patch, which certifies that you wrote it or otherwise have
-the right to pass it on as a open-source patch. The rules are
+the right to pass it on as an open-source patch. The rules are
pretty simple: if you can certify the below D-C-O:
[[dco]]
@@ -403,7 +403,7 @@ don't demand). +git log -p {litdd} _$area_you_are_modifying_+ would
help you find out who they are.
. You get comments and suggestions for improvements. You may
- even get them in a "on top of your change" patch form.
+ even get them in an "on top of your change" patch form.
. Polish, refine, and re-send to the list and the people who
spend their time to improve your patch. Go back to step (2).