threads / patch / 57836

patchproto-v2 doc: mark-up fix

Subject: [PATCH] proto-v2 doc: mark-up fix

## tl;dr

2 messages between May 3, 2022 and May 3, 2022. Diffs are folded; open one to read it.

replies: 1people: 2as markdown or json

Junio C Hamano· May 3, 2022, 00:58 UTC · lore

For some reason, the 'object-format' command was surrounded by extra spaces with extra underline to match.

Noticed when "git grep '^object-format'" did not find this line.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/technical/protocol-v2.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Show changes to diff +2 −2

diff --git c/Documentation/technical/protocol-v2.txt w/Documentation/technical/protocol-v2.txt
index 8a877d27e2..c5051e4d29 100644
--- c/Documentation/technical/protocol-v2.txt
+++ w/Documentation/technical/protocol-v2.txt
@@ -514,8 +514,8 @@ a request.
 
 The provided options must not contain a NUL or LF character.
 
- object-format
-~~~~~~~~~~~~~~~
+object-format
+~~~~~~~~~~~~~
 
 The server can advertise the `object-format` capability with a value `X` (in the
 form `object-format=X`) to notify the client that the server is able to deal

Bagas Sanjaya· May 3, 2022, 07:20 UTC · re: Junio C Hamano · lore

Re: [PATCH] proto-v2 doc: mark-up fix

On Mon, May 02, 2022 at 05:58:55PM -0700, Junio C Hamano wrote:

Show 9 quoted lines

>  The provided options must not contain a NUL or LF character.
>  
> - object-format
> -~~~~~~~~~~~~~~~
> +object-format
> +~~~~~~~~~~~~~
>  
>  The server can advertise the `object-format` capability with a value `X` (in the
>  form `object-format=X`) to notify the client that the server is able to deal

LGTM.

The mistake fixed by this patch doesn't affect the asciidoc output (only tested with html), since the subheading is correctly rendered.

Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>

-- 
An old man doll... just what I always wanted! - Clara