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

Re: git bisect for reachable commits only

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 1, 2016, 16:49 UTC
Message-ID
<xmqqoa5cl9i7.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<2bfd9cf5-a9fa-7650-21e9-9ceb9cc34d8b@gmail.com>
Jakub Narębski <jnareb@gmail.com> writes:
> Isn't `--reachable-commits` the same as existing `--ancestry-path`
> option to `git log` and friends (I wonder if passing log options to
> bisect, that is: `git bisect --ancestry-path ...` would work)?

Yes, I somehow missed it, but you are absolutely correct to point out that what is being requested is --ancestry-path.

My gut feeling is that by default the command should be taught to follow the ancestry path, but I say this with reservation, as I am not sure offhand what it means to traverse along the ancestry path when there are multiple good commits.

Thanks.
Previous: Jakub NarębskiNext: Oleg Taranenko
Message 5 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.