From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Elijah Newren <newren@gmail.com>
Subject: js/bisect-in-c (was: What's cooking in git.git (Aug 2022, #06; Wed, 17))
Date: Thu, 18 Aug 2022 14:42:53 +0200 [thread overview]
Message-ID: <220818.86czcxafew.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqq7d36s31e.fsf@gitster.g>
On Wed, Aug 17 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>
The msgid here is typo'd, the correct one is
https://lore.kernel.org/git/220627.86ilolhnnn.gmgdl@evledraar.gmail.com/
(i.e. a "2" is missing from the front).
The more recent
https://lore.kernel.org/git/220817.86pmgzabv0.gmgdl@evledraar.gmail.com/
also has some more follow-up, and a proposed fix-up for one of the
issues I noted with the series (the completion helper interaction with
the new "bisect").
next prev parent reply other threads:[~2022-08-18 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 2:23 What's cooking in git.git (Aug 2022, #06; Wed, 17) Junio C Hamano
2022-08-18 12:42 ` Ævar Arnfjörð Bjarmason [this message]
2022-08-19 11:06 ` js/bisect-in-c (was: What's cooking in git.git (Aug 2022, #06; Wed, 17)) Johannes Schindelin
2022-08-19 14:28 ` Ævar Arnfjörð Bjarmason
2022-08-18 13:18 ` What's cooking in git.git (Aug 2022, #06; Wed, 17) Derrick Stolee
2022-08-18 13:19 ` Derrick Stolee
2022-08-18 15:00 ` ds/* (was Re: What's cooking in git.git (Aug 2022, #06; Wed, 17)) Derrick Stolee
2022-08-18 17:39 ` Junio C Hamano
2022-08-18 18:12 ` vd/* (was: " Victoria Dye
2022-08-18 19:09 ` vd/* Junio C Hamano
2022-08-18 22:42 ` What's cooking in git.git (Aug 2022, #06; Wed, 17) Jonathan Tan
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=220818.86czcxafew.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.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).