From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "Matthew Hughes" <matthewhughes934@gmail.com>, git@vger.kernel.org
Subject: Re: Crash on git log with -L and -G on file rename
Date: Tue, 03 Mar 2026 18:06:17 -0800 [thread overview]
Message-ID: <xmqqseag9wme.fsf@gitster.g> (raw)
In-Reply-To: <54a45011-c0f5-4852-b344-b81c36ed8924@app.fastmail.com> (Kristoffer Haugsbakk's message of "Wed, 04 Mar 2026 00:49:53 +0100")
"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.
next prev parent reply other threads:[~2026-03-04 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 20:42 Crash on git log with -L and -G on file rename Matthew Hughes
2026-03-03 23:49 ` Kristoffer Haugsbakk
2026-03-04 2:06 ` Junio C Hamano [this message]
2026-03-04 3:01 ` Koji Nakamaru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqseag9wme.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
--cc=matthewhughes934@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.