Not delivering {bugs,gnats,faq}.html in releases

[Wolfgang Bangerth]

> > gnats.html if dysfunctional anyway, so there shouldn't be any opposition
> > if I delete it and references to it soonish. The question is: do we want
> > to put
>
> Following, of course, the previous context of the discussion
> <http://gcc.gnu.org/ml/gcc/2003-06/msg01632.html> on how to do this, which
> you forgot to mention in your message.  I.e., include corresponding
> documentation extracted from Bugzilla.

Hm, do you mean that we have to distribute a list of bugzilla 
categories/keywords/... and their meanings with releases? I don't see any 
value in this, since you can only do something with this information if you 
are online. The only exception is the gccbug script, but I will certainly 
refuse to go through hoops generating this information just for the sake of 
gccbug.

Can you please clarify this?

> > Regarding bugs/faq.html: The only advertised method for bug submission is
>
> faq.html is not included as bug reporting documentation - it is included
> as the FAQ - and it is not "bugs/faq.html".  The files included are
> explicitly for the convenience of offline use, in that they refer to where
> the current version may be found, if online.

That should have read {bugs,faq}.html.

If you see any value in keeping these files in releases, that's fine with me. 
Let's keep in then.

Thanks
  W.

-------------------------------------------------------------------------
Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                               www: http://www.ices.utexas.edu/~bangerth/