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

git bisect for reachable commits only

From
Oleg Taranenko <olegtaranenko@gmail.com>
Date
Jul 29, 2016, 08:53 UTC
Message-ID
<CABEd3j8VLbpeWbA6BfHYp5aLPEy0PesqYoHM9u4OM=b7Qm=LDg@mail.gmail.com>
Hi all,

I just found an interesting post how git bisect can trouble humans. Full story is here https://groups.google.com/forum/#!topic/git-users/v3__t42qbKE

My suggestion to fix it (ditto)
What I suggest change logic of bisecting to something like
      git config bisect.reachable true

This behaviour will reduce bisecting only to reachable commits between bad/good points and will never goes away.

Maybe if commit will be found at merge commit git bisect can suggest open another round trip to looking into not reachable way, but anyway it should be explicit confirmed by user.

BTW, if bad commit is merge point with more than 2 parents, how git bisect will find "first wrong commit" at the current state?

Thanks for the attention,
Oleg
Next: Junio C Hamano
Message 1 of 14 in “git bisect for reachable commits only”
  1. Oleg TaranenkoJul 29, 2016
  2. Junio C HamanoJul 29, 2016
  3. Oleg TaranenkoJul 31, 2016
  4. Jakub NarębskiJul 31, 2016
  5. Junio C HamanoAug 1, 2016
  6. Oleg TaranenkoAug 1, 2016
  7. Christian CouderAug 1, 2016
  8. Junio C HamanoAug 1, 2016
  9. Christian CouderAug 1, 2016
  10. Junio C HamanoAug 1, 2016
  11. Oleg TaranenkoAug 2, 2016
  12. Stefan BellerAug 2, 2016
  13. Junio C HamanoAug 2, 2016
  14. Oleg TaranenkoAug 4, 2016

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.