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

[BUG] git bisect start fails when stale bisect data is left behind

From
JKJoel Kaasinen <joel@zenrobotics.com>
Date
Sep 5, 2011, 11:15 UTC
Message-ID
<CAC6WLetwT9UvBY_=Nf38hhkyU1mhmdWHWqscf3ebba1WRGS1LQ@mail.gmail.com>
Hi,

Just bumped into a weird bug: bisect refused to start. It seems some previous bisect had left around state that referred to a now-nonexistent branch.

How to reproduce: $ echo foo > .git/BISECT_START $ git bisect start HEAD HEAD^

Fails with "fatal: invalid reference:" on git 1.7.6.
–J
PS. Please CC me when answering, I'm not subscribed
Next: Christian Couder
Message 1 of 6 in “[BUG] git bisect start fails when stale bisect data is left behind”
  1. Joel KaasinenSep 5, 2011
  2. Christian CouderSep 6, 2011
  3. Junio C HamanoSep 6, 2011
  4. Christian CouderSep 7, 2011
  5. Joel KaasinenSep 7, 2011
  6. Junio C HamanoSep 7, 2011

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.