From: Stan Shebs <stan@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stan Shebs <stan@codesourcery.com>,
pedro@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: gdb/PROBLEMS ?
Date: Mon, 03 May 2010 03:55:00 -0000 [thread overview]
Message-ID: <4BDE492E.1020004@codesourcery.com> (raw)
In-Reply-To: <83pr1dvfzi.fsf@gnu.org>
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
next prev parent reply other threads:[~2010-05-03 3:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 16:26 Pedro Alves
2010-05-02 17:05 ` Joel Brobecker
2010-05-02 17:38 ` Eli Zaretskii
2010-05-03 1:38 ` Stan Shebs
2010-05-03 3:09 ` Eli Zaretskii
2010-05-03 3:55 ` Stan Shebs [this message]
2010-07-29 15:00 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BDE492E.1020004@codesourcery.com \
--to=stan@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).