From: Junio C Hamano <gitster@pobox.com>
To: "Jean-Noël AVILA" <jn.avila@free.fr>
Cc: "Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 4/4] doc: convert git-request-pull synopsis and options to new style
Date: Mon, 20 Jul 2026 14:26:00 -0700 [thread overview]
Message-ID: <xmqqy0f5bbfb.fsf@gitster.g> (raw)
In-Reply-To: <23179740.EfDdHjke4D@piment-oiseau> ("Jean-Noël AVILA"'s message of "Mon, 20 Jul 2026 22:39:29 +0200")
Jean-Noël AVILA <jn.avila@free.fr> writes:
> "Widely accepted", I do not know. I would better frame it as "because at least
> four is needed and I'm lazy, then it's four". I'm not expert enough the
> asciidoc specification to have a definitive answer of mine, but the
> asciidoctor specification says exactly four [1]
>
> We could indeed apply the rule of 4 dashes by default.
>
> Note that this only applies because it is a listing block which does not
> accept nesting.
>
> I will reroll.
Thanks. Sounds like a good plan to me.
prev parent reply other threads:[~2026-07-20 21:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 19:54 [PATCH 0/4] A new batch of synopsis conversion Jean-Noël Avila via GitGitGadget
2026-07-19 19:54 ` [PATCH 1/4] doc: convert git-imap-send synopsis and options to new style Jean-Noël Avila via GitGitGadget
2026-07-19 19:54 ` [PATCH 2/4] doc: convert git-format-patch " Jean-Noël Avila via GitGitGadget
2026-07-19 23:40 ` Junio C Hamano
2026-07-20 20:09 ` Jean-Noël AVILA
2026-07-19 19:54 ` [PATCH 3/4] doc: convert git-send-email " Jean-Noël Avila via GitGitGadget
2026-07-19 19:54 ` [PATCH 4/4] doc: convert git-request-pull " Jean-Noël Avila via GitGitGadget
2026-07-19 23:47 ` Junio C Hamano
2026-07-20 20:39 ` Jean-Noël AVILA
2026-07-20 21:26 ` Junio C Hamano [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=xmqqy0f5bbfb.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=jn.avila@free.fr \
/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