Re: bisect: "won't bisect on seeked tree"
- From
- Mike Galbraith <efault@gmx.de>
- Date
- Feb 21, 2008, 06:00 UTC
- Message-ID
- <1203573624.20492.12.camel@homer.simson.net>
- In-Reply-To
- <20080221054332.GB2887@spearce.org>
On Thu, 2008-02-21 at 00:43 -0500, Shawn O. Pearce wrote:
Show 17 quoted lines
> Mike Galbraith <efault@gmx.de> wrote: > > 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.
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