From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2021, #06; Sat, 30)
Date: Wed, 3 Feb 2021 08:08:45 +0700 [thread overview]
Message-ID: <YBn3ndkwo9qvXHFr@danh.dev> (raw)
In-Reply-To: <xmqqsg6infev.fsf@gitster.c.googlers.com>
On 2021-01-30 16:00:56-0800, Junio C Hamano <gitster@pobox.com> wrote:
> * mr/bisect-in-c-4 (2021-01-26) 7 commits
> - bisect--helper: retire `--check-and-set-terms` subcommand
> - bisect--helper: reimplement `bisect_skip` shell function in C
> - bisect--helper: retire `--bisect-auto-next` subcommand
> - bisect--helper: use `res` instead of return in BISECT_RESET case option
> - bisect--helper: retire `--bisect-write` subcommand
> - bisect--helper: reimplement `bisect_replay` shell function in C
> - bisect--helper: reimplement `bisect_log` shell function in C
>
> Piecemeal of rewrite of "git bisect" in C continues.
>
> Will merge to 'next'.
I think the bisect_log still haven't added back the:
We are not bisecting
as addressing in gohp6kv9bml9qc.fsf@gmail.com
--
Danh
next prev parent reply other threads:[~2021-02-03 1:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 0:00 What's cooking in git.git (Jan 2021, #06; Sat, 30) Junio C Hamano
2021-01-31 1:42 ` Taylor Blau
2021-01-31 20:50 ` Junio C Hamano
2021-01-31 17:21 ` SZEDER Gábor
2021-01-31 20:52 ` Junio C Hamano
2021-01-31 20:11 ` Derrick Stolee
2021-01-31 20:53 ` Junio C Hamano
2021-02-01 0:27 ` Ævar Arnfjörð Bjarmason
2021-02-01 1:48 ` Junio C Hamano
2021-02-02 15:54 ` Johannes Schindelin
2021-02-02 20:18 ` Junio C Hamano
2021-02-01 15:51 ` Charvi Mendiratta
2021-02-01 19:48 ` Junio C Hamano
2021-02-02 15:28 ` Charvi Mendiratta
2021-02-03 1:08 ` Đoàn Trần Công Danh [this message]
2021-02-03 1:22 ` Junio C Hamano
2021-02-03 22:00 ` Miriam R.
2021-02-04 1:38 ` 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=YBn3ndkwo9qvXHFr@danh.dev \
--to=congdanhqx@gmail.com \
--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).