From: Evan Castillo <eycastio@icloud.com>
To: corbet@lwn.net, sashal@kernel.org
Cc: linux-kernel@vger.kernel.org, Evan Castillo <eycastio@icloud.com>
Subject: [PATCH] README: remove out of place emdashes
Date: Sat, 27 Jun 2026 16:09:38 -0500 [thread overview]
Message-ID: <20260627210938.85899-1-eycastio@icloud.com> (raw)
This removes emdashes in the README. In other places in the README,
colons are used.
Signed-off-by: Evan Castillo <eycastio@icloud.com>
---
README | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/README b/README
index e6549b2a7aac..010c58722422 100644
--- a/README
+++ b/README
@@ -30,15 +30,15 @@ Who Are You?
Find your role below:
-* New Kernel Developer - Getting started with kernel development
-* Academic Researcher - Studying kernel internals and architecture
-* Security Expert - Hardening and vulnerability analysis
-* Backport/Maintenance Engineer - Maintaining stable kernels
-* System Administrator - Configuring and troubleshooting
-* Maintainer - Leading subsystems and reviewing patches
-* Hardware Vendor - Writing drivers for new hardware
-* Distribution Maintainer - Packaging kernels for distros
-* AI Coding Assistant - LLMs and AI-powered development tools
+* New Kernel Developer: Getting started with kernel development
+* Academic Researcher: Studying kernel internals and architecture
+* Security Expert: Hardening and vulnerability analysis
+* Backport/Maintenance Engineer: Maintaining stable kernels
+* System Administrator: Configuring and troubleshooting
+* Maintainer: Leading subsystems and reviewing patches
+* Hardware Vendor: Writing drivers for new hardware
+* Distribution Maintainer: Packaging kernels for distros
+* AI Coding Assistant: LLMs and AI-powered development tools
For Specific Users
--
2.54.0
next reply other threads:[~2026-06-27 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 21:09 Evan Castillo [this message]
2026-07-10 19:48 ` Jonathan Corbet
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=20260627210938.85899-1-eycastio@icloud.com \
--to=eycastio@icloud.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@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