Web lists-archives.com

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

On Sat, 2017-11-11 at 10:27 -0500, Robert P. J. Day wrote:
>   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 ?