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, #10; Tue, 30)
Date: Tue, 30 Aug 2022 22:40:51 +0200 (CEST) [thread overview]
Message-ID: <n1p36n77-2nn5-1740-40q7-9o17p8no994q@tzk.qr> (raw)
In-Reply-To: <xmqqilm9k0bc.fsf@gitster.g>
Hi Junio,
On Tue, 30 Aug 2022, Junio C Hamano wrote:
> * js/bisect-in-c (2022-08-27) 17 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--helper: make `state` optional
> - bisect--helper: calling `bisect_state()` without an argument is a bug
> - 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
> - bisect--helper: migrate to OPT_SUBCOMMAND()
> - bisect--helper: make the order consistently `argc, argv`
> - bisect--helper: make `terms` an explicit singleton
> - bisect--helper: simplify exit code computation
> - bisect--helper: really retire `--bisect-autostart`
> - bisect--helper: really retire --bisect-next-check
> - bisect--helper: retire the --no-log option
> - Merge branch 'sg/parse-options-subcommand' into js/bisect-in-c
> (this branch uses sg/parse-options-subcommand.)
>
> 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.v5.git.1661604264.gitgitgadget@gmail.com>
There exist two "rerolls" that were sent since that mail was sent ;-)
Ciao,
Dscho
next prev parent reply other threads:[~2022-08-30 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 19:17 What's cooking in git.git (Aug 2022, #10; Tue, 30) Junio C Hamano
2022-08-30 20:40 ` Johannes Schindelin [this message]
2022-08-31 8:00 ` jk/unused-annotation + ab/unused-annotation (was: What's cooking in git.git (Aug 2022, #10; Tue, 30)) Ævar Arnfjörð Bjarmason
2022-08-31 15:27 ` Jeff King
2022-08-31 16:23 ` jk/unused-annotation + ab/unused-annotation Junio C Hamano
2022-08-31 17:21 ` Ævar Arnfjörð Bjarmason
2022-08-31 8:29 ` js/add-p-diff-parsing-fix (was: What's cooking in git.git (Aug 2022, #10; Tue, 30)) Ævar Arnfjörð Bjarmason
2022-08-31 9:31 ` Phillip Wood
2022-08-31 19:54 ` Johannes Schindelin
2022-08-31 20:15 ` js/add-p-diff-parsing-fix Junio C Hamano
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=n1p36n77-2nn5-1740-40q7-9o17p8no994q@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).