All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: "Christian Couder" <christian.couder@gmail.com>,
	"Manuel Bärenz" <manuel@enigmage.de>, git <git@vger.kernel.org>
Subject: Re: Feature request: Exponential search in git bisect
Date: Mon, 26 Oct 2020 11:13:34 -0700	[thread overview]
Message-ID: <xmqqpn54etyp.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <b1adedaa-5809-9ea1-f664-3a7cabaf0d14@iee.email> (Philip Oakley's message of "Sun, 25 Oct 2020 17:15:20 +0000")

Philip Oakley <philipoakley@iee.email> writes:

>> Ok, but the conclusion of the above discussion is that the problem
>> with this idea is being able to distinguish between a commit that is
>> bad and a commit where the feature that you want to test cannot be
>> tested for example because it hasn't been implemented yet.
>
> Does any of the proposed improvement in the "bisect: loosen halfway()
> check for a large number of commits"
> https://lore.kernel.org/git/20201022103806.26680-1-szeder.dev@gmail.com/
> assist in this.

I doubt it.  

If you cannot say if a rev is testable or not, it would not help you
much if Git asked "is this good, bad or untestable?" question 5
times faster, I suspect.



  reply	other threads:[~2020-10-26 18:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 12:56 Feature request: Exponential search in git bisect Manuel Bärenz
2020-10-10  9:22 ` Christian Couder
2020-10-10  9:46   ` Christian Couder
2020-10-25 17:15   ` Philip Oakley
2020-10-26 18:13     ` Junio C Hamano [this message]
2020-10-26 20:59       ` Philip Oakley
2020-11-01 20:17     ` Manuel Bärenz
2020-10-27 12:10 ` Ævar Arnfjörð Bjarmason
2020-11-01 20:30   ` Manuel Bärenz
2020-11-02 10:36     ` Æ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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqpn54etyp.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=manuel@enigmage.de \
    --cc=philipoakley@iee.email \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.