From: van den Berg, Kasper <kasper_vandenberg@reyrey.com>
Date: Tue, 03 Sep 2019 06:34:30 GMT
Subject: RE: git range-diff <range1> <range2> throws Segmentation fault
Message-ID: <a675af41c66a457f97fe0e61d914fe58@EML-MBX11-DAY.ad.reyrey.com>
In-Reply-To: <nycvar.QRO.7.76.6.1908302147490.46@tvgsbejvaqbjf.bet>

Hi Johannes, hello Thomas,

Currently, I'm approaching a release deadline and there are some tasks with higher priority waiting for me and creating a MCVE takes some time.  Creating the stacktrace and ensuring I don't leak proprietary code also takes more time than I can currently afford.
In two weeks I might have more time.  If needed, I will try to help with appropriate error data and/or a reproduction.

With kind regards,
Kasper van den Berg

-----Oorspronkelijk bericht-----
Van: Johannes Schindelin <Johannes.Schindelin@gmx.de> 
Verzonden: vrijdag 30 augustus 2019 21:49
Aan: van den Berg, Kasper <Kasper_vandenBerg@reyrey.com>
CC: git@vger.kernel.org
Onderwerp: Re: git range-diff <range1> <range2> throws Segmentation fault

Hi Kasper,

On Fri, 30 Aug 2019, van den Berg, Kasper wrote:

> `git range-diff <range1> <range2>` prints "segmentation fault" to the 
> console and nothing else.  It happens in git version 2.23.0.windows.1 
> and only occurs for some branches in my repository.

Maybe you can come up with a Minimal, Complete and Verifiable Example (https://stackoverflow.com/help/mcve)?

Ciao,
Johannes