git/list[1] front-page[2] threads[3] people[4] search[5] about
 

js/bisect-in-c, was Re: What's cooking in git.git (Aug 2022, #05; Mon, 15)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 16, 2022, 08:56 UTC
Message-ID
<p053rrpq-17q7-pnrs-3794-o04ro1445s5s@tzk.qr>
In-Reply-To
<xmqq5yityzcu.fsf@gitster.g>
Hi Junio,
On Mon, 15 Aug 2022, Junio C Hamano wrote:
Show 23 quoted lines
> * 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>
>  source: <pull.1132.v4.git.1656354677.gitgitgadget@gmail.com>

I had another look at the thread and did not see any feedback that focuses on the actual scope of the patch series. Conversions from scripted parts of Git to built-ins are always a bit finicky (and hard to review, I admit).

Therefore I would like to move the status to "needs review".

I do not think that there are any major issues with it (Ævar's feedback notwithstanding, it focuses on tangents that should be addressed after the conversion, to avoid losing focus), but I would love to see a thorough review of the conversion to avoid obvious regressions like the one in the built-in interactive `add` I had to fix recently.

Ciao, Dscho

Previous: Junio C HamanoNext: Elijah Newren
Message 2 of 13 in “What's cooking in git.git (Aug 2022, #05; Mon, 15)”
  1. Junio C HamanoAug 15, 2022
  2. js/bisect-in-c, was Re: What's cooking in git.git (Aug 2022, #05; Mon, 15)Johannes Schindelin, Aug 16, 2022
  3. Elijah NewrenAug 17, 2022
  4. Johannes SchindelinAug 17, 2022
  5. Junio C HamanoAug 17, 2022
  6. Elijah NewrenAug 17, 2022
  7. Junio C HamanoAug 17, 2022
  8. Johannes SchindelinAug 19, 2022
  9. Ævar Arnfjörð BjarmasonAug 19, 2022
  10. sy/mv-out-of-cone (was Re: What's cooking in git.git (Aug 2022, #05; Mon, 15))Victoria Dye, Aug 16, 2022
  11. Junio C HamanoAug 16, 2022
  12. Shaoxuan YuanAug 17, 2022
  13. cw/submodule-merge-messages (Was: Re: What's cooking in git.git (Aug 2022, #05; Mon, 15))Elijah Newren, Aug 17, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.