summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSarah Sharp <sarah.a.sharp@linux.intel.com>2013-04-14 05:25:13 +0400
committerSarah Sharp <sarah.a.sharp@linux.intel.com>2013-04-19 03:55:08 +0400
commitbf6adaf50131cee0be3307cc65f97b43c5a65717 (patch)
tree102b0e3778fa041a465fb84be6371f250671cf02
parentbc6bed481ff3fbe2050f4290f59d27fad30b62a7 (diff)
downloadlinux-bf6adaf50131cee0be3307cc65f97b43c5a65717.tar.xz
Docs: Add a tips section to REPORTING-BUGS.
Lots of grumpy maintainers would love to have annoying newbies and disorganized bug reporters read Eric S. Raymond's "How To Ask Questions The Smart Way". Simon Tatham's "How to Report Bugs Effectively" is also relevant. It's likely no one will bother to read these, but it does give maintainers something to point to. Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
-rw-r--r--REPORTING-BUGS13
1 files changed, 13 insertions, 0 deletions
diff --git a/REPORTING-BUGS b/REPORTING-BUGS
index 327b33b43d63..d397e9181b97 100644
--- a/REPORTING-BUGS
+++ b/REPORTING-BUGS
@@ -64,6 +64,19 @@ information on the linux-kernel mailing list see
http://www.tux.org/lkml/).
+Tips for reporting bugs
+-----------------------
+
+If you haven't reported a bug before, please read:
+
+http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
+http://www.catb.org/esr/faqs/smart-questions.html
+
+It's REALLY important to report bugs that seem unrelated as separate email
+threads or separate bugzilla entries. If you report several unrelated
+bugs at once, it's difficult for maintainers to tease apart the relevant
+data.
+
[Some of this is taken from Frohwalt Egerer's original linux-kernel FAQ]
Gather information