On Tue, Sep 11, 2018 at 8:27 AM ryenus <ryenus@xxxxxxxxx> wrote:
>
> I just updated to 2.19 via Homebrew, git range-diff seems cool, but I
> only got a Segmentation fault: 11
>
> $ git version; git range-diff origin/master HEAD@{2} HEAD
> git version 2.19.0
> Segmentation fault: 11
>
> Both origin/master and my local branch each got two new commits of their own,
> please correct me if this is not the expected way to use git range-diff.
>
> FYI, I've created a sample repo here:
> https://github.com/ryenus/range-diff-segfault/
Thanks for the report and coming up with a sample repo. However,
reflogs don't transfer with clones, and your origin/master may well
point somewhere different than ours. Could you run
git rev-parse origin/master HEAD@{2} HEAD
in the range-diff-segfault repo where you can reproduce so we know
what commits to pass to trigger the bug?
