From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: PATCH: Clarify maintainers and include security info (Version 2)
Date: Wed, 17 May 2006 18:43:07 +0100 [thread overview]
Message-ID: <1147887787.10470.58.camel@localhost.localdomain> (raw)
In-Reply-To: <20060516090315.421e5166.rdunlap@xenotime.net>
This version has the advanced new feature of including the correct email
address (duh sorry), and also another hint about the Signed-off-by:
bits. It goes on top of the original patch. Below this is a second diff
if the first wrong change was not applied.
Signed-off-by: Alan Cox <alan@redhat.com) (or is that Screwed-up-by: ..)
--- linux-2.6.17-rc4/MAINTAINERS~ 2006-05-17 13:06:37.922464048 +0100
+++ linux-2.6.17-rc4/MAINTAINERS 2006-05-17 13:06:37.923463896 +0100
@@ -40,12 +40,17 @@
PLEASE document known bugs. If it doesn't work for everything
or does something very odd once a month document it.
+ PLEASE remember that submissions must be made under the terms
+ of the OSDL certificate of contribution
+ (http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_dco.html)
+ and should include a Signed-off-by: line.
+
6. Make sure you have the right to send any changes you make. If you
do changes at work you may find your employer owns the patch
not you.
7. When sending security related changes or reports to a maintainer
- please Cc: linux-security@kernel.org, especially if the maintainer
+ please Cc: security@kernel.org, especially if the maintainer
does not respond.
8. Happy hacking.
or alternatively:
--- linux.vanilla-2.6.17-rc4/MAINTAINERS 2006-05-15 15:46:01.000000000 +0100
+++ linux-2.6.17-rc4/MAINTAINERS 2006-05-17 13:06:37.923463896 +0100
@@ -40,11 +40,20 @@
PLEASE document known bugs. If it doesn't work for everything
or does something very odd once a month document it.
+ PLEASE remember that submissions must be made under the terms
+ of the OSDL certificate of contribution
+ (http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_dco.html)
+ and should include a Signed-off-by: line.
+
6. Make sure you have the right to send any changes you make. If you
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: security@kernel.org, especially if the maintainer
+ does not respond.
+
+8. Happy hacking.
-----------------------------------
prev parent reply other threads:[~2006-05-17 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 16:03 PATCH: Clarify maintainers and include linux-security info Alan Cox
2006-05-16 15:57 ` Andrew Morton
2006-05-16 22:53 ` Alan Cox
2006-05-16 16:03 ` Randy.Dunlap
2006-05-17 17:43 ` Alan Cox [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=1147887787.10470.58.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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