Lines Matching full:good
21 # You must set the commit that was considered good (git bisect good)
28 # that requires to run a test to know if the bisect was good or bad.
29 # The test should exit with 0 on good, non-zero for bad. But see
33 # It is usually a good idea to confirm that the GOOD and the BAD
34 # commits are truly good and bad respectively. Having BISECT_CHECK
35 # set to 1 will check both that the good commit works and the bad
37 # set BISECT_CHECK to 'good' or to 'bad'.
39 #BISECT_CHECK = good
42 # Usually it's a good idea to specify the exact config you
66 # if the commit was good or bad. Instead, it will ask you to tell
67 # it if the current commit was good. In the mean time, you could
70 # ktest if you think it was good or not and ktest.pl will continue
77 # must be a superset of the good config. This is because it only
79 # good config is not a subset of the bad config, or if the target
89 # MIN_CONFIG as the good config.
90 CONFIG_BISECT_GOOD = ${THIS_DIR}/config-good