lkml.org 
[lkml]   [2000]   [Jul]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH] 2.4.0-test3-pre6 REPORTING-BUGS cleanup continued
Date
Paul <set@pobox.com> noticed an error in REPORTING-BUGS that I didn't.
Namely, the word "to" is missing from "Send the output to the maintainer...."
This patch, which is relative to my previous cleanup patch, fixes that.
-Barry K. Nathan <barryn@pobox.com>

--- linux-2.4.0test3pre6bkn-old1/REPORTING-BUGS Sat Jul 8 22:49:01 2000
+++ linux-2.4.0test3pre6bkn/REPORTING-BUGS Sun Jul 9 00:36:07 2000
@@ -9,12 +9,12 @@
This explains what you should do with the "Oops" information to make it
useful to the recipient.

-Send the output 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.
+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.

If you are totally stumped as to whom to send the report, send it to
linux-kernel@vger.rutgers.edu. (For more information on the linux-kernel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:57    [from the cache]
©2003-2011 Jasper Spaans. Advertise on this site