From: Gusted <gusted@codeberg.org>
To: git@vger.kernel.org
Subject: git-last-modified on bare repository
Date: Mon, 5 Jan 2026 14:35:56 +0100 [thread overview]
Message-ID: <09870987-ae2f-44ec-b8a0-1654f598b5fd@codeberg.org> (raw)
Hi,
Now trying to actually make Forgejo use git last-modified after being
pointed to the non-yet-documented options but I quickly noticed that it
looks like it does not work as intended on bare repositories when
looking specifying files.
$ git clone https://codeberg.org/Gusted/math-accuracy
$ cd math-accuracy
$ git last-modified -- LICENSES
768f05837e7db2832425bc3b65d0f524e81b2769 LICENSES
And on a bare repository:
$ git clone --bare https://codeberg.org/Gusted/math-accuracy
$ cd math-accuracy.git
$ git last-modified -- LICENSE
fatal: ambiguous argument 'LICENSE': unknown revision or path not in the
working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Is a worktree required for this to work?
Because it was talking about revision, I quickly checked a refspec as
input and it looks like I found another way to trigger a BUG.
$ git last-modified -- HEAD:LICENSES
BUG: builtin/last-modified.c:456: paths remaining beyond boundary in
last-modified
[1] 202076 IOT instruction (core dumped) git last-modified --
HEAD:LICENSES
On the bare and non-bare repository.
Kind Regards
Gusted
next reply other threads:[~2026-01-05 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 13:35 Gusted [this message]
2026-01-05 15:03 ` git-last-modified on bare repository 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
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=09870987-ae2f-44ec-b8a0-1654f598b5fd@codeberg.org \
--to=gusted@codeberg.org \
--cc=git@vger.kernel.org \
/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