[PATCH] wwwdocs: Clarify meaning of "not issued by" in bugs web page

[Jonathan Wakely]

Should we make this change?

Firstly, these bullet points are full sentences and so should end with
a period (or smiley, in some cases).

Secondly, releases are not issued by the GNU Project at all, they're
issued by the GCC release managers.

Finally, "releases or snapshots of GCC not issued by ..." has confused
at least one bug reporter, and I think saying "unofficial releases or
snapshots" makes it slightly clearer. Comparatively few users actually
use a self-built GCC based on official source tarballs, but that's OK.
Distro builds tend to be much closer to upstream these days, and we
rarely reject bug reports where the reporter is using a build from
Fedora, Ubuntu, Arch or whatever (unless it really is caused by a
downstream patch and doesn't reproduce with a gcc.gnu.org release).

OK for wwwdocs?


-------------- next part --------------
commit b7bf1f0b9f708673feeb13fcdbc1d461b82ad6d6
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Jul 27 16:08:10 2021 +0100

    Clarify meaning of "not issued by" in bugs web page

diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index 80dac392..5143350a 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -102,11 +102,11 @@ three of which can be obtained from the output of <code>gcc -v</code>:</p>
   <li>An error that occurs only some of the times a certain file is
   compiled, such that retrying a sufficient number of times results in
   a successful compilation; this is a symptom of a hardware problem,
-  not of a compiler bug (sorry)</li>
+  not of a compiler bug (sorry).</li>
 
   <li>Assembly files (<code>*.s</code>) produced by the compiler, or any
   binary files, such as object files, executables, core files, or
-  precompiled header files</li>
+  precompiled header files.</li>
 
   <li>Duplicate bug reports, or reports of bugs already fixed in the
   development tree, especially those that have already been reported
@@ -114,14 +114,14 @@ three of which can be obtained from the output of <code>gcc -v</code>:</p>
 
   <li>Bugs in the assembler, the linker or the C library.  These are
   separate projects, with separate mailing lists and different bug
-  reporting procedures</li>
+  reporting procedures.</li>
 
-  <li>Bugs in releases or snapshots of GCC not issued by the GNU
-  Project.  Report them to whoever provided you with the release</li>
+  <li>Bugs in unofficial releases or snapshots of GCC not issued by
+  the GCC project.  Report them to whoever provided you with the release.</li>
 
   <li>Questions about the correctness or the expected behavior of
   certain constructs that are not GCC extensions.  Ask them in forums
-  dedicated to the discussion of the programming language</li>
+  dedicated to the discussion of the programming language.</li>
 </ul>
 
 <h3 id="where">Where to post it</h3>