This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[wwwdocs] Shorten bugs/index.html a little


Just having pointed someone to our bug reporting instructions, I had
a look myself and noticed that they are a little unwieldy .  This is
a first step of shortening the text a little.

Help and contributions very welcome!

Gerald

Index: index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/bugs/index.html,v
retrieving revision 1.119
diff -u -r1.119 index.html
--- index.html	19 Mar 2017 07:50:55 -0000	1.119
+++ index.html	25 Nov 2017 19:00:10 -0000
@@ -38,9 +38,8 @@
 
 <h1><a name="report">Reporting Bugs</a></h1>
 
-<p>The main purpose of a bug report is to enable us to fix the bug. The
-most important prerequisite for this is that the report must be complete
-and self-contained.</p>
+<p>A good bug report, which is complete and self-contained, enables us
+to fix the bug.</p>
 
 <p>Before you report a bug, please check the 
 <a href="#known">list of well-known bugs</a> and, <strong>if possible,
@@ -56,13 +55,12 @@
 
 <h2>Summarized bug reporting instructions</h2>
 
-<p>After this summary, you'll find detailed bug reporting
-instructions, that explain how to obtain some of the information
-requested in this summary.</p>
+<p>After this summary, you'll find detailed instructions that explain
+how to obtain some of the information requested in this summary.</p>
 
 <h3><a name="need">What we need</a></h3>
 
-<p>Please include in your bug report all of the following items, the first
+<p>Please include all of the following items, the first
 three of which can be obtained from the output of <code>gcc -v</code>:</p>
 
 <ul>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]