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>
Subject: js/bisect-in-c (was: What's cooking in git.git (Dec 2022, #05; Wed, 14))
Date: Thu, 15 Dec 2022 10:49:44 +0100 [thread overview]
Message-ID: <221215.86mt7p2dx4.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqiliewbje.fsf@gitster.g>
On Wed, Dec 14 2022, Junio C Hamano wrote:
> * js/bisect-in-c (2022-08-30) 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
>
> Final bits of "git bisect.sh" have been rewritten in C.
>
> Tired of waiting for too long.
> source: <pull.1132.v6.git.1661885419.gitgitgadget@gmail.com>
I submitted
https://lore.kernel.org/git/cover-0.6-00000000000-20221215T094038Z-avarab@gmail.com/
just now, which cherry-picks the various small fixes from this topic.
next prev parent reply other threads:[~2022-12-15 9:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 9:59 What's cooking in git.git (Dec 2022, #05; Wed, 14) Junio C Hamano
2022-12-14 10:44 ` Junio C Hamano
2022-12-14 19:46 ` Taylor Blau
2022-12-14 15:09 ` Derrick Stolee
2022-12-14 23:50 ` Junio C Hamano
2022-12-14 19:09 ` Jeff Hostetler
2022-12-14 23:50 ` Junio C Hamano
2022-12-14 19:18 ` Jeff Hostetler
2022-12-15 22:37 ` Junio C Hamano
2022-12-15 9:14 ` ag/merge-strategies-in-c (was: What's cooking in git.git (Dec 2022, #05; Wed, 14)) Ævar Arnfjörð Bjarmason
2022-12-15 12:55 ` Phillip Wood
2022-12-15 15:32 ` Ævar Arnfjörð Bjarmason
2022-12-15 16:27 ` Phillip Wood
2022-12-15 16:29 ` Ævar Arnfjörð Bjarmason
2022-12-15 9:33 ` ab/remove--super-prefix & ab/submodule-no-abspath " Ævar Arnfjörð Bjarmason
2022-12-15 9:49 ` Ævar Arnfjörð Bjarmason [this message]
2022-12-15 11:55 ` What's cooking in git.git (Dec 2022, #05; Wed, 14) Sean Allred
2022-12-15 22:45 ` Junio C Hamano
2022-12-15 23:09 ` Junio C Hamano
2022-12-16 15:33 ` ds/bundle-uri-4* (was Re: What's cooking in git.git (Dec 2022, #05; Wed, 14)) Derrick Stolee
2022-12-16 22:55 ` 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=221215.86mt7p2dx4.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
/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).