| Message ID | xmqqczgvsa7k.fsf@gitster.g (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | proto-v2 doc: mark-up fix | expand |
On Mon, May 02, 2022 at 05:58:55PM -0700, Junio C Hamano wrote: > 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>
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
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(-)