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: Re: js/bisect-in-c
Date: Fri, 27 May 2022 14:52:11 +0200 [thread overview]
Message-ID: <220527.86k0a72klr.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <xmqqo7zkxdvu.fsf@gitster.g>
On Thu, May 26 2022, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
>>>> Final bits of "git bisect.sh" have been rewritten in C.
>>>>
>>>> Will merge to 'next'?
>>>> source: <pull.1132.v3.git.1653144546.gitgitgadget@gmail.com>
>>>
>>> This topic has outstanding regressions in CLI parsing. I.e. we'll now
>>> offer to start bisection where we previously errored out on invalid
>>> command usage. See my replies in that thread.
>>
>> Pointers?
>
> I guess you meant this one?
>
> https://lore.kernel.org/git/220521.86zgjazuy4.gmgdl@evledraar.gmail.com/
Yes, sorry about the lack of specific reference upthread.
As noted after in
https://lore.kernel.org/git/220523.865ylwzgji.gmgdl@evledraar.gmail.com/
we're rewriting code in this case that doesn't have test coverage to
catch these regressions, so more than just a narrow bugfix I'd really
like to see a re-roll that gives some confidence that there aren't other
such issues by first adding missing test coverage.
next prev parent reply other threads:[~2022-05-27 13:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 8:41 What's cooking in git.git (May 2022, #07; Wed, 25) Junio C Hamano
2022-05-26 16:02 ` Victoria Dye
2022-05-26 17:23 ` Junio C Hamano
2022-05-26 18:02 ` Ævar Arnfjörð Bjarmason
2022-05-26 18:30 ` Victoria Dye
2022-05-26 18:40 ` Ævar Arnfjörð Bjarmason
2022-05-26 23:10 ` Junio C Hamano
2022-05-26 18:08 ` tb/cruft-packs (was Re: What's cooking in git.git (May 2022, #07; Wed, 25)) Taylor Blau
2022-05-26 18:10 ` What's cooking in git.git (May 2022, #07; Wed, 25) Taylor Blau
2022-05-26 20:17 ` Junio C Hamano
2022-05-26 18:11 ` tb/midx-race-in-pack-objects (was Re: What's cooking in git.git (May 2022, #07; Wed, 25)) Taylor Blau
2022-05-26 18:49 ` sg/build-gitweb (was: " Ævar Arnfjörð Bjarmason
2022-05-26 19:06 ` sg/build-gitweb Junio C Hamano
2022-05-26 18:51 ` jc/http-clear-finished-pointer (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
2022-05-26 19:37 ` Re* jc/http-clear-finished-pointer Junio C Hamano
2022-05-27 20:41 ` Johannes Schindelin
2022-05-27 21:35 ` Junio C Hamano
2022-06-01 7:26 ` Ævar Arnfjörð Bjarmason
2022-06-01 15:48 ` Junio C Hamano
2022-05-26 18:54 ` js/bisect-in-c (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
2022-05-26 19:38 ` js/bisect-in-c Junio C Hamano
2022-05-26 20:00 ` js/bisect-in-c Junio C Hamano
2022-05-27 12:52 ` Ævar Arnfjörð Bjarmason [this message]
2022-05-26 18:57 ` jx/l10n-workflow-change (was: What's cooking in git.git (May 2022, #07; Wed, 25)) Ævar Arnfjörð Bjarmason
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=220527.86k0a72klr.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=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).