{"thread":{"id":"59554","subject":"Can see log for a renamed file","startedAt":"2023-04-05T23:21:36Z","lastAt":"2023-04-06T04:00:01Z","messageCount":2,"participants":["Eugen Konkov","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"474896","messageId":"909508822.20230405191602@yandex.ru","threadId":"59554","inReplyTo":null,"subject":"Can see log for a renamed file","fromName":"Eugen Konkov","fromEmail":"kes-kes@yandex.ru","sentAt":"2023-04-05T23:16:02Z","receivedAt":"2023-04-05T23:21:36Z","isPatch":false,"sender":{"key":"kes-kes@yandex.ru","avatar":null},"body":"Hello, folks.\n\n```\ngit log 9ce3e165f284d55503eff9b627ef3723854c53bb^ -- lib/Invoice/Schema/Result/Company.pm\nfatal: ambiguous argument 'lib/Invoice/Schema/Result/Company.pm': unknown revision or path not in the working tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'\n```\n\nBut if I checkout to the commit before renaming then this command works:\n\ngit log 9ce3e165f284d55503eff9b627ef3723854c53bb^ -- lib/Invoice/Schema/Result/Company.pm\n\nI beleive it would be much handy if git checks the file after analizing of the commit 9ce3e165f284d55503eff9b627ef3723854c53bb^\n\nThanks\n-- \nBest regards,\nEugen Konkov\n\n"},{"id":"474906","messageId":"20230406035953.GB2092667@coredump.intra.peff.net","threadId":"59554","inReplyTo":"909508822.20230405191602@yandex.ru","subject":"Re: Can see log for a renamed file","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2023-04-06T03:59:53Z","receivedAt":"2023-04-06T04:00:01Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Apr 05, 2023 at 07:16:02PM -0400, Eugen Konkov wrote:\n\n> Hello, folks.\n> \n> ```\n> git log 9ce3e165f284d55503eff9b627ef3723854c53bb^ -- lib/Invoice/Schema/Result/Company.pm\n> fatal: ambiguous argument 'lib/Invoice/Schema/Result/Company.pm': unknown revision or path not in the working tree.\n> Use '--' to separate paths from revisions, like this:\n> 'git <command> [<revision>...] -- [<file>...]'\n> ```\n\nAre you sure you've cut and paste accurately here? You _do_ have a \"--\"\nin the command you showed, so it should not print the \"ambiguous\nargument\" error. It should behave exactly as you're expecting (accepting\nthe path as-is).\n\nIf that is what you typed, then something very funny is going on in your\nGit build, where it is ignoring some arguments. Is \"git\" a wrapper\nscript or something?\n\n-Peff\n"}]}