js/bisect-in-c, was Re: What's cooking in git.git (Jul 2022, #03; Mon, 11)

[Johannes Schindelin <Johannes.Schindelin@gmx.de>]

Hi Junio,

On Tue, 12 Jul 2022, Junio C Hamano wrote:

> * js/bisect-in-c (2022-06-27) 16 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: move even the command-line parsing to `bisect--helper`
>  - bisect: teach the `bisect--helper` command to show the correct usage strings
>  - 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
>  - bisect: verify that a bogus option won't try to start a bisection
>
>  Final bits of "git bisect.sh" have been rewritten in C.
>
>  Expecting a (hopefully final) reroll.
>  cf. <20627.86ilolhnnn.gmgdl@evledraar.gmail.com>

I did not find that one, but I found
https://lore.kernel.org/git/220627.86ilolhnnn.gmgdl@evledraar.gmail.com/

And that claims that Git has a convention to universally exit with code
129 when options are passed with incorrect values.

That claim does not survive even minimal contact with Git's source
code, though.

If I find some time, I will respond to that mail, but a reroll is actually
unnecessary.

>  source: <pull.1132.v4.git.1656354677.gitgitgadget@gmail.com>

Thanks,
Dscho