From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 04 Mar 2026 02:06:17 GMT
Subject: Re: Crash on git log with -L and -G on file rename
Message-ID: <xmqqseag9wme.fsf@gitster.g>
In-Reply-To: <54a45011-c0f5-4852-b344-b81c36ed8924@app.fastmail.com>

"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:

> I was able to reproduce this on `master`, `next`, and `seen`.
>
> • master: 50d063e3 (The 10th batch, 2026-03-03)
> • seen: 62670724 (Merge branch 'ng/submodule-default-remote' into seen,
>   2026-03-03)
> • 87284122 (Sync with 'master', 2026-03-03)

Not surprised, as I do not recall we made any changes to code paths
around either -L nor -G for quite some time.  I wouldn't be
surprised if this were broken exactly the same way since the
inception of the -L option, but bisecting might shed some lights on
the root cause, perhaps?

Thanks.