> This looks like the stack trace in
> https://github.com/git-for-windows/git/issues/952, which was fixed by
> Johannes Schindelin in commit
> 55e9f0e5c ("merge-recursive: handle NULL in add_cacheinfo()
> correctly", 2016-11-26). Could you retry with a newer version of git?
A newer version (2.14.
On Wed, Jan 31, 2018 at 1:43 PM, Ayke van Laethem
wrote:
> Hi all,
>
> I've found a segmentation fault in git.
>
> Here, fabsf is a branch that I'm trying to get the topmost commit from.
> After the failed cherry-pick, the change is added to the local working
> tree, but the commit isn't applied a
Hi all,
I've found a segmentation fault in git.
Here, fabsf is a branch that I'm trying to get the topmost commit from.
After the failed cherry-pick, the change is added to the local working
tree, but the commit isn't applied and .git/index.lock still exists.
Version: 2.11.0 (Debian stretch)
~/
3 matches
Mail list logo