Commit f5364ecf authored by Paul Moore's avatar Paul Moore

MAINTAINERS: update the SELinux entry

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.

* Update the source tree's git URI to use https.
Signed-off-by: default avatarPaul Moore <paul@paul-moore.com>
parent a67d2a14
...@@ -19520,9 +19520,11 @@ M: Stephen Smalley <stephen.smalley.work@gmail.com> ...@@ -19520,9 +19520,11 @@ M: Stephen Smalley <stephen.smalley.work@gmail.com>
M: Eric Paris <eparis@parisplace.org> M: Eric Paris <eparis@parisplace.org>
L: selinux@vger.kernel.org L: selinux@vger.kernel.org
S: Supported S: Supported
W: https://selinuxproject.org
W: https://github.com/SELinuxProject W: https://github.com/SELinuxProject
T: git git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git 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 https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
F: Documentation/ABI/removed/sysfs-selinux-checkreqprot F: Documentation/ABI/removed/sysfs-selinux-checkreqprot
F: Documentation/ABI/removed/sysfs-selinux-disable F: Documentation/ABI/removed/sysfs-selinux-disable
F: Documentation/admin-guide/LSM/SELinux.rst F: Documentation/admin-guide/LSM/SELinux.rst
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment