Re: [PATCH] bisect: Store first bad commit as comment in log file

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 22, 2013, 22:37 UTC
Message-ID: <7vwqrumbtg.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20130422222058.GF5650@pvv.ntnu.no>

Torstein Hegge <hegge@resisty.net> writes:

Show 16 quoted lines

> On Mon, Apr 22, 2013 at 14:13:00 -0700, Junio C Hamano wrote:
>> Torstein Hegge <hegge@resisty.net> writes:
>> 
>> > I took another look at this. I wasn't able to come up with anything
>> > useful for the "The merge base $rev is bad" case, but for the "only
>> > skipped commits left to test" case one could do something like this.
>> 
>> We skipped them because we can gain _no_ information from testing
>> these commits. They are not even "possibly bad", but are "unknown".
>> 
>> So it feels to me that by definition listing them would not be
>> useful. What am I missing?
>
> The information lies in that those commits are the only commits with an
> unknown state. So if the bisecter hands off the bisect log to someone
> else when they can't test further, the current status is recorded.

That is an interesting use case: "I've narrowed it down somewhat, but there are a few commits I do not have proper hardware for to test them, could you take it over from here?"