From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH] proto-v2 doc: mark-up fix
Date: Tue, 3 May 2022 14:20:11 +0700 [thread overview]
Message-ID: <YnDXqzdiEGNkCrdu@debian.me> (raw)
In-Reply-To: <xmqqczgvsa7k.fsf@gitster.g>
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>
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2022-05-03 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 0:58 [PATCH] proto-v2 doc: mark-up fix Junio C Hamano
2022-05-03 7:20 ` Bagas Sanjaya [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YnDXqzdiEGNkCrdu@debian.me \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).