Re: [PATCH] Bisect: fix calculation of the number of suspicious revisions
- From
Junio C Hamano <junkio@cox.net>
- Date
- Mar 21, 2007, 21:23 UTC
- Message-ID
- <7vodmmz3wy.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <20070321210454.GA2844@lala>
Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de> writes:
Show 7 quoted lines
> 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?