Re: Feature request: git bisect merge to usable base

From: Christian Couder <christian.couder@gmail.com>
Date: Dec 30, 2015, 18:54 UTC
Message-ID: <CAP8UFD3vc+gZtPpWKgFug1NUXc3WzPFwtoNaZLiNiW5oW-WAqA@mail.gmail.com>
In-Reply-To: <CALCETrUgsawpwkkjO_BpPHyOaH7NsJNU-4mF97a6NAxCMB5aUA@mail.gmail.com>

Hi,

On Wed, Dec 30, 2015 at 11:40 AM, Andy Lutomirski <luto@kernel.org> wrote:

Show 16 quoted lines

> Hi-
>
> I'm currently bisecting a Linux bug on my laptop.  The starting good
> commit is v4.4-rc3 and the starting bad commit is v4.4-rc7.
> Unfortunately, anything much older than v4.4-rc3 doesn't boot at all.
>
> I'd like to say:
>
> $ git bisect merge-to v4.4-rc3
>
> or similar.  The effect would be that, rather than testing commits in
> between the good and bad commits, it would test the result of merging
> those commits with v4.4-rc3.
>
> Obviously the syntax could be tweaked a lot, but I think the concept
> could be quite handy.

There have been talks about bisecting on the first parents and I think it would be useful in your case. After bisecting on the first parents you would know which merged branch is responsible for the bug and you could for example rebase it on top of v4.4-rc3 and then bisect on it.

You may find some scripts that might help you by searching for "bisect first parent", like maybe there:

http://stackoverflow.com/questions/20240526/how-to-git-bisect-only-on-one-branchs-commits

Or maybe some old patchs on this list.

Best, Christian.