[PATCH 0/3] Expand and enhance git-last-modified(1) documentation · Toon Claes <hidden> · 2025-11-26
[PATCH 1/3] last-modified: handle and document NUL termination · Toon Claes <hidden> · 2025-11-26
Re: [PATCH 1/3] last-modified: handle and document NUL termination · Karthik Nayak <hidden> · 2025-11-26
[PATCH 2/3] last-modified: document option --max-depth · Toon Claes <hidden> · 2025-11-26
Re: [PATCH 2/3] last-modified: document option --max-depth · Karthik Nayak <hidden> · 2025-11-26
Re: [PATCH 2/3] last-modified: document option --max-depth · Toon Claes <hidden> · 2026-01-16
[PATCH 3/3] last-modified: better document how depth in handled · Toon Claes <hidden> · 2025-11-26
Re: [PATCH 3/3] last-modified: better document how depth in handled · Eric Sunshine <hidden> · 2025-11-26
Re: [PATCH 3/3] last-modified: better document how depth in handled · Patrick Steinhardt <hidden> · 2025-12-01
Re: [PATCH 3/3] last-modified: better document how depth in handled · Toon Claes <hidden> · 2025-12-02
Re: [PATCH 3/3] last-modified: better document how depth in handled · Patrick Steinhardt <hidden> · 2025-12-02
[PATCH v2 0/5] Change git-last-modified(1) default behavior and add documentation · Toon Claes <hidden> · 2026-01-16
[PATCH v2 1/5] last-modified: document NUL termination · Toon Claes <hidden> · 2026-01-16
[PATCH v2 2/5] last-modified: add option '-z' to help output · Toon Claes <hidden> · 2026-01-16
[PATCH v2 3/5] last-modified: document option --max-depth · Toon Claes <hidden> · 2026-01-16
[PATCH v2 4/5] last-modified: add option '--max-depth' to help output · Toon Claes <hidden> · 2026-01-16
[PATCH v2 5/5] last-modified: change default max-depth to 0 · Toon Claes <hidden> · 2026-01-16
Re: [PATCH v2 0/5] Change git-last-modified(1) default behavior and add documentation · Kristoffer Haugsbakk <hidden> · 2026-01-16
Re: [PATCH v2 0/5] Change git-last-modified(1) default behavior and add documentation · Toon Claes <hidden> · 2026-01-20
[PATCH v3 0/4] Change git-last-modified(1) default behavior and add documentation · Toon Claes <hidden> · 2026-01-20
[PATCH v3 1/4] last-modified: clarify in the docs the command takes a pathspec · Toon Claes <hidden> · 2026-01-20
[PATCH v3 2/4] last-modified: document option '-z' · Toon Claes <hidden> · 2026-01-20
[PATCH v3 3/4] last-modified: document option '--max-depth' · Toon Claes <hidden> · 2026-01-20
[PATCH v3 4/4] last-modified: change default max-depth to 0 · Toon Claes <hidden> · 2026-01-20
Re: [PATCH v3 4/4] last-modified: change default max-depth to 0 · Kristoffer Haugsbakk <hidden> · 2026-01-25

Re: [PATCH 3/3] last-modified: better document how depth in handled

From: Patrick Steinhardt <hidden>
Date: 2025-12-01 10:32:52

On Wed, Nov 26, 2025 at 07:09:45AM +0100, Toon Claes wrote:

By default git-last-modified(1) only shows information about paths at
the root level. This can be confusing. Clarify the command's behavior in
the documentation.

Hm, that's confusing indeed. Is it possible for git-last-modified(1) to
do the "right thing" automatically? That is, given "sub/file", show when
that specific file has been last modified? Or is there a good
(non-technical) reason it behaves the way it does?

Patrick

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help