From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Patrick Steinhardt" <ps@pks.im>, Gusted <gusted@codeberg.org>
Cc: git@vger.kernel.org, "Toon Claes" <toon@iotcl.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: git-last-modified on bare repository
Date: Tue, 06 Jan 2026 11:54:39 +0100 [thread overview]
Message-ID: <39eb6099-49ec-4ebd-8347-e2f2e18f3e8a@app.fastmail.com> (raw)
In-Reply-To: <aVzcyYjR8l-xXD4L@pks.im>
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).
next prev parent reply other threads:[~2026-01-06 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 13:35 git-last-modified on bare repository Gusted
2026-01-05 15:03 ` Patrick Steinhardt
2026-01-05 15:06 ` Gusted
2026-01-05 15:17 ` Patrick Steinhardt
2026-01-06 9:42 ` Gusted
2026-01-06 9:58 ` Patrick Steinhardt
2026-01-06 10:54 ` Kristoffer Haugsbakk [this message]
2026-01-07 0:01 ` Junio C Hamano
2026-01-07 17:12 ` D. Ben Knoble
2026-01-05 15:17 ` Kristoffer Haugsbakk
2026-01-12 15:15 ` Toon Claes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39eb6099-49ec-4ebd-8347-e2f2e18f3e8a@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gusted@codeberg.org \
--cc=ps@pks.im \
--cc=toon@iotcl.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox