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

Re: [PATCH] Add command `git bisect state` that checks if the current bisection process has reached the first bad commit.

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 18, 2013, 21:39 UTC
Message-ID
<7vmwoen0g8.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130816065410.56665c03.maandree@kth.se>
Mattias Andrée <maandree@member.fsf.org> writes:
Show 8 quoted lines
> This patch allows you to an automated by section
> by just like if it was a manual, i.e. stating
> with `git bisect start && git bisect bad &&
> git bisect good <commit>` but then type:
>
> while ! git bisect state; do
> <test command> && git bisect good || git bisect bad
> done
Hmph, so this is "git bisect run" turned inside out?
Previous: Mattias Andrée
Message 4 of 4 in “Add command `git bisect state` that checks if the current bisection process has reached the first bad commit.”
  1. Add command `git bisect state` that checks if the current bisection process has reached the first bad commit.Mattias Andrée, Aug 15, 2013
  2. Eric SunshineAug 16, 2013
  3. Mattias AndréeAug 16, 2013
  4. Junio C HamanoAug 18, 2013

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.