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
Subject: Re: [PATCH] docs: maintainer: Fix capitalization
Date: Mon, 15 Sep 2025 12:43:06 -0700 [thread overview]
Message-ID: <8a9b2f36-963a-4d10-9aa1-10f8dcb4bc31@infradead.org> (raw)
In-Reply-To: <E32E7460-02E4-4E85-8482-E91D3FD12253@linux.dev>
On 9/15/25 12:35 PM, Thorsten Blum wrote:
> Hi Randy,
>
> 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
>
> How would that be fixed?
I'm not sure. At a minimum, add another colon at the end of the line.
Or both sub-headings (this one and the one before it) might need a "::"
at the end of the line and then a blank line inserted there.
I'd have to play around with it and test some, but for now I have to do
something else...
--
~Randy
next prev parent reply other threads:[~2025-09-15 19:43 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 [this message]
2025-09-15 20:06 ` Thorsten Blum
2025-09-16 3:37 ` Randy Dunlap
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=8a9b2f36-963a-4d10-9aa1-10f8dcb4bc31@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--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