From: "Shawn O. Pearce" <spearce@spearce.org>
To: Mike Galbraith <efault@gmx.de>
Cc: git <git@vger.kernel.org>
Subject: Re: bisect: "won't bisect on seeked tree"
Date: Thu, 21 Feb 2008 00:43:32 -0500 [thread overview]
Message-ID: <20080221054332.GB2887@spearce.org> (raw)
In-Reply-To: <1203572388.20492.0.camel@homer.simson.net>
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.
--
Shawn.
next prev parent reply other threads:[~2008-02-21 5:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 5:20 bisect: "won't bisect on seeked tree" Mike Galbraith
2008-02-21 5:33 ` Shawn O. Pearce
2008-02-21 5:39 ` Mike Galbraith
2008-02-21 5:43 ` Shawn O. Pearce [this message]
2008-02-21 6:00 ` Mike Galbraith
2008-02-21 17:32 ` [PATCH] Eliminate confusing "won't bisect on seeked tree" failure Carl Worth
2008-02-22 17:18 ` Junio C Hamano
2008-02-23 9:21 ` Karl Hasselström
2008-02-23 18:33 ` Carl Worth
2008-02-23 22:59 ` Junio C Hamano
2008-02-24 1:14 ` Carl Worth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080221054332.GB2887@spearce.org \
--to=spearce@spearce.org \
--cc=efault@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.