Re: gdb/PROBLEMS ?

[Stan Shebs <stan at codesourcery dot com>]

Eli Zaretskii wrote:
> > Date: Sun, 02 May 2010 18:38:01 -0700
> > From: Stan Shebs <stan@codesourcery.com>
> > CC: gdb-patches@sourceware.org
> >
> > Pedro Alves wrote:
> >     
> > > I looked over the described problems in gdb/PROBLEMS, and, it looks
> > > to me that all of them fall in one of two categories: either
> > > they've been fixed already, or aren't worth mentioning here.
> > > Anyone wants to double check, or believes otherwise?  I'll
> > > be happy to adjust the patch.
> > >   
> > >       
> > I'd say to just toss the file entirely, and remove mentions of it in the 
> > documentation.  It's really just a relic of pre-web days; I'd be 
> > astonished if there were any users who would think to look at it instead 
> > of going to our website.
> >     
>
> Are you saying that no one ever works off-line these days?
>
>   

Not at all, in fact I bet I do it more than most people.  But we haven't 
been maintaining an up-to-date self-contained synopsis of open bugs, and 
as far as I know nobody is complaining that they were working offline 
the other day, and couldn't wait until getting back online to find out 
what bugs were open.

If a bug were so serious that we needed to be sure that everyone knew 
about it, even if they were using GDB while backpacking through upper 
Amazonia, then I would think we'd want it at the top of gdb/NEWS, with 
extra markup to ensure that it would be blinking red in most file 
readers. :-)

Another way to look at it is that both NEWS and PROBLEMS are chapters of 
the release note, and it's generally simpler for users if all release 
note info is in a single place.

Stan