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

git bisect should return 1 when the first bad commit is found

From
PLPedro Larroy <pedro.larroy.lists@gmail.com>
Date
Jun 12, 2019, 22:33 UTC
Message-ID
<CAC_CU1iWBCTt5jLQ0Zp2HoyA0oFgG3shDB2rLfOsmC+x67NdAw@mail.gmail.com>
Hi

I'm using git bisect, and for complex reasons I can't use git bisect run to drive the bisection. I don't think git bisect bad/good is returning a different status code when the first bad commit is found and this would be very useful to stop the driver of the bisection.

What do you think?  Would such a change be acceptable?
Thank you!
Pedro.
Next: Junio C Hamano
Message 1 of 9 in “git bisect should return 1 when the first bad commit is found”
  1. Pedro LarroyJun 12, 2019
  2. Junio C HamanoJun 13, 2019
  3. Pedro LarroyJun 23, 2019
  4. Jeff KingJun 23, 2019
  5. Christian CouderJun 24, 2019
  6. Jeff KingJun 25, 2019
  7. Junio C HamanoJun 24, 2019
  8. Jeff KingJun 25, 2019
  9. Junio C HamanoJun 25, 2019

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.