From: Nguyen Thai Ngoc Duy Date: Wed, 11 Oct 2006 07:50:28 GMT Subject: Re: Clueless bisect error message Message-ID: In-Reply-To: <7vpsczuxj9.fsf@assigned-by-dhcp.cox.net> On 10/11/06, Junio C Hamano wrote: > "Nguyen Thai Ngoc Duy" 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? Well, I probably removed it myself. It's one of my temporary branches IIRC. Perhaps I forgot to do "bisect reset". > > 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". That might be the case. I used bisect on this repo a long ago. I'm not sure what actually happened. > > 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. -- Duy