Re: Odd git overrflow bug?

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Jul 10, 2016, 21:01 UTC
Message-ID: <CA+55aFyJP8FLaBtsMekzQDsCjDbFPa-qUZNHZNpvva2vZTRGgQ@mail.gmail.com>
In-Reply-To: <87eg712v5o.fsf@linux-m68k.org>

On Sun, Jul 10, 2016 at 11:41 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:

>
> I've seen that too, but only at the end of bisection, when it tries to
> display the bad commit.

That's apparently what the kernel bug reporter sees too now.

However, I cannot reproduce the problem with the particular kernel bisect that the reporter is using. Judging by what he bisected things down to, he must have done

    git bisect start
    git bisect bad 7ed18e2d1b6782989eb399ef79a8cc1a1b583b3c
    git bisect good 7ed18e2d1b6782989eb399ef79a8cc1a1b583b3c^
    git bisect good
    git bisect bad

but that works fine for me.

[ Oops. I tested something. It works for me with current git, but with git-2.9.0 I get the failure ].

I'll try to figure out why git-2.9.0 fails.

               Linus