diff options
| author | Ralf Wildenhues <Ralf.Wildenhues@gmx.de> | 2010-01-31 14:24:39 +0100 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2010-01-31 10:24:53 -0800 |
| commit | 6a5d0b0a90789ed92cb87f1b69cfeef2a1db3566 (patch) | |
| tree | 7e41d2a126b9090d7d3eaaa37c4dead8ce2a090a /Documentation/git-bisect-lk2009.txt | |
| parent | b0883aa6c77111e88496bd0afe073caf68ab9f99 (diff) | |
| download | git-6a5d0b0a90789ed92cb87f1b69cfeef2a1db3566.tar.gz | |
Fix typos in technical documentation.
Signed-off-by: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-bisect-lk2009.txt')
| -rw-r--r-- | Documentation/git-bisect-lk2009.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-bisect-lk2009.txt b/Documentation/git-bisect-lk2009.txt index 6b7b2e5497..86b3015c13 100644 --- a/Documentation/git-bisect-lk2009.txt +++ b/Documentation/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 |