|author||J. Bruce Fields <firstname.lastname@example.org>||2008-02-07 00:13:40 -0800|
|committer||Linus Torvalds <email@example.com>||2008-02-07 08:42:17 -0800|
REPORTING-BUGS: cc the mailing list too
People should also cc relevant mailing lists when reporting bugs. Signed-off-by: J. Bruce Fields <firstname.lastname@example.org> Acked-by: Randy Dunlap <email@example.com> Signed-off-by: Andrew Morton <firstname.lastname@example.org> Signed-off-by: Linus Torvalds <email@example.com>
Diffstat (limited to 'REPORTING-BUGS')
1 files changed, 6 insertions, 5 deletions
diff --git a/REPORTING-BUGS b/REPORTING-BUGS
index ac02e42a262..ab0c56630a8 100644
@@ -10,11 +10,12 @@ bug report. This explains what you should do with the "Oops" information
to make it useful to the recipient.
Send the output to the maintainer of the kernel area that seems to
-be involved with the problem. Don't worry too much about getting the
-wrong person. If you are unsure send it to the person responsible for the
-code relevant to what you were doing. If it occurs repeatably try and
-describe how to recreate it. That is worth even more than the oops itself.
-The list of maintainers is in the MAINTAINERS file in this directory.
+be involved with the problem, and cc the relevant mailing list. Don't
+worry too much about getting the wrong person. If you are unsure send it
+to the person responsible for the code relevant to what you were doing.
+If it occurs repeatably try and describe how to recreate it. That is
+worth even more than the oops itself. The list of maintainers and
+mailing lists is in the MAINTAINERS file in this directory.
If it is a security bug, please copy the Security Contact listed
in the MAINTAINERS file. They can help coordinate bugfix and disclosure.