git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Crash on git log with -L and -G on file rename

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 4, 2026, 02:06 UTC
Message-ID
<xmqqseag9wme.fsf@gitster.g>
In-Reply-To
<54a45011-c0f5-4852-b344-b81c36ed8924@app.fastmail.com>
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
Show 6 quoted lines
> 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.
Previous: Kristoffer HaugsbakkNext: Koji Nakamaru
Message 3 of 4 in “Crash on git log with -L and -G on file rename”
  1. Matthew HughesMar 3, 2026
  2. Kristoffer HaugsbakkMar 3, 2026
  3. Junio C HamanoMar 4, 2026
  4. Koji NakamaruMar 4, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.