Re: Feature request: Exponential search in git bisect
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Oct 26, 2020, 18:13 UTC
- Message-ID
- <xmqqpn54etyp.fsf@gitster.c.googlers.com>
- In-Reply-To
- <b1adedaa-5809-9ea1-f664-3a7cabaf0d14@iee.email>
Philip Oakley <philipoakley@iee.email> writes:
Show 9 quoted lines
>> 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.