2006-05-16 15:50:50

by Alan

[permalink] [raw]
Subject: PATCH: Clarify maintainers and include linux-security info

Signed-off-by: Alan Cox <[email protected]>

--- 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: [email protected], especially if the maintainer
+ does not respond.
+
+8. Happy hacking.

-----------------------------------



2006-05-16 16:01:25

by Randy Dunlap

[permalink] [raw]
Subject: Re: PATCH: Clarify maintainers and include linux-security info

On Tue, 16 May 2006 17:03:41 +0100 Alan Cox wrote:

> Signed-off-by: Alan Cox <[email protected]>
>
> --- 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: [email protected], especially if the maintainer
> + does not respond.

It's just [email protected] according to MAINTAINERS.

> +8. Happy hacking.



---
~Randy

2006-05-16 16:01:25

by Andrew Morton

[permalink] [raw]
Subject: Re: PATCH: Clarify maintainers and include linux-security info

Alan Cox <[email protected]> wrote:
>
> -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].

2006-05-16 22:40:21

by Alan

[permalink] [raw]
Subject: Re: PATCH: Clarify maintainers and include linux-security info

On Maw, 2006-05-16 at 08:57 -0700, Andrew Morton wrote:
> Alan Cox <[email protected]> wrote:
> >
> > -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.

2006-05-17 17:30:12

by Alan

[permalink] [raw]
Subject: 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.


Signed-off-by: Alan Cox <[email protected]) (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: [email protected], especially if the maintainer
+ please Cc: [email protected], 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: [email protected], especially if the maintainer
+ does not respond.
+
+8. Happy hacking.

-----------------------------------