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

From: Junio C Hamano <[email-masked]>
Date: Thu, 28 Aug 2025 15:44:41 -0700

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

> Toon Claes <[email-masked]> writes:
>
>> Looks good to me. Do you want me to reroll, or will you `--autosquash`
>> yourself? 
>
> I can do the latter, unless there are other reasons that make it
> necessary to update the patches.  We'll see.

Sorry, but it seems that I dropped the ball after this exchange.

The topic still has the fixup! sitting at the top.  If there are no
further changes needed, let me squash it into the base commit and
then mark the topic for 'next'.

 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-262-gbae8ff527a