Re: [PATCH] Bisect: fix calculation of the number of suspicious revisions

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

 



Uwe Kleine-König  <ukleinek@xxxxxxxxxxxxxxxxxxxxxxxxxx> writes:

> Up to now the number printed was calculated assuming that the
> current revision to test is bad.  Given that it's not possible
> that this always matches the number of suspicious revs if the
> current one is good, the maximum of both is taken now.
>
> Moreover I think the number printed was always one to high,
> this is fixed, too.

I know you mean well, but is it really worth an extra rev-list
for this off-by-one, I wonder?

-
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]