Add discussion of checking if issue has already been reported.

README.md

@@ -20,7 +20,9 @@ i'm not an Emacs dev myself, but i do follow the bug-gnu-emacs list, and have do
 
     * For those running a development version of Emacs, make sure you're at the latest commit on `master`, then run `make bootstrap`, which removes all existing compiled files and forces a new bootstrap from a clean slate.
 
-Still experiencing the issue even in the most recent release, or at the most recent commit? Now's the time to report it via `report-emacs-bug`:
+Still experiencing the issue even in the most recent release, or at the most recent commit? Check whether the issue has already been reported, either by visiting [the GNU Emacs bug tracker on the Web](https://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs;max-bugs=100;base-order=1;bug-rev=1), or by installing [the `debbugs` package from GNU ELPA](http://elpa.gnu.org/packages/debbugs.html) and searching for existing issues via its Emacs interface. If the issue has already been reported, consider adding to that report any details not already described.
+
+Assuming there's no existing report of the issue on the bug tracker, you can now `report-emacs-bug`:
 
 * Regardless of where you send the report, it should include the following information: