{"thread":{"id":"59435","subject":"git log -L:<funcname>:<file> bug report","startedAt":"2023-03-22T10:06:10Z","lastAt":"2023-03-22T10:06:10Z","messageCount":1,"participants":["Robin Vagner"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"473906","messageId":"CAHadCYLUTxzBYk+jw1Eg9FrP2Abn_qTyAvGBPeoi=Cwum2FfnA@mail.gmail.com","threadId":"59435","inReplyTo":null,"subject":"git log -L:<funcname>:<file> bug report","fromName":"Robin Vagner","fromEmail":"robin.vagner@unit-image.fr","sentAt":"2023-03-22T10:05:52Z","receivedAt":"2023-03-22T10:06:10Z","isPatch":false,"sender":{"key":"robin.vagner@unit-image.fr","avatar":null},"body":"Hello, this is my first time reporting an issue through mail, so I am\nsorry if I missed something.\nThe file generated with `git bugreport` is attached to this mail, and\nI also copy-pasted its contents below just in case.\n\nTell me if you need more precisions, I feel like this is a bug, but it\nmight just be an absence of feature.\n\nThanks in advance,\n\nRobin Vagner.\n\n---\n\nThank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\n> Use the command `git log -L:<funcname>:<file>` on a python file, with an existing function name in an existing file.\n\nWhat did you expect to happen? (Expected behavior)\n> The git log function to find the given function name and display its history.\n\nWhat happened instead? (Actual behavior)\n> I got this error : `fatal: -L parameter 'get_comment_from_args' starting at line 1: no match`\n\nWhat's different between what you expected and what actually happened?\n> Since git already knows by default to use python for diffs with *.py files, I expected it to find the function.\n\nAnything else you want to add:\n> 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.\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.35.1.windows.2\ncpu: x86_64\nbuilt from commit: 5437f0fd368c7faf1a0b5e1fef048232c1f2a3e6\nsizeof-long: 4\nsizeof-size_t: 8\nshell-path: /bin/sh\nfeature: fsmonitor--daemon\nuname: Windows 10.0 19043\ncompiler info: gnuc: 11.2\nlibc info: no libc information available\n$SHELL (typically, interactive shell): <unset>\n\n\n[Enabled Hooks]\n\n\nThank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\n> Use the command `git log -L:<funcname>:<file>` on a python file, with an existing function name in an existing file.\n\nWhat did you expect to happen? (Expected behavior)\n> The git log function to find the given function name and display its history.\n\nWhat happened instead? (Actual behavior)\n> I got this error : `fatal: -L parameter 'get_comment_from_args' starting at line 1: no match`\n\nWhat's different between what you expected and what actually happened?\n> Since git already knows by default to use python for diffs with *.py files, I expected it to find the function.\n\nAnything else you want to add:\n> 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.\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.35.1.windows.2\ncpu: x86_64\nbuilt from commit: 5437f0fd368c7faf1a0b5e1fef048232c1f2a3e6\nsizeof-long: 4\nsizeof-size_t: 8\nshell-path: /bin/sh\nfeature: fsmonitor--daemon\nuname: Windows 10.0 19043 \ncompiler info: gnuc: 11.2\nlibc info: no libc information available\n$SHELL (typically, interactive shell): <unset>\n\n\n[Enabled Hooks]\n"}]}