Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> writes: > On Thu, May 26 2022, Junio C Hamano wrote: > >> * js/bisect-in-c (2022-05-21) 15 commits >> - bisect: no longer try to clean up left-over `.git/head-name` files >> - bisect: remove Cogito-related code >> - Turn `git bisect` into a full built-in >> - bisect: teach the `bisect--helper` command to show the correct usage strings >> - bisect: move even the command-line parsing to `bisect--helper` >> - bisect--helper: return only correct exit codes in `cmd_*()` >> - bisect--helper: move the `BISECT_STATE` case to the end >> - bisect--helper: make `--bisect-state` optional >> - bisect--helper: align the sub-command order with git-bisect.sh >> - bisect--helper: using `--bisect-state` without an argument is a bug >> - bisect--helper: really retire `--bisect-autostart` >> - bisect--helper: really retire --bisect-next-check >> - bisect--helper: retire the --no-log option >> - bisect: avoid double-quoting when printing the failed command >> - bisect run: fix the error message >> >> Final bits of "git bisect.sh" have been rewritten in C. >> >> Will merge to 'next'? >> source: <pull.1132.v3.git.1653144546.gitgitgadget@xxxxxxxxx> > > This topic has outstanding regressions in CLI parsing. I.e. we'll now > offer to start bisection where we previously errored out on invalid > command usage. See my replies in that thread. Pointers?
