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

Re: "git bisect" takes exactly one bad commit and one or more good?

From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Date
Nov 12, 2017, 12:14 UTC
Message-ID
<1510488875.2683.3.camel@gmail.com>
In-Reply-To
<alpine.LFD.2.21.1711111024470.10756@localhost.localdomain>
On Sat, 2017-11-11 at 10:27 -0500, Robert P. J. Day wrote:
Show 8 quoted lines
> 
>   i realize that one of each commit is the simplest use case, but the
> scenario that occurred to me is a bunch of branches being merged and,
> suddenly, you have a bug, and you're not sure where it came from so
> you identify a number of good commits, one per merged branch, and go
> from there.
> 
>

Just thinking out loud, couldn't you give the one commit that was the tip of the branch, to which you merged the branches, before you merged in the branches as the good commit ?

-- 
Kaartic
Previous: Robert P. J. DayNext: Robert P. J. Day
Message 5 of 7 in “"git bisect" takes exactly one bad commit and one or more good?”
  1. Robert P. J. DayNov 11, 2017
  2. Christian CouderNov 11, 2017
  3. Junio C HamanoNov 11, 2017
  4. Robert P. J. DayNov 11, 2017
  5. Kaartic SivaraamNov 12, 2017
  6. Robert P. J. DayNov 11, 2017
  7. Stephan BeyerNov 12, 2017

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.