Re: Clueless bisect error message

[Junio C Hamano <junkio@cox.net>]

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

> $ git bisect start
> won't bisect on seeked tree
>
> It complained because .git/head-name contained 't' which had been
> deleted before. git-bisect reset works. However I'd request git-bisect
> to inform more useful messages. At first, I was completely stunned:
> "what is a seeked tree? how can I fix that?"

Interesting.  There is certainly something clueless but I am not
sure if it is git-bisect.

Other git-core tools never create $GIT_DIR/head-name unless
bisect is in effect, and you end your bisect session by doing
"bisect reset" (otherwise there is no easy way to get back to
your original branch head).  How did head-name got 't' in it,
and how was branch 't' removed?

If the answer to the first question is because earlier you
created a temporary branch 't' to run a bisect, and the answer
to the latter is because you ended your bisect session by saying
"git checkout -f someotherbranch && git branch -D t", then we
should be able to fix that by removing head-name upon branch
switching with "git checkout".

By looking at commit 810255f, however, I suspect that fix would
break Cogito.  The wording of the message actually comes from
Cogito nomenclature.