From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc: patch-id: fix accidental literal blocks
Date: Sun, 28 Sep 2025 12:37:37 -0700 [thread overview]
Message-ID: <xmqqv7l25pxa.fsf@gitster.g> (raw)
In-Reply-To: <b7ded038-fc91-41cc-b241-1ace6b46069c@app.fastmail.com> (Kristoffer Haugsbakk's message of "Sun, 28 Sep 2025 21:25:26 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> ...
>>> This is kind of subtle since only the last paragraph of each option gets
>>> rendered in an unintended way, namely as literal blocks. This is easier
>>> to see in the HTML output since the man page output just has a slightly
>>> larger indentation on these paragraphs.
>>
>> Hmph, I've always thought that the practice breaks every paragraph
>> except for the first one (which is the same as "only the last",
>> only when you have exactly 2 paragraphs; when you have more than 2,
>> it makes a difference).
>
> I don’t understand why but `doc-diff` agrees that these last ones are
> the only ones affected by this change.
But in this patch, you are not dealing with a section with three or
more paragraphs, are you? I think there is nothing doc-diff can
show you in this particular fix.
For example, the first hunk deals with
--verbatim::
Calculate the patch-id of the input as it is given, do not strip
any whitespace.
This is the default if patchid.verbatim is true.
two paragraphs, "Calculate...", and "This is the default...". It is
correct that the second paragraph needs to be treated, like so:
--verbatim::
Calculate the patch-id of the input as it is given, do not strip
any whitespace.
+
This is the default if patchid.verbatim is true.
and that is what your patch does.
But if you had three or more, e.g.,
--verbatim::
Calculate the patch-id of the input as it is given, do not strip
any whitespace.
This is the default if patchid.verbatim is true.
For fun, we add a third paragraph.
would it render the first two paragraph correctly, and only the "For
fun, ..." paragraph gets shown incorrectly? And would it give us a
good rendition to fix only the last paragraph, like so:
--verbatim::
Calculate the patch-id of the input as it is given, do not strip
any whitespace.
This is the default if patchid.verbatim is true.
+
For fun, we add a third paragraph.
That is what your proposed log message said, and that is what I
wanted to double check, as from memory and experience, I am
reasonably sure that in such a case, I had to correct it more like
--verbatim::
Calculate the patch-id of the input as it is given, do not strip
any whitespace.
+
This is the default if patchid.verbatim is true.
+
For fun, we add a third paragraph.
i.e., the second and subsequent paragraphs needed the "a + on a line
byitself before the paragraph, and paragraph itself dedented"
treatment.
Thanks.
next prev parent reply other threads:[~2025-09-28 19:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 14:03 [PATCH] doc: patch-id: fix accidental literal blocks kristofferhaugsbakk
2025-09-28 15:45 ` Kristoffer Haugsbakk
2025-09-28 16:01 ` Junio C Hamano
2025-09-28 19:25 ` Kristoffer Haugsbakk
2025-09-28 19:37 ` Junio C Hamano [this message]
2025-09-29 20:47 ` [PATCH v2] " kristofferhaugsbakk
2025-09-29 22:18 ` Junio C Hamano
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=xmqqv7l25pxa.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.com \
/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).