Re: js/bisect-in-c

From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: js/bisect-in-c
Date: Thu, 26 May 2022 12:38:48 -0700	[thread overview]
Message-ID: <xmqq35gwyth3.fsf@gitster.g> (raw)
In-Reply-To: <220526.86r14g3yya.gmgdl@evledraar.gmail.com> (=?utf-8?B?IsOG?= =?utf-8?B?dmFyIEFybmZqw7Zyw7A=?= Bjarmason"'s message of "Thu, 26 May 2022 20:54:36 +0200")

Ævar Arnfjörð Bjarmason <avarab@gmail.com> 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@gmail.com>
>
> 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?