Re: [PATCH v3 0/4] Change git-last-modified(1) default behavior and add documentation

From: Karthik Nayak <karthik.188@gmail.com>
Date: Feb 3, 2026, 09:58 UTC
Message-ID: <CAOLa=ZQEU7kD6DEj446Wj19XUQP_1bOXYK1xsg5rbjnw7W3sDw@mail.gmail.com>
In-Reply-To: <xmqqpl72u7vc.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

Show 13 quoted lines

> Toon Claes <toon@iotcl.com> writes:
>
>> Changes in v3:
>> - Rejoined the two commits about `-z and the two about `--max-depth`
>> - In the end, drop `struct last_modified::recursive`. This ensures
>>   the effect of `--recursive` or `--max-depth` depends on whatever comes
>>   last.
>> - Added a commit to rename `<path>` to `<pathspec>` in the docs.
>> - Link to v2: https://patch.msgid.link/20260116-toon-last-modified-zzzz-v2-0-79e44f2806fe@iotcl.com
>
> This round looked reasonable to me.  Shall we mark it for 'next'?
>
> Thanks.

I also did a round of review and think it is indeed ready for 'next'.

Thanks

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.