{"thread":{"id":"64724","subject":"git-last-modified on bare repository","startedAt":"2026-01-05T13:35:58Z","lastAt":"2026-01-12T15:16:06Z","messageCount":11,"participants":["Gusted","Patrick Steinhardt","Kristoffer Haugsbakk","Junio C Hamano","D. Ben Knoble","Toon Claes"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"533043","messageId":"09870987-ae2f-44ec-b8a0-1654f598b5fd@codeberg.org","threadId":"64724","inReplyTo":null,"subject":"git-last-modified on bare repository","fromName":"Gusted","fromEmail":"gusted@codeberg.org","sentAt":"2026-01-05T13:35:56Z","receivedAt":"2026-01-05T13:35:58Z","isPatch":false,"sender":{"key":"gusted@codeberg.org","avatar":null},"body":"Hi,\n\nNow trying to actually make Forgejo use git last-modified after being \npointed to the non-yet-documented options but I quickly noticed that it \nlooks like it does not work as intended on bare repositories when \nlooking specifying files.\n\n$ git clone https://codeberg.org/Gusted/math-accuracy\n$ cd math-accuracy\n$ git last-modified -- LICENSES\n768f05837e7db2832425bc3b65d0f524e81b2769        LICENSES\n\nAnd on a bare repository:\n\n$ git clone --bare https://codeberg.org/Gusted/math-accuracy\n$ cd math-accuracy.git\n$ git last-modified -- LICENSE\nfatal: ambiguous argument 'LICENSE': unknown revision or path not in the \nworking tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'\n\nIs a worktree required for this to work?\n\nBecause it was talking about revision, I quickly checked a refspec as \ninput and it looks like I found another way to trigger a BUG.\n\n$ git last-modified -- HEAD:LICENSES\nBUG: builtin/last-modified.c:456: paths remaining beyond boundary in \nlast-modified\n[1]    202076 IOT instruction (core dumped)  git last-modified -- \nHEAD:LICENSES\n\nOn the bare and non-bare repository.\n\nKind Regards\nGusted\n"},{"id":"533056","messageId":"aVvSwkK7RdpFDaVv@pks.im","threadId":"64724","inReplyTo":"09870987-ae2f-44ec-b8a0-1654f598b5fd@codeberg.org","subject":"Re: git-last-modified on bare repository","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-01-05T15:03:30Z","receivedAt":"2026-01-05T15:03:38Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Mon, Jan 05, 2026 at 02:35:56PM +0100, Gusted wrote:\n> Hi,\n> \n> Now trying to actually make Forgejo use git last-modified after being\n> pointed to the non-yet-documented options but I quickly noticed that it\n> looks like it does not work as intended on bare repositories when looking\n> specifying files.\n> \n> $ git clone https://codeberg.org/Gusted/math-accuracy\n> $ cd math-accuracy\n> $ git last-modified -- LICENSES\n> 768f05837e7db2832425bc3b65d0f524e81b2769        LICENSES\n> \n> And on a bare repository:\n> \n> $ git clone --bare https://codeberg.org/Gusted/math-accuracy\n> $ cd math-accuracy.git\n> $ git last-modified -- LICENSE\n> fatal: ambiguous argument 'LICENSE': unknown revision or path not in the\n> working tree.\n> Use '--' to separate paths from revisions, like this:\n> 'git <command> [<revision>...] -- [<file>...]'\n> \n> Is a worktree required for this to work?\n\nA worktree is not required for this to work. The problem is that you've\ngot a typo in there: you say \"LICENSE\", but the actual file is called\n\"LICENSES\". If you spell it correctly it should work alright.\n\n> Because it was talking about revision, I quickly checked a refspec as input\n> and it looks like I found another way to trigger a BUG.\n> \n> $ git last-modified -- HEAD:LICENSES\n> BUG: builtin/last-modified.c:456: paths remaining beyond boundary in\n> last-modified\n> [1]    202076 IOT instruction (core dumped)  git last-modified --\n> HEAD:LICENSES\n> \n> On the bare and non-bare repository.\n\nThis looks like a bug to me indeed. Cc'ing Toon.\n\nThanks!\n\nPatrick\n"},{"id":"533057","messageId":"8e6dd4d7-6e0a-477a-b10c-8571d6b7da4c@codeberg.org","threadId":"64724","inReplyTo":"aVvSwkK7RdpFDaVv@pks.im","subject":"Re: git-last-modified on bare repository","fromName":"Gusted","fromEmail":"gusted@codeberg.org","sentAt":"2026-01-05T15:06:39Z","receivedAt":"2026-01-05T15:06:45Z","isPatch":false,"sender":{"key":"gusted@codeberg.org","avatar":null},"body":"On 1/5/26 4:03 PM, Patrick Steinhardt wrote:\n> On Mon, Jan 05, 2026 at 02:35:56PM +0100, Gusted wrote:\n>> Hi,\n>>\n>> Now trying to actually make Forgejo use git last-modified after being\n>> pointed to the non-yet-documented options but I quickly noticed that it\n>> looks like it does not work as intended on bare repositories when looking\n>> specifying files.\n>>\n>> $ git clone https://codeberg.org/Gusted/math-accuracy\n>> $ cd math-accuracy\n>> $ git last-modified -- LICENSES\n>> 768f05837e7db2832425bc3b65d0f524e81b2769        LICENSES\n>>\n>> And on a bare repository:\n>>\n>> $ git clone --bare https://codeberg.org/Gusted/math-accuracy\n>> $ cd math-accuracy.git\n>> $ git last-modified -- LICENSE\n>> fatal: ambiguous argument 'LICENSE': unknown revision or path not in the\n>> working tree.\n>> Use '--' to separate paths from revisions, like this:\n>> 'git <command> [<revision>...] -- [<file>...]'\n>>\n>> Is a worktree required for this to work?\n> \n> A worktree is not required for this to work. The problem is that you've\n> got a typo in there: you say \"LICENSE\", but the actual file is called\n> \"LICENSES\". If you spell it correctly it should work alright.\n> \n\nAh, sorry the typo is on me from copying the wrong command from the \nshell history. It produces the same output with using LICENSES as path.\n\n$ git last-modified -- LICENSES\nfatal: ambiguous argument 'LICENSES': unknown revision or path not in \nthe working tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'\n\n>> Because it was talking about revision, I quickly checked a refspec as input\n>> and it looks like I found another way to trigger a BUG.\n>>\n>> $ git last-modified -- HEAD:LICENSES\n>> BUG: builtin/last-modified.c:456: paths remaining beyond boundary in\n>> last-modified\n>> [1]    202076 IOT instruction (core dumped)  git last-modified --\n>> HEAD:LICENSES\n>>\n>> On the bare and non-bare repository.\n> \n> This looks like a bug to me indeed. Cc'ing Toon.\n> \n> Thanks!\n> \n> Patrick\n\nKind Regards\nGusted\n"},{"id":"533059","messageId":"f9449d2c-cbfd-46b0-a961-5c668b895503@app.fastmail.com","threadId":"64724","inReplyTo":"aVvSwkK7RdpFDaVv@pks.im","subject":"Re: git-last-modified on bare repository","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2026-01-05T15:17:09Z","receivedAt":"2026-01-05T15:17:31Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Mon, Jan 5, 2026, at 16:03, Patrick Steinhardt wrote:\n> On Mon, Jan 05, 2026 at 02:35:56PM +0100, Gusted wrote:\n>> Hi,\n>>\n>> Now trying to actually make Forgejo use git last-modified after being\n>> pointed to the non-yet-documented options but I quickly noticed that it\n>> looks like it does not work as intended on bare repositories when looking\n>> specifying files.\n>>\n>> $ git clone https://codeberg.org/Gusted/math-accuracy\n>> $ cd math-accuracy\n>> $ git last-modified -- LICENSES\n>> 768f05837e7db2832425bc3b65d0f524e81b2769        LICENSES\n>>\n>> And on a bare repository:\n>>\n>> $ git clone --bare https://codeberg.org/Gusted/math-accuracy\n>> $ cd math-accuracy.git\n>> $ git last-modified -- LICENSE\n>> fatal: ambiguous argument 'LICENSE': unknown revision or path not in the\n>> working tree.\n>> Use '--' to separate paths from revisions, like this:\n>> 'git <command> [<revision>...] -- [<file>...]'\n>>\n>> Is a worktree required for this to work?\n>\n> A worktree is not required for this to work. The problem is that you've\n> got a typo in there: you say \"LICENSE\", but the actual file is called\n> \"LICENSES\". If you spell it correctly it should work alright.\n\nThe error message is more generic than it needs to be though. It has\nseen a `--` but it falls back to “revision or path”. A more pointed\nerror error message “unknown path” would make it harder to make the\nmistake of dismissing the error as a bogus one.\n\nOf course, separate issue and all.\n"},{"id":"533060","messageId":"aVvWDDtBeJMIF3F0@pks.im","threadId":"64724","inReplyTo":"8e6dd4d7-6e0a-477a-b10c-8571d6b7da4c@codeberg.org","subject":"Re: git-last-modified on bare repository","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-01-05T15:17:32Z","receivedAt":"2026-01-05T15:17:37Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Mon, Jan 05, 2026 at 04:06:39PM +0100, Gusted wrote:\n> On 1/5/26 4:03 PM, Patrick Steinhardt wrote:\n> > On Mon, Jan 05, 2026 at 02:35:56PM +0100, Gusted wrote:\n> > > Hi,\n> > > \n> > > Now trying to actually make Forgejo use git last-modified after being\n> > > pointed to the non-yet-documented options but I quickly noticed that it\n> > > looks like it does not work as intended on bare repositories when looking\n> > > specifying files.\n> > > \n> > > $ git clone https://codeberg.org/Gusted/math-accuracy\n> > > $ cd math-accuracy\n> > > $ git last-modified -- LICENSES\n> > > 768f05837e7db2832425bc3b65d0f524e81b2769        LICENSES\n> > > \n> > > And on a bare repository:\n> > > \n> > > $ git clone --bare https://codeberg.org/Gusted/math-accuracy\n> > > $ cd math-accuracy.git\n> > > $ git last-modified -- LICENSE\n> > > fatal: ambiguous argument 'LICENSE': unknown revision or path not in the\n> > > working tree.\n> > > Use '--' to separate paths from revisions, like this:\n> > > 'git <command> [<revision>...] -- [<file>...]'\n> > > \n> > > Is a worktree required for this to work?\n> > \n> > A worktree is not required for this to work. The problem is that you've\n> > got a typo in there: you say \"LICENSE\", but the actual file is called\n> > \"LICENSES\". If you spell it correctly it should work alright.\n> > \n> \n> Ah, sorry the typo is on me from copying the wrong command from the shell\n> history. It produces the same output with using LICENSES as path.\n> \n> $ git last-modified -- LICENSES\n> fatal: ambiguous argument 'LICENSES': unknown revision or path not in the\n> working tree.\n> Use '--' to separate paths from revisions, like this:\n> 'git <command> [<revision>...] -- [<file>...]'\n\nHm, interesting, this works for me in a bare repository. Has this\nalready been fixed...? Indeed, bisecting this points to 05491b90ce\n(last-modified: support sparse checkouts, 2025-11-29). So you should\nprobably try with Git's \"master\" branch.\n\nPatrick\n"},{"id":"533117","messageId":"eecb1c9a-4dc9-4666-b2af-1e3478109db3@codeberg.org","threadId":"64724","inReplyTo":"aVvWDDtBeJMIF3F0@pks.im","subject":"Re: git-last-modified on bare repository","fromName":"Gusted","fromEmail":"gusted@codeberg.org","sentAt":"2026-01-06T09:42:55Z","receivedAt":"2026-01-06T09:45:16Z","isPatch":false,"sender":{"key":"gusted@codeberg.org","avatar":null},"body":"On 1/5/26 4:17 PM, Patrick Steinhardt wrote:\n> On Mon, Jan 05, 2026 at 04:06:39PM +0100, Gusted wrote:\n>> On 1/5/26 4:03 PM, Patrick Steinhardt wrote:\n>>> On Mon, Jan 05, 2026 at 02:35:56PM +0100, Gusted wrote:\n>>>> Hi,\n>>>>\n>>>> Now trying to actually make Forgejo use git last-modified after being\n>>>> pointed to the non-yet-documented options but I quickly noticed that it\n>>>> looks like it does not work as intended on bare repositories when looking\n>>>> specifying files.\n>>>>\n>>>> $ git clone https://codeberg.org/Gusted/math-accuracy\n>>>> $ cd math-accuracy\n>>>> $ git last-modified -- LICENSES\n>>>> 768f05837e7db2832425bc3b65d0f524e81b2769        LICENSES\n>>>>\n>>>> And on a bare repository:\n>>>>\n>>>> $ git clone --bare https://codeberg.org/Gusted/math-accuracy\n>>>> $ cd math-accuracy.git\n>>>> $ git last-modified -- LICENSE\n>>>> fatal: ambiguous argument 'LICENSE': unknown revision or path not in the\n>>>> working tree.\n>>>> Use '--' to separate paths from revisions, like this:\n>>>> 'git <command> [<revision>...] -- [<file>...]'\n>>>>\n>>>> Is a worktree required for this to work?\n>>>\n>>> A worktree is not required for this to work. The problem is that you've\n>>> got a typo in there: you say \"LICENSE\", but the actual file is called\n>>> \"LICENSES\". If you spell it correctly it should work alright.\n>>>\n>>\n>> Ah, sorry the typo is on me from copying the wrong command from the shell\n>> history. It produces the same output with using LICENSES as path.\n>>\n>> $ git last-modified -- LICENSES\n>> fatal: ambiguous argument 'LICENSES': unknown revision or path not in the\n>> working tree.\n>> Use '--' to separate paths from revisions, like this:\n>> 'git <command> [<revision>...] -- [<file>...]'\n> \n> Hm, interesting, this works for me in a bare repository. Has this\n> already been fixed...? Indeed, bisecting this points to 05491b90ce\n> (last-modified: support sparse checkouts, 2025-11-29). So you should\n> probably try with Git's \"master\" branch.\n> \n> Patrick\n\nYup, git from source works! Do you by any chance know if 05491b90ce is \ngoing to be in v2.52.1?\n\nKind Regards\nGusted\n"},{"id":"533118","messageId":"aVzcyYjR8l-xXD4L@pks.im","threadId":"64724","inReplyTo":"eecb1c9a-4dc9-4666-b2af-1e3478109db3@codeberg.org","subject":"Re: git-last-modified on bare repository","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-01-06T09:58:33Z","receivedAt":"2026-01-06T09:58:40Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Tue, Jan 06, 2026 at 10:42:55AM +0100, Gusted wrote:\n> On 1/5/26 4:17 PM, Patrick Steinhardt wrote:\n> > On Mon, Jan 05, 2026 at 04:06:39PM +0100, Gusted wrote:\n> > > On 1/5/26 4:03 PM, Patrick Steinhardt wrote:\n> > > > On Mon, Jan 05, 2026 at 02:35:56PM +0100, Gusted wrote:\n> > > > > Hi,\n> > > > > \n> > > > > Now trying to actually make Forgejo use git last-modified after being\n> > > > > pointed to the non-yet-documented options but I quickly noticed that it\n> > > > > looks like it does not work as intended on bare repositories when looking\n> > > > > specifying files.\n> > > > > \n> > > > > $ git clone https://codeberg.org/Gusted/math-accuracy\n> > > > > $ cd math-accuracy\n> > > > > $ git last-modified -- LICENSES\n> > > > > 768f05837e7db2832425bc3b65d0f524e81b2769        LICENSES\n> > > > > \n> > > > > And on a bare repository:\n> > > > > \n> > > > > $ git clone --bare https://codeberg.org/Gusted/math-accuracy\n> > > > > $ cd math-accuracy.git\n> > > > > $ git last-modified -- LICENSE\n> > > > > fatal: ambiguous argument 'LICENSE': unknown revision or path not in the\n> > > > > working tree.\n> > > > > Use '--' to separate paths from revisions, like this:\n> > > > > 'git <command> [<revision>...] -- [<file>...]'\n> > > > > \n> > > > > Is a worktree required for this to work?\n> > > > \n> > > > A worktree is not required for this to work. The problem is that you've\n> > > > got a typo in there: you say \"LICENSE\", but the actual file is called\n> > > > \"LICENSES\". If you spell it correctly it should work alright.\n> > > > \n> > > \n> > > Ah, sorry the typo is on me from copying the wrong command from the shell\n> > > history. It produces the same output with using LICENSES as path.\n> > > \n> > > $ git last-modified -- LICENSES\n> > > fatal: ambiguous argument 'LICENSES': unknown revision or path not in the\n> > > working tree.\n> > > Use '--' to separate paths from revisions, like this:\n> > > 'git <command> [<revision>...] -- [<file>...]'\n> > \n> > Hm, interesting, this works for me in a bare repository. Has this\n> > already been fixed...? Indeed, bisecting this points to 05491b90ce\n> > (last-modified: support sparse checkouts, 2025-11-29). So you should\n> > probably try with Git's \"master\" branch.\n> > \n> > Patrick\n> \n> Yup, git from source works! Do you by any chance know if 05491b90ce is going\n> to be in v2.52.1?\n\nNo idea, point releases are typically done rather ad-hoc. Let me Cc\nJunio though so that he's aware that we might want to pick this if we\never release v2.52.1.\n\nPatrick\n"},{"id":"533126","messageId":"39eb6099-49ec-4ebd-8347-e2f2e18f3e8a@app.fastmail.com","threadId":"64724","inReplyTo":"aVzcyYjR8l-xXD4L@pks.im","subject":"Re: git-last-modified on bare repository","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2026-01-06T10:54:39Z","receivedAt":"2026-01-06T10:55:34Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Tue, Jan 6, 2026, at 10:58, Patrick Steinhardt wrote:\n> On Tue, Jan 06, 2026 at 10:42:55AM +0100, Gusted wrote:\n>> On 1/5/26 4:17 PM, Patrick Steinhardt wrote:\n>>>[snip]\n>>\n>> Yup, git from source works! Do you by any chance know if 05491b90ce is going\n>> to be in v2.52.1?\n>\n> No idea, point releases are typically done rather ad-hoc. Let me Cc\n> Junio though so that he's aware that we might want to pick this if we\n> ever release v2.52.1.\n\n`RelNotes` says that this will be merged to `maint` later which points\nat tag v2.52.0 currently.\n\n     * \"git last-modified\" used to mishandle \"--\" to mark the beginning of\n       pathspec, which has been corrected.\n       (merge 05491b90ce js/last-modified-with-sparse-checkouts later to maint).\n"},{"id":"533171","messageId":"xmqqbjj6jnpb.fsf@gitster.g","threadId":"64724","inReplyTo":"39eb6099-49ec-4ebd-8347-e2f2e18f3e8a@app.fastmail.com","subject":"Re: git-last-modified on bare repository","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-01-07T00:01:04Z","receivedAt":"2026-01-07T00:01:07Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Kristoffer Haugsbakk\" <kristofferhaugsbakk@fastmail.com> writes:\n\n> On Tue, Jan 6, 2026, at 10:58, Patrick Steinhardt wrote:\n>> On Tue, Jan 06, 2026 at 10:42:55AM +0100, Gusted wrote:\n>>> On 1/5/26 4:17 PM, Patrick Steinhardt wrote:\n>>>>[snip]\n>>>\n>>> Yup, git from source works! Do you by any chance know if 05491b90ce is going\n>>> to be in v2.52.1?\n>>\n>> No idea, point releases are typically done rather ad-hoc. Let me Cc\n>> Junio though so that he's aware that we might want to pick this if we\n>> ever release v2.52.1.\n>\n> `RelNotes` says that this will be merged to `maint` later which points\n> at tag v2.52.0 currently.\n>\n>      * \"git last-modified\" used to mishandle \"--\" to mark the beginning of\n>        pathspec, which has been corrected.\n>        (merge 05491b90ce js/last-modified-with-sparse-checkouts later to maint).\n\nThese are really \"if we will produce a release out of 'maint', the\ntopics marked with these can cleanly be merged to be part of it\",\nand does not answer \"if we ever have 2.52.1?\" at all, though ;-)\n\nI am on a bereavement leave now, so expect that my response will be\nleaky and slow.\n\n"},{"id":"533233","messageId":"CALnO6CDRPdXJ-HR0CK7VRf30NCWamX5yBE18uf+nJaM8FMJCmg@mail.gmail.com","threadId":"64724","inReplyTo":"xmqqbjj6jnpb.fsf@gitster.g","subject":"Re: git-last-modified on bare repository","fromName":"D. Ben Knoble","fromEmail":"ben.knoble@gmail.com","sentAt":"2026-01-07T17:12:36Z","receivedAt":"2026-01-07T17:12:48Z","isPatch":false,"sender":{"key":"ben.knoble@gmail.com","avatar":"https://avatars.githubusercontent.com/u/22802209?v=4"},"body":"On Tue, Jan 6, 2026 at 7:01 PM Junio C Hamano <gitster@pobox.com> wrote:\n>\n> \"Kristoffer Haugsbakk\" <kristofferhaugsbakk@fastmail.com> writes:\n>\n> > On Tue, Jan 6, 2026, at 10:58, Patrick Steinhardt wrote:\n> >> On Tue, Jan 06, 2026 at 10:42:55AM +0100, Gusted wrote:\n> >>> On 1/5/26 4:17 PM, Patrick Steinhardt wrote:\n> >>>>[snip]\n> >>>\n> >>> Yup, git from source works! Do you by any chance know if 05491b90ce is going\n> >>> to be in v2.52.1?\n> >>\n> >> No idea, point releases are typically done rather ad-hoc. Let me Cc\n> >> Junio though so that he's aware that we might want to pick this if we\n> >> ever release v2.52.1.\n> >\n> > `RelNotes` says that this will be merged to `maint` later which points\n> > at tag v2.52.0 currently.\n> >\n> >      * \"git last-modified\" used to mishandle \"--\" to mark the beginning of\n> >        pathspec, which has been corrected.\n> >        (merge 05491b90ce js/last-modified-with-sparse-checkouts later to maint).\n>\n> These are really \"if we will produce a release out of 'maint', the\n> topics marked with these can cleanly be merged to be part of it\",\n> and does not answer \"if we ever have 2.52.1?\" at all, though ;-)\n\nGood to know; I'd had questions about that as well.\n\n> I am on a bereavement leave now, so expect that my response will be\n> leaky and slow.\n\nSorry to hear that. The only thing I know for sure is it gets easier with time.\n\n-- \nD. Ben Knoble\n"},{"id":"533644","messageId":"87v7h6kgkc.fsf@iotcl.com","threadId":"64724","inReplyTo":"aVvSwkK7RdpFDaVv@pks.im","subject":"Re: git-last-modified on bare repository","fromName":"Toon Claes","fromEmail":"toon@iotcl.com","sentAt":"2026-01-12T15:15:47Z","receivedAt":"2026-01-12T15:16:06Z","isPatch":false,"sender":{"key":"toon@iotcl.com","avatar":"https://avatars.githubusercontent.com/u/121621?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n> On Mon, Jan 05, 2026 at 02:35:56PM +0100, Gusted wrote:\n>> Because it was talking about revision, I quickly checked a refspec as input\n>> and it looks like I found another way to trigger a BUG.\n>> \n>> $ git last-modified -- HEAD:LICENSES\n>> BUG: builtin/last-modified.c:456: paths remaining beyond boundary in\n>> last-modified\n>> [1]    202076 IOT instruction (core dumped)  git last-modified --\n>> HEAD:LICENSES\n>> \n>> On the bare and non-bare repository.\n>\n> This looks like a bug to me indeed. Cc'ing Toon.\n\nOkay, there are various things going on.\n\nFirst. If you do:\n\n    $ git last-modified -- HEAD:LICENSES\n\nOn Git 2.52.0, then you're getting the BUG. On 'master' you'll get\nsimply no output.\n\nBut if you do:\n\n    $ git last-modified HEAD:LICENSES\n\nThen you actually trigger the same bug as you've reported before.\n\"HEAD:LICENSES\" resolves to a tree oid. So that command is basically the\nsame as:\n\n    $ git last-modified b79c618f6a11fc6f550dc98ef3227ef77b3132aa\n\nIn both situation you get a BUG. And I'm still working on a fix.\n\n-- \nCheers,\nToon\n"}]}