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.txt | |
| 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.txt')
| -rw-r--r-- | git-bisect-lk2009.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/git-bisect-lk2009.txt b/git-bisect-lk2009.txt index 6b7b2e549..86b3015c1 100644 --- a/git-bisect-lk2009.txt +++ b/git-bisect-lk2009.txt @@ -799,7 +799,7 @@ fixed in the "main" branch by commit "F"? 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! -And yes it's can happen in practice that people working on one branch +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 |