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@xxxxxxxxx/ > 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.
