GIT-LAST-MODIFIED(1)
β¨ git-last-modified(1) β¨
okay so bestie, welcome to git-last-modified β it's a manual page, it's a vibe, it's giving "detective but make it git" π
(the official manual name is git-last-modified(1), fyi, in case you were wondering what to call it at parties π)
πΈ NAME πΈ
git-last-modified β EXPERIMENTAL: shows you when files were last modified π΅οΈββοΈβ¨
π¦ SYNOPSIS π¦
git last-modified [--recursive] [--show-trees] [--max-depth=<depth>] [-z]
[<revision-range>] [[--] <pathspec>...]
no cap, that's the whole shape of it π«Ά
π DESCRIPTION π
So what does it do? It shows which commit last modified each of the relevant files and subdirectories π₯ A commit that renames a path also counts, and so does a commit that changes the path's mode β everything's taken into account, we're being thorough π
β οΈ THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE. β οΈ like, genuinely β it's not settled yet, so don't come for me if it shifts on you π
β¨ OPTIONS β¨
-r,--recursiveβ recursively traverse into all the subtrees π³ By default the command only shows tree entries that match the<pathspec>. With this option it descends into subtrees and displays all the entries inside them. It's exactly equivalent to--max-depth=-1β-t,--show-treesβ show tree entries even when it's recursing into them π--max-depth=<depth>β for each pathspec you give on the command line, traverse at most<depth>levels into subtrees. A negative value means no limit π The default is0, which shows all paths matching the pathspec without descending into subtrees β so chill, it's not going digging unless you ask π§-zβ terminate each line with aNULcharacter instead of a newline π«Ά (yes, that's the whole personality of this flag)<revision-range>β only traverse commits in the specified revision range. When no<revision-range>is specified, it defaults toHEAD(i.e. the whole history leading to the current commit) π For the complete list of ways to spell<revision-range>, see the Specifying Ranges section ofgitrevisions(7)π[--] <pathspec>...β show the commit that last modified each path matching<pathspec>. If you don't give a<pathspec>, all files and subdirectories are included π Seegitglossary(7)for the details on pathspec syntax, iykyk π
π OUTPUT π
The output is in this format:
<oid> TAB <path> LF
If a path contains any special characters, the path is C-style quoted π To avoid the quoting, pass option -z to terminate each line with a NUL:
<oid> TAB <path> NUL
there you go, delicious, parsed πΈ
π SEE ALSO π
git-blame(1), git-log(1) π¦
β GIT β
Part of the git(1) suite π
and that's the whole page, bestie β slay, go find out when your files were last touched π β¨
that was git-last-modified(1) from Git 2.56.0, dated 2026-09-27 β mwah, see you in the next manpage ππ«Άπ
π¦ where this page comes from
- arch rolling: git 2.56.0-1 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms