summaryrefslogtreecommitdiffstats
path: root/git-bisect-lk2009.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2019-12-01 14:58:27 -0800
committerJunio C Hamano <gitster@pobox.com>2019-12-01 14:58:27 -0800
commit8ef91f31f6606a0370b18943c3b0f089e04873f9 (patch)
tree2bf27a3779a34fa4bf69dfc02e1fe1be848ea0d2 /git-bisect-lk2009.html
parent8ac8a3d8dd001611b77776fa19ef37c2c87cd987 (diff)
downloadgit-htmldocs-8ef91f31f6606a0370b18943c3b0f089e04873f9.tar.gz
Autogenerated HTML docs for v2.24.0-308-g228f5
Diffstat (limited to 'git-bisect-lk2009.html')
-rw-r--r--git-bisect-lk2009.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/git-bisect-lk2009.html b/git-bisect-lk2009.html
index f1f1b1b25..478bcf6d0 100644
--- a/git-bisect-lk2009.html
+++ b/git-bisect-lk2009.html
@@ -886,7 +886,7 @@ test suites and tools similar as "git bisect".</p></div>
supposed to be used so that all the tests are checked after each
commit. This means that they are not very efficient, because many
tests are run for no interesting result, and they suffer from
-combinational explosion.</p></div>
+combinatorial explosion.</p></div>
<div class="paragraph"><p>In fact the problem is that big software often has many different
configuration options and that each test case should pass for each
configuration after each commit. So if you have for each release: N
@@ -1983,7 +1983,7 @@ author to given a talk and for publishing this paper.</p></div>
<div id="footer">
<div id="footer-text">
Last updated
- 2018-10-30 16:33:48 JST
+ 2019-12-01 14:55:34 PST
</div>
</div>
</body>