git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: js/bisect-in-c, was Re: What's cooking in git.git (Aug 2022, #05; Mon, 15)
Date: Tue, 16 Aug 2022 10:56:58 +0200 (CEST)	[thread overview]
Message-ID: <p053rrpq-17q7-pnrs-3794-o04ro1445s5s@tzk.qr> (raw)
In-Reply-To: <xmqq5yityzcu.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]

Hi Junio,

On Mon, 15 Aug 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>
>  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

  reply	other threads:[~2022-08-16 10:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 21:24 What's cooking in git.git (Aug 2022, #05; Mon, 15) Junio C Hamano
2022-08-16  8:56 ` Johannes Schindelin [this message]
2022-08-17  1:26   ` js/bisect-in-c, was " Elijah Newren
2022-08-17  6:27     ` Johannes Schindelin
2022-08-17 18:57     ` Junio C Hamano
2022-08-17 19:24       ` Elijah Newren
2022-08-17 20:05         ` Junio C Hamano
2022-08-19 11:04           ` Johannes Schindelin
2022-08-19 14:40             ` Ævar Arnfjörð Bjarmason
2022-08-16 16:00 ` sy/mv-out-of-cone (was Re: What's cooking in git.git (Aug 2022, #05; Mon, 15)) Victoria Dye
2022-08-16 16:16   ` Junio C Hamano
2022-08-17  2:03   ` Shaoxuan Yuan
2022-08-17  0:36 ` cw/submodule-merge-messages (Was: " Elijah Newren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=p053rrpq-17q7-pnrs-3794-o04ro1445s5s@tzk.qr \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).