Re: Clueless bisect error message

From: Junio C Hamano <junkio@cox.net>
Date: Oct 11, 2006, 08:11 UTC
Message-ID: <7v1wpfuv9d.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <fcaeb9bf0610110050h4c3a56fbge19607ff0bc094af@mail.gmail.com>

"Nguyen Thai Ngoc Duy" <pclouds@gmail.com> writes:

Show 7 quoted lines

>> By looking at commit 810255f, however, I suspect that fix would
>> break Cogito.  The wording of the message actually comes from
>> Cogito nomenclature.
> Ah. I forgot to say I'm using git 1.4.2.1. My only wish is not a fix
> (unless it's a trivial fix) but that bisect should explain the
> situation better and guide people to fix it. I had grepped bisect man
> page for "seeked tree" and was still clueless.

My point actually was that even a simple rewording is harder than it seems, because that cluelessness actually was introduced to help Cogito. If we do not care about it, we can just reword it to say "Hey you are in the middle of another bisect, or maybe you left your bisect by doing git-checkout earlier? In either case git-bisect --reset is your friend, oh, and we can run that for you now if you want". We could even remove head-name in git-checkout when we see one.

But I suspect that doing either of these things would harm Cogito users. After cg-seek the user is not "in the middle of another bisect", and if we run "git bisect --reset" when we see head-name, it would probably break it too.