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

Allow git bisect in reverse mode?

From
BDBrad Davis <bdavis@saintandreas.org>
Date
Sep 11, 2018, 19:52 UTC
Message-ID
<CAMK-fcye+nNyB9pFrp1nQwQC1+sQWMt_4yq2f7svJUiB=ZnnJA@mail.gmail.com>

I'm currently trying to determine when an issue was fixed in a long list of commits. I attempted to do this by running `git bisect` and marking the commit where I knew it was broken as bad, and the tip as good, but I got back an error message saying that good revs weren't ancestors of bad ones.

I'm currently working around this by mentally reversing the meanings of good and bad, but it feels unnatural and error prone to have to say `good` when I encounter the failure and `bad` when i don't.

Couldn't git simply do the same thing and internally reverse the meaning of good and bad if the bad revision is an ancestor of the good?

Next: Ævar Arnfjörð Bjarmason
Message 1 of 2 in “Allow git bisect in reverse mode?”
  1. Brad DavisSep 11, 2018
  2. Ævar Arnfjörð BjarmasonSep 11, 2018

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.