Re: git-merge-recursive segmentation error

Luben Tuikov [off-list ref] writes:

I also ran git-bisect twice over two well known but overlapping
good-bad regions and I get the same commit as being the culprit.
It seems to be commit 1510fea781cb0517eeba8c378964f7bc4f9577ab.

    Luben

Ooooooops.