git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: bisect: "won't bisect on seeked tree"

From
Shawn O. Pearce <spearce@spearce.org>
Date
Feb 21, 2008, 05:43 UTC
Message-ID
<20080221054332.GB2887@spearce.org>
In-Reply-To
<1203572388.20492.0.camel@homer.simson.net>
Mike Galbraith <efault@gmx.de> wrote:
Show 11 quoted lines
> On Thu, 2008-02-21 at 00:33 -0500, Shawn O. Pearce wrote:
> > Mike Galbraith <efault@gmx.de> wrote:
> > > I have no idea how tree became "seeked", but would love to know how to
> > > "un-seek" it so I can proceed with a bisection.  Help?
> > 
> > I think you are already in the middle of a bisect.
> > 
> > Try "git bisect reset" first to get out of the current bisect before
> > starting another one.
> 
> It says "We are not bisecting".

Your repository is in a funny state. The file .git/BISECT_NAMES was removed but .git/head-name was not. Deleting .git/head-name should resolve the issue. But it would be interesting to know how the repository came into this state.

-- 
Shawn.
Previous: Mike GalbraithNext: Mike Galbraith
Message 4 of 11 in “bisect: "won't bisect on seeked tree"”
  1. Mike GalbraithFeb 21, 2008
  2. Shawn O. PearceFeb 21, 2008
  3. Mike GalbraithFeb 21, 2008
  4. Shawn O. PearceFeb 21, 2008
  5. Mike GalbraithFeb 21, 2008
  6. Eliminate confusing "won't bisect on seeked tree" failureCarl Worth, Feb 21, 2008
  7. Junio C HamanoFeb 22, 2008
  8. Karl HasselströmFeb 23, 2008
  9. Carl WorthFeb 23, 2008
  10. Junio C HamanoFeb 23, 2008
  11. Carl WorthFeb 24, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.