PATCH: Clarify maintainers and include linux-security info
MAINTAINERS renamed from MAINTAINERS~ +5 -1
@@ -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: [email protected], especially if the maintainer + does not respond. + +8. Happy hacking. -----------------------------------
Quoted 5 lines · Alan Cox
-7. Happy hacking.
+7. When sending security related changes or reports to a maintainer
+ please Cc: [email protected], especially if the maintainer
+ does not respond.
Does that address work? People have been using [email protected].
Quoted 8 lines · Andrew Morton
Quoted 5 lines · Alan Cox
-7. Happy hacking.
+7. When sending security related changes or reports to a maintainer
+ please Cc: [email protected], especially if the maintainer
+ does not respond.Does that address work? People have been using [email protected].
No I pasted the wrong thing while making it. I'll send a corrected one tomorrow.
MAINTAINERS line 49
Quoted 12 lines · On Tue, 16 May 2006 17:03:41 +0100 Alan Cox wrote:
Signed-off-by Alan Cox <[email protected]>MAINTAINERS renamed from MAINTAINERS~ +3
-1@@ -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: [email protected], especially if the maintainer + does not respond.
It's just [email protected] according to MAINTAINERS.
MAINTAINERS line 51
Quoted 1 line
MAINTAINERS renamed from MAINTAINERS~ +1
-0+8. Happy hacking.
---
~Randy
PATCH: Clarify maintainers and include security info (Version 2)
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.
MAINTAINERS renamed from MAINTAINERS~ +6 -1
@@ -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: [email protected], especially if the maintainer + please Cc: [email protected], especially if the maintainer does not respond. 8. Happy hacking.
or alternatively:
MAINTAINERS +10 -1
@@ -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: [email protected], especially if the maintainer + does not respond. + +8. Happy hacking. -----------------------------------