-- Logs using @c debug_level 3 (e.g. add '-d 3' to the command line)
-- If this is a regression, include logs for working and broken version
-- If this is a regression, please find out the precise version that
- caused the regression. This can be done via a binary search; For
- example: if testing version 550 works but 600 fail, then try 575, etc.
+- Logs using <code>debug_level 3</code> (or with '-d 3' on the command line)
+- If the report is for a regression:
+ - Include logs for both working and broken versions.
+ - Find the precise version that caused the regression by binary search.
+ You can use "git bisect" to expedite this binary search:
+ http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
+
+If possible, please develop and attach a patch that helps to expose or
+solve the reported problem. See the HACKING file for information
+about that process.
+
+Attach all files directly to your posting. The mailing list knows to
+transform attachments to links, but attachments must be less than 300KB
+in total.