summaryrefslogtreecommitdiffstats
path: root/git-bisect-lk2009.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junio@kernel.org>2010-08-18 22:15:35 +0000
committerJunio C Hamano <junio@kernel.org>2010-08-18 22:15:35 +0000
commit619596afe5769620cfbaca941f701a3fa106e6e5 (patch)
treea0065a9102205adf638a7ff9e35bb50ce049dcd0 /git-bisect-lk2009.txt
parentb5a296fa6d8cd1a703ce2eb6232e0bbc654bd2a2 (diff)
downloadgit-htmldocs-619596afe5769620cfbaca941f701a3fa106e6e5.tar.gz
Autogenerated HTML docs for v1.7.2.1-158-gbd3a97
Diffstat (limited to 'git-bisect-lk2009.txt')
-rw-r--r--git-bisect-lk2009.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/git-bisect-lk2009.txt b/git-bisect-lk2009.txt
index 86b3015c1..efbe3790b 100644
--- a/git-bisect-lk2009.txt
+++ b/git-bisect-lk2009.txt
@@ -971,7 +971,7 @@ logical change in each commit.
The smaller the changes in your commit, the most effective "git
bisect" will be. And you will probably need "git bisect" less in the
first place, as small changes are easier to review even if they are
-only reviewed by the commiter.
+only reviewed by the committer.
Another good idea is to have good commit messages. They can be very
helpful to understand why some changes were made.