From: Nikita Makarov <n.makarov@yadro.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Bugreport: git log -L
Date: Mon, 21 Sep 2026 07:45:15 +0000 [thread overview]
Message-ID: <41c54b809eb1490fb467ba0fd4c5a8cf@yadro.com> (raw)
Hello, I have the found the strange behavior of "git log -L" command with python function.
It is counting a blank line that sits after a function's last statement as part of that function.
This happens only when the function is at the end of a file.
The way to reproduce that
git init repro && cd repro
git config user.email t@t && git config user.name t
printf 'def foo():\n return 1\n\n' > bug.py
git add bug.py && git commit -qm c1
printf 'def foo():\n return 1\n' > bug.py
git add bug.py && git commit -qm c2
Then do
git log -L :'foo':bug.py
And you'll see
Author: t <t@t>
Date: Fri Sep 18 18:21:10 2026 +0300
c2
diff --git a/bug.py b/bug.py
--- a/bug.py
+++ b/bug.py
@@ -1,2 +1,3 @@
def foo():
return 1
+
Though I expect that commit "c2" should never appear in log, since the changes from it doesn't affect the functions body at all.
[System Info]
git version:
git version 2.43.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 7.0.0-31-generic #31~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Aug 10 09:38:02 UTC 2 x86_64
compiler info: gnuc: 13.3
libc info: glibc: 2.39
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
next reply other threads:[~2026-09-21 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 7:45 Nikita Makarov [this message]
2026-09-21 9:49 ` Bugreport: git log -L Kristofer Karlsson
2026-09-21 16:40 ` Johannes Sixt
2026-09-21 18:04 ` Tim Tassonis
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=41c54b809eb1490fb467ba0fd4c5a8cf@yadro.com \
--to=n.makarov@yadro.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox