Rename example job files (*.job -> *.fio)

[fio.git] / REPORTING-BUGS

diff --git a/REPORTING-BUGS b/REPORTING-BUGS
index ded68ab4fea9de3cfbc54385ad54b25cf7a30f2c..d8876ae6870f691f0e5a777b398d71b19203937e 100644 (file)
--- a/REPORTING-BUGS
+++ b/REPORTING-BUGS
@@ -2,15 +2,20 @@ Reporting a bug
 ---------------
 
 If you notice anything that seems like a fio bug, please do send email
-to the list (fio@vger.kernel.org, see README) about it. You'll need
-to report at least:
+to the list (fio@vger.kernel.org, see README) about it. If you are not
+running the newest release of fio, upgrading first is recommended.
+
+When reporting a bug, you'll need to include:
 
 1) A description of what you think the bug is
 2) Environment (Linux distro version, kernel version). This is mostly
    needed if it's a build bug.
-3) The fio version. The most useful is the git top level commit, you
-   can find out by doing a cat .git/HEAD from the top level fio directory.
+3) The output from fio --version.
 4) How to reproduce. Please include a full list of the parameters
    passed to fio and the job file used (if any).
 
+A bug report can never have too much information. Any time information
+is left out and has to be asked for, it'll add to the turn-around time
+of getting to the bottom of it and committing a fix.
+
 That's it!