diff options
| author | Junio C Hamano <junio@kernel.org> | 2010-01-31 23:04:31 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@kernel.org> | 2010-01-31 23:04:31 +0000 |
| commit | 167b1384c594ba1ce67e6aae4e4c3cfb304bf025 (patch) | |
| tree | 31e32edd1f8c3544e90e2768653cffa0be026cf1 /git-bisect-lk2009.html | |
| parent | 197c229dba62a22dd8e42d6fc026a00de2944081 (diff) | |
| download | git-htmldocs-167b1384c594ba1ce67e6aae4e4c3cfb304bf025.tar.gz | |
Autogenerated HTML docs for v1.7.0-rc1-7-gc0da5
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 33ae16987..3125f8ee1 100644 --- a/git-bisect-lk2009.html +++ b/git-bisect-lk2009.html @@ -966,7 +966,7 @@ too.</p></div> fixed in the "main" branch by commit "F"?</p></div>
<div class="para"><p>The result of such a bisection would be that we would find that H is
the first bad commit, when in fact it's B. So that would be wrong!</p></div>
-<div class="para"><p>And yes it's can happen in practice that people working on one branch
+<div class="para"><p>And yes it can happen in practice that people working on one branch
are not aware that people working on another branch fixed a bug! It
could also happen that F fixed more than one bug or that it is a
revert of some big development effort that was not ready to be
@@ -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 2009-12-03 09:12:57 UTC
+Last updated 2010-01-31 23:03:59 UTC
</div>
</div>
</body>
|