Le mardi 27 mars 2007 07:46, Junio C Hamano a écrit : [...] > So our requirement to have at least one good commit is not a > fundamental one, but only a practical one. > > We could give an --immediate (or --no-good) option to 'git > bisect bad' to start bisecting as soon as you give a single bad > commit. It might turn out that the commits you test are bad all > the way down to the root commit, though ;-). Yes, I plan to add some options to git bisect subcommands. For example "git bisect run" could accept the following options: --not mark current revision as bad instead of good and as good instead of bad --strict all exit code except 0 and 1 abort the bisect run process --good <rev1> --bad <rev2> use rev1 as good and rev2 as bad --check or --test run the script once and then do nothing if the result is good Are there other options that people want ? Thanks, Christian. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html