From: Kristoffer Haugsbakk <code@khaugsbakk.name>
Date: Mon, 11 May 2026 13:25:57 GMT
Subject: Re: [PATCH v4 5/5] format-rev: introduce builtin for on-demand pretty formatting
Message-ID: <c3da244d-9e01-42dc-a4fe-98b2d1c30570@app.fastmail.com>
In-Reply-To: <V4_format-rev_new_builtin.6af@msgid.xyz>

On Thu, May 7, 2026, at 21:34, kristofferhaugsbakk@fastmail.com wrote:
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> Introduce a new builtin for pretty formatting one revision expression
> per line or commit object names found in running text.
>
>[snip]
>
> diff --git a/Documentation/git-format-rev.adoc
>[snip]
> +OPTIONS
> +-------
> +
> +`--stdin-mode=<mode>`::
> +	How to interpret standard input data:
> ++
> +--
> +`revs`:: Each line or record (see the <<io,INPUT AND OUTPUT FORMATS>>
> +	section) is interpreted as a commit. Any kind of revision
> +	expression can be used (see linkgit:gitrevisions[7]). Annotated
> +	tags are peeled (see linkgit:gitglossary[7]).
> ++
> +The argument `rev` is also accepted.
> +`text`:: Formats all commit object names found in freeform text. These
> +	must the full object names, i.e. abbreviated hexidecimal object
> +	names will not be interpreted.
> ++
> +Anything that is parsed as an object name but that is not found to be a
> +commit object name is left alone (echoed).
> +--

This nested definition list is malformed. I’ll need to fix that.

> +
> +`--format=<pretty>`::
> +	Pretty format string.
>[snip]