From: Thorsten Blum <thorsten.blum@linux.dev>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Thorsten Blum <thorsten.blum@linux.dev>,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] docs: maintainer: Fix capitalization
Date: Mon, 15 Sep 2025 21:22:35 +0200 [thread overview]
Message-ID: <20250915192235.2414746-2-thorsten.blum@linux.dev> (raw)
The sentence starts at the previous line: s/Indicate/indicate/
Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
---
Documentation/maintainer/maintainer-entry-profile.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/maintainer/maintainer-entry-profile.rst b/Documentation/maintainer/maintainer-entry-profile.rst
index cda5d691e967..f411a0d10fad 100644
--- a/Documentation/maintainer/maintainer-entry-profile.rst
+++ b/Documentation/maintainer/maintainer-entry-profile.rst
@@ -68,7 +68,7 @@ wait for the next -rc. At a minimum:
submissions should appear before -rc5.
- Last -rc to merge features: Deadline for merge decisions
- Indicate to contributors the point at which an as yet un-applied patch
+ indicate to contributors the point at which an as yet un-applied patch
set will need to wait for the NEXT+1 merge window. Of course there is no
obligation to ever accept any given patchset, but if the review has not
concluded by this point the expectation is the contributor should wait and
--
2.51.0
next reply other threads:[~2025-09-15 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 19:22 Thorsten Blum [this message]
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
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=20250915192235.2414746-2-thorsten.blum@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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