From: Paul Moore <paul@paul-moore.com>
To: selinux@vger.kernel.org
Subject: [PATCH] MAINTAINERS: update the SELinux entry
Date: Wed, 15 Nov 2023 12:04:06 -0500 [thread overview]
Message-ID: <20231115170405.113117-2-paul@paul-moore.com> (raw)
Bring the SELinux entry up to date with the following changes:
* Remove the selinuxproject.org link. The wiki located there is in
read-only mode and exists primarily for historical reasons.
* Add our patchwork link. I'm not sure this is of much use for
anyone but the maintainer, but there is a provision for including it
here so we might as well include it.
* Add a bug report URI. I suspect most everyone knows to send mail
to the mailing list if they hit a bug, but let's make it official.
* Add a link to the SELinux tree process/management documentation.
While the doc exists both in the canonical kernel.org location and
the GitHub mirror, provide a link to the mirror as GitHub does a
better job rendering the Markdown.
Signed-off-by: Paul Moore <paul@paul-moore.com>
---
MAINTAINERS | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 97f51d5ec1cf..e5d289eaba83 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19520,8 +19520,10 @@ M: Stephen Smalley <stephen.smalley.work@gmail.com>
M: Eric Paris <eparis@parisplace.org>
L: selinux@vger.kernel.org
S: Supported
-W: https://selinuxproject.org
W: https://github.com/SELinuxProject
+Q: https://patchwork.kernel.org/project/selinux/list
+B: mailto:selinux@vger.kernel.org
+P: https://github.com/SELinuxProject/selinux-kernel/blob/main/README.md
T: git git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
F: Documentation/ABI/removed/sysfs-selinux-checkreqprot
F: Documentation/ABI/removed/sysfs-selinux-disable
--
2.42.1
next reply other threads:[~2023-11-15 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 17:04 Paul Moore [this message]
2023-11-15 17:21 ` [PATCH] MAINTAINERS: update the SELinux entry Paul Moore
2023-11-16 4:45 ` Paul Moore
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=20231115170405.113117-2-paul@paul-moore.com \
--to=paul@paul-moore.com \
--cc=selinux@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).