From: Randy Dunlap <rdunlap@infradead.org>
To: Thorsten Blum <thorsten.blum@linux.dev>
Cc: Jonathan Corbet <corbet@lwn.net>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] docs: maintainer: Fix capitalization
Date: Mon, 15 Sep 2025 20:37:40 -0700 [thread overview]
Message-ID: <6a2f324d-5be3-48d4-a787-2c3bc76a56ad@infradead.org> (raw)
In-Reply-To: <DBCAF005-F4C6-44D2-8DB3-71B002501770@linux.dev>
On 9/15/25 1:06 PM, Thorsten Blum wrote:
> On 15. Sep 2025, at 21:43, Randy Dunlap wrote:
>> On 9/15/25 12:35 PM, Thorsten Blum wrote:
>>>
>>> On 15. Sep 2025, at 21:29, Randy Dunlap wrote:
>>>> On 9/15/25 12:22 PM, Thorsten Blum wrote:
>>>>> The sentence starts at the previous line: s/Indicate/indicate/
>>>>
>>>> Are you sure?
>>>> ISTM that the entire line is a "sub-heading".
>>
>> After I sent this I saw that I should have added that it's ambiguous
>> and needs some formatting help, so I'm not surprised to see this:
>>
>>> Hm maybe, but then the layout/rendering on the web is very confusing:
>>>
>>> https://docs.kernel.org/maintainer/maintainer-entry-profile.html#key-cycle-dates
>
> I think the entire line is meant to be a sub-heading. If it were a
> single sentence, it should be either "Deadline ... indicates" or
> "Deadlines ... indicate", but not "Deadline ... indicate".
>
> Maybe the author of 4699c504e603 (cc Dan Williams) can confirm this?
I think all that is needed is a blank line after each of these sub-headings.
That makes the html output readable and more understandable.
Would you submit that patch, Thorsten?
thanks.
--
~Randy
prev parent reply other threads:[~2025-09-16 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 19:22 Thorsten Blum
2025-09-15 19:29 ` Randy Dunlap
2025-09-15 19:35 ` Thorsten Blum
2025-09-15 19:43 ` Randy Dunlap
2025-09-15 20:06 ` Thorsten Blum
2025-09-16 3:37 ` Randy Dunlap [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=6a2f324d-5be3-48d4-a787-2c3bc76a56ad@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thorsten.blum@linux.dev \
--cc=workflows@vger.kernel.org \
/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