diff options
author | Junio C Hamano <junio@kernel.org> | 2010-08-18 22:15:35 +0000 |
---|---|---|
committer | Junio C Hamano <junio@kernel.org> | 2010-08-18 22:15:35 +0000 |
commit | 619596afe5769620cfbaca941f701a3fa106e6e5 (patch) | |
tree | a0065a9102205adf638a7ff9e35bb50ce049dcd0 /git-bisect-lk2009.html | |
parent | b5a296fa6d8cd1a703ce2eb6232e0bbc654bd2a2 (diff) | |
download | git-htmldocs-619596afe5769620cfbaca941f701a3fa106e6e5.tar.gz |
Autogenerated HTML docs for v1.7.2.1-158-gbd3a97
Diffstat (limited to 'git-bisect-lk2009.html')
-rw-r--r-- | git-bisect-lk2009.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/git-bisect-lk2009.html b/git-bisect-lk2009.html index 0d0619f3c..394a19bbf 100644 --- a/git-bisect-lk2009.html +++ b/git-bisect-lk2009.html @@ -1104,7 +1104,7 @@ logical change in each commit.</p></div> <div class="para"><p>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.</p></div>
+only reviewed by the committer.</p></div>
<div class="para"><p>Another good idea is to have good commit messages. They can be very
helpful to understand why some changes were made.</p></div>
<div class="para"><p>These general best practices are very helpful if you bisect often.</p></div>
@@ -1472,7 +1472,7 @@ author to given a talk and for publishing this paper.</p></div> </div>
<div id="footer">
<div id="footer-text">
-Last updated 2010-07-21 21:55:45 UTC
+Last updated 2010-08-18 22:14:55 UTC
</div>
</div>
</body>
|