From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: mr/bisect-in-c-3, was Re: What's cooking in git.git (Oct 2020, #03; Mon, 19)
Date: Wed, 21 Oct 2020 16:48:03 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2010211647050.56@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqr1put77h.fsf@gitster.c.googlers.com>
Hi Junio,
On Mon, 19 Oct 2020, Junio C Hamano wrote:
> * mr/bisect-in-c-3 (2020-10-16) 7 commits
> - bisect--helper: retire `--bisect-autostart` subcommand
> - bisect--helper: retire `--write-terms` subcommand
> - bisect--helper: retire `--check-expected-revs` subcommand
> - bisect--helper: reimplement `bisect_state` & `bisect_head` shell functions in C
> - bisect--helper: retire `--next-all` subcommand
> - bisect--helper: retire `--bisect-clean-state` subcommand
> - bisect--helper: finish porting `bisect_start()` to C
>
> Rewriting "git bisect" in C continues.
>
> How ready is this one?
It has been reviewed _quite_ a couple of times over the course of 9
iterations, and I think it is ready now.
Thanks,
Dscho
next prev parent reply other threads:[~2020-10-21 14:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 18:13 What's cooking in git.git (Oct 2020, #03; Mon, 19) Junio C Hamano
2020-10-19 18:21 ` Eric Sunshine
2020-10-20 22:59 ` Junio C Hamano
2020-10-20 19:17 ` Preparing to rewind 'next' Junio C Hamano
2020-10-20 19:37 ` Matheus Tavares Bernardino
2020-10-21 14:48 ` Johannes Schindelin [this message]
2020-10-21 20:44 ` mr/bisect-in-c-3, was Re: What's cooking in git.git (Oct 2020, #03; Mon, 19) Junio C Hamano
2020-10-21 20:45 ` Junio C Hamano
2020-10-22 13:16 ` Johannes Schindelin
2020-10-23 8:02 ` Jeff King
2020-10-23 15:27 ` Junio C Hamano
2020-10-23 19:17 ` Elijah Newren
2020-10-27 8:39 ` Jeff King
2020-10-23 14:39 ` ak/corrected-commit-date, was " Jakub Narębski
2020-10-23 16:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.2010211647050.56@tvgsbejvaqbjf.bet \
--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.
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 NNTP newsgroup(s).