Update the contributing guide

This wording made it seem as if bug reports had to be in the form of
patches too. While this is ideal not everyone reporting a bug will
necessarily have a patch to fix it.

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 13e5e8735c2612bef847388787b5f7fb80052d13..18987c3b14968d1259c7b555c968af6261dfa97c 100644 (file)
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -5,11 +5,11 @@ Basic Information
 -----------------
 
 To report a bug or submit changes to this repository please send a
 -----------------
 
 To report a bug or submit changes to this repository please send a

-patch to the GNU Linux-libre mailing list:
+message to the GNU Linux-libre mailing list:

 <https://www.fsfla.org/cgi-bin/mailman/listinfo/linux-libre>
 
 -   Changes should be in the form of a patch generated by
 <https://www.fsfla.org/cgi-bin/mailman/listinfo/linux-libre>
 
 -   Changes should be in the form of a patch generated by

-    `git format-patch`. Email those to the mailing list for review.
+    `git format-patch`.

 
 -   A patch should address one, and only one, concern. For example, a
     bug fix.
 
 -   A patch should address one, and only one, concern. For example, a
     bug fix.