This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Not delivering {bugs,gnats,faq}.html in releases
On Thu, 26 Jun 2003, Joseph S. Myers wrote:
>> Can you please clarify this?
> The point of this is providing documentation for gccbug, by way of "lynx
> -source http://gcc.gnu.org/bugzilla/describecomponents.cgi"; in the release
> script.
I had a look, and transforming this into something that is really suitable
for someone without web access (there is a lot of "useless" stuff there)
is far from straightforward, so despite what I wrote earlier I think we
should...
> (The rest of gnats.html - other than the list of categories -
> does have some use as documentation for gccbug, as describing the fields
> before the GNATS-to-Bugzilla converter handles them; perhaps the rest
> should just be in the gcc rather than wwwdocs CVS as gccbug documentation,
> but we wanted to avoid duplicate documentation of the categories.
> Incidentally, in general the descriptions of categories in gnats.html are
> better-written documentation than those in Bugzilla and should be merged
> into those in Bugzilla.
(a) merge these better descriptions from gnats.html into Bugzilla,
(b) add a note to the online resources concerning components (and we
are only taking about components here AFAICS, which are mostly
self-explanatory anyways) to gccbug, and
(c) remove gnats.html.
This is pragmatic and considers that our volunteer time is finite, and
the more we spend on this, the less can we spend on other issues, and iff
after GCC 3.3.x or GCC 3.4 some user appears which reports this lack of
offline bug reporting documentation wrt. components as a problem, I hereby
volunteer to do whatever is necessary to provide it again.
> Removing documentation previously present in releases of how to use part
> of those releases would certainly be a regression.
Aren't we talking only about the documentation of (Bugzilla) components
here?
Gerald