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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Torstein Hegge <hegge@xxxxxxxxxxx> 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?

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]