From: Paul Moore <paul@paul-moore.com>
To: audit@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update the audit entry
Date: Wed, 15 Nov 2023 23:40:19 -0500 [thread overview]
Message-ID: <CAHC9VhSNVAds99M3ew9wcu6uO1KFnNB1-jT8kvWdcxTq9d02Jg@mail.gmail.com> (raw)
In-Reply-To: <20231115172537.130415-2-paul@paul-moore.com>
On Wed, Nov 15, 2023 at 12:25 PM Paul Moore <paul@paul-moore.com> wrote:
>
> Bring the audit subsystem entry up to date with the following changes:
>
> * 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 audit 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.
>
> * Aside from changes to the audit code itself, we also would like to
> be notified when the audit call sites are changed so we are adding an
> audit_XXX(...) regex to try and catch all of the callers.
>
> Signed-off-by: Paul Moore <paul@paul-moore.com>
> ---
> MAINTAINERS | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
Merged into audit/dev.
--
paul-moore.com
prev parent reply other threads:[~2023-11-16 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 17:25 [PATCH] MAINTAINERS: update the audit entry Paul Moore
2023-11-16 4:40 ` Paul Moore [this message]
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=CAHC9VhSNVAds99M3ew9wcu6uO1KFnNB1-jT8kvWdcxTq9d02Jg@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=audit@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).