This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Documentation: Bugs
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Subject: Re: Documentation: Bugs
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 28 Jul 1999 16:09:17 -0600
- cc: Jonas Rathert <jrt at gmx dot de>, gcc at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <Pine.GSO.4.10.9907282203010.25793-100000@markab.dbai.tuwien.ac.at
>you write:
> > I'd suggest to create a subdirectory bugs/ which contains files
> > egcs-1.1.html, egcs-1.2.html and gcc-2.95.html.
>
> If we go that road, we should re-use the current directory structure
> with egcs-1.0, egcs-1.1 and gcc-2.95.
I do not recommend we go this route.
Jason Molenda basically has gnats/prms ready to go, if we're going to have
bug lists and such, we should get them out of the reported bugs database
instead of creating lots of static html pages. This is especially true for
older releases that we have end of life'd.
> I think we should not care too much about old versions of GCC, where
> currently old means GCC 2.8.x and EGCS 1.0.x and I am not sure how
> maintainable separate bug lists will be.
Exactly. It's hard enough to keep a bugs database for the current release,
keeping them for older releases, while useful, wouldn't be the best use of
people's time.
> How about having a list with frequently encountered bugs in the current
> (GCC 2.95.x) and previous (EGCS 1.1.x) releases together with detailed
> information which release suffers from which bug and information when
> resp. whether a bug has been fixed?
This is much more plausible.
jeff