From: D. Ben Knoble <ben.knoble@gmail.com>
Date: Wed, 07 Jan 2026 17:12:36 GMT
Subject: Re: git-last-modified on bare repository
Message-ID: <CALnO6CDRPdXJ-HR0CK7VRf30NCWamX5yBE18uf+nJaM8FMJCmg@mail.gmail.com>
In-Reply-To: <xmqqbjj6jnpb.fsf@gitster.g>

On Tue, Jan 6, 2026 at 7:01 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> 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 ;-)

Good to know; I'd had questions about that as well.

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

Sorry to hear that. The only thing I know for sure is it gets easier with time.

-- 
D. Ben Knoble