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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2008-02-21 at 00:43 -0500, Shawn O. Pearce wrote:
> Mike Galbraith <efault@xxxxxx> wrote:
> > On Thu, 2008-02-21 at 00:33 -0500, Shawn O. Pearce wrote:
> > > Mike Galbraith <efault@xxxxxx> 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.

Bingo, thanks!

There's only one git user here, so I have a good idea who to blame...
but he (me) is claiming innocence.  The content of head-name was
"master" fwiw.

	-Mike

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux