From: Weishi Zeng <amwish.zeng@gmail.com>
To: git@vger.kernel.org
Subject: [Bug Report] git log -L:<funcname>:<file>
Date: Wed, 19 May 2021 17:11:48 -0700 [thread overview]
Message-ID: <CAH6yD_bkY+_7XrzHdOqnnE=qvnnvxAWEQPtOyVh=BwvbcheTCA@mail.gmail.com> (raw)
Summary:
git log -L:<funcname>:<file>
would fail if there's any java-style comment that appears before the
<funcname> string in the file.
Details:
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)
git log -L:'myFunction':~/a.java
The file is a java file that contains comment before the function name.
E.g.
/**
* comments will interrupt the regex match
*/
private static void myFunction() {}
What did you expect to happen? (Expected behavior)
As described, it should return me the commit history that touched this function
What happened instead? (Actual behavior)
It returns error:
fatal: -L parameter 'myFunction' starting at line 1: no match
Anything else you want to add:
If the function name string to search for appears before any
java-style comment, it returns a valid response.
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.30.1 (Apple Git-130)
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Darwin 20.4.0 Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47
PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64 x86_64
compiler info: clang: 12.0.5 (clang-1205.0.22.6)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh
[Enabled Hooks]
post-commit
post-rewrite
next reply other threads:[~2021-05-20 0:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 0:11 Weishi Zeng [this message]
2021-05-20 3:18 ` [Bug Report] git log -L:<funcname>:<file> Bagas Sanjaya
2021-05-20 6:45 ` Weishi Zeng
2021-05-20 7:05 ` Atharva Raykar
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='CAH6yD_bkY+_7XrzHdOqnnE=qvnnvxAWEQPtOyVh=BwvbcheTCA@mail.gmail.com' \
--to=amwish.zeng@gmail.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;
as well as URLs for NNTP newsgroup(s).