From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: PATCH: Clarify maintainers and include linux-security info
Date: Tue, 16 May 2006 17:03:41 +0100 [thread overview]
Message-ID: <1147795421.2151.80.camel@localhost.localdomain> (raw)
Signed-off-by: Alan Cox <alan@redhat.com>
--- linux-2.6.17-rc4/MAINTAINERS~ 2006-05-16 16:38:42.034901424 +0100
+++ linux-2.6.17-rc4/MAINTAINERS 2006-05-16 16:38:42.034901424 +0100
@@ -44,7 +44,11 @@
do changes at work you may find your employer owns the patch
not you.
-7. Happy hacking.
+7. When sending security related changes or reports to a maintainer
+ please Cc: linux-security@kernel.org, especially if the maintainer
+ does not respond.
+
+8. Happy hacking.
-----------------------------------
next reply other threads:[~2006-05-16 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 16:03 Alan Cox [this message]
2006-05-16 15:57 ` PATCH: Clarify maintainers and include linux-security info Andrew Morton
2006-05-16 22:53 ` Alan Cox
2006-05-16 16:03 ` Randy.Dunlap
2006-05-17 17:43 ` PATCH: Clarify maintainers and include security info (Version 2) Alan Cox
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=1147795421.2151.80.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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