Subject: Re: git-last-modified on bare repository

From: Junio C Hamano <[email-masked]>
Date: Wed, 07 Jan 2026 09:01:04 +0900

"Kristoffer Haugsbakk" <[email-masked]> writes:

> On Tue, Jan 6, 2026, at 10:58, Patrick Steinhardt wrote:
>> On Tue, Jan 06, 2026 at 10:42:55AM +0100, Gusted wrote:
>>> On 1/5/26 4:17 PM, Patrick Steinhardt wrote:
>>>>[snip]
>>>
>>> Yup, git from source works! Do you by any chance know if 05491b90ce is going
>>> to be in v2.52.1?
>>
>> No idea, point releases are typically done rather ad-hoc. Let me Cc
>> Junio though so that he's aware that we might want to pick this if we
>> ever release v2.52.1.
>
> `RelNotes` says that this will be merged to `maint` later which points
> at tag v2.52.0 currently.
>
>      * "git last-modified" used to mishandle "--" to mark the beginning of
>        pathspec, which has been corrected.
>        (merge 05491b90ce js/last-modified-with-sparse-checkouts later to maint).

These are really "if we will produce a release out of 'maint', the
topics marked with these can cleanly be merged to be part of it",
and does not answer "if we ever have 2.52.1?" at all, though ;-)

I am on a bereavement leave now, so expect that my response will be
leaky and slow.