Subject: Re: [PATCH v7 0/3] Introduce git-last-modified(1) command

From: Toon Claes <[email-masked]>
Date: Wed, 06 Aug 2025 14:01:04 +0200

Junio C Hamano <[email-masked]> writes:

> This is what I queued on top of your topic to prepare the
> integration today.
>
> --- >8 ---
> From: Junio C Hamano <[email-masked]>
> Date: Tue, 5 Aug 2025 14:37:25 -0700
> Subject: [PATCH] fixup! last-modified: new subcommand to show when files were last modified
>
> ---
>  Documentation/git-last-modified.adoc | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/git-last-modified.adoc b/Documentation/git-last-modified.adoc
> index 35bd4a1dd0..602843e095 100644
> --- a/Documentation/git-last-modified.adoc
> +++ b/Documentation/git-last-modified.adoc
> @@ -22,24 +22,24 @@ THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.
>  OPTIONS
>  -------
>  
> --r::
> ---recursive::
> +`-r`::
> +`--recursive`::
>  	Instead of showing tree entries, step into subtrees and show all entries
>  	inside them recursively.
>  
> --t::
> ---show-trees::
> +`-t`::
> +`--show-trees`::
>  	Show tree entries even when recursing into them. It has no effect
>  	without `--recursive`.
>  
> -<revision-range>::
> +`<revision-range>`::
>  	Only traverse commits in the specified revision range. When no
>  	`<revision-range>` is specified, it defaults to `HEAD` (i.e. the whole
>  	history leading to the current commit). For a complete list of ways to
>  	spell `<revision-range>`, see the 'Specifying Ranges' section of
>  	linkgit:gitrevisions[7].
>  
> -[--] <path>...::
> +`[--] <path>...`::
>  	For each _<path>_ given, the commit which last modified it is returned.
>  	Without an optional path parameter, all files and subdirectories
>  	in path traversal the are included in the output.
> -- 
> 2.51.0-rc0-162-g220549999b

Looks good to me. Do you want me to reroll, or will you `--autosquash`
yourself? 

-- 
Cheers,
Toon