From: Robin Vagner <robin.vagner@unit-image.fr>
To: git@vger.kernel.org
Subject: git log -L:<funcname>:<file> bug report
Date: Wed, 22 Mar 2023 11:05:52 +0100 [thread overview]
Message-ID: <CAHadCYLUTxzBYk+jw1Eg9FrP2Abn_qTyAvGBPeoi=Cwum2FfnA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
Hello, this is my first time reporting an issue through mail, so I am
sorry if I missed something.
The file generated with `git bugreport` is attached to this mail, and
I also copy-pasted its contents below just in case.
Tell me if you need more precisions, I feel like this is a bug, but it
might just be an absence of feature.
Thanks in advance,
Robin Vagner.
---
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
> Use the command `git log -L:<funcname>:<file>` on a python file, with an existing function name in an existing file.
What did you expect to happen? (Expected behavior)
> The git log function to find the given function name and display its history.
What happened instead? (Actual behavior)
> I got this error : `fatal: -L parameter 'get_comment_from_args' starting at line 1: no match`
What's different between what you expected and what actually happened?
> Since git already knows by default to use python for diffs with *.py files, I expected it to find the function.
Anything else you want to add:
> It works properly if I add a .gitattributes file with the following line : `*.py diff=python`, which is weird because I thought this was already the default values for git (at least a `git diff` shows me the function name properly in the diff blobs.
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.35.1.windows.2
cpu: x86_64
built from commit: 5437f0fd368c7faf1a0b5e1fef048232c1f2a3e6
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 19043
compiler info: gnuc: 11.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
[-- Attachment #2: git-bugreport-2023-03-22-1040.txt --]
[-- Type: text/plain, Size: 1516 bytes --]
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
> Use the command `git log -L:<funcname>:<file>` on a python file, with an existing function name in an existing file.
What did you expect to happen? (Expected behavior)
> The git log function to find the given function name and display its history.
What happened instead? (Actual behavior)
> I got this error : `fatal: -L parameter 'get_comment_from_args' starting at line 1: no match`
What's different between what you expected and what actually happened?
> Since git already knows by default to use python for diffs with *.py files, I expected it to find the function.
Anything else you want to add:
> It works properly if I add a .gitattributes file with the following line : `*.py diff=python`, which is weird because I thought this was already the default values for git (at least a `git diff` shows me the function name properly in the diff blobs.
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.35.1.windows.2
cpu: x86_64
built from commit: 5437f0fd368c7faf1a0b5e1fef048232c1f2a3e6
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 19043
compiler info: gnuc: 11.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
reply other threads:[~2023-03-22 10:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAHadCYLUTxzBYk+jw1Eg9FrP2Abn_qTyAvGBPeoi=Cwum2FfnA@mail.gmail.com' \
--to=robin.vagner@unit-image.fr \
--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;
as well as URLs for NNTP newsgroup(s).