From: "Eli Zaretskii" <eliz@elta.co.il>
To: Andrew Cagney <cagney@gnu.org>
Cc: mec.gnu@mindspring.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Thu, 18 Mar 2004 16:52:00 -0000 [thread overview]
Message-ID: <6654-Thu18Mar2004185016+0200-eliz@elta.co.il> (raw)
In-Reply-To: <4059C8A6.1020504@gnu.org> (message from Andrew Cagney on Thu, 18 Mar 2004 11:04:54 -0500)
> Date: Thu, 18 Mar 2004 11:04:54 -0500
> From: Andrew Cagney <cagney@gnu.org>
>
> Er, we already have a repostory of known bugs, it's called the bug
> database. Why duplicate the content and tracking effort?
As Michael points out, and I concur, many, if not most, bugs stored
in the bug database are of no interest to users. They also don't
tell how to work around them. This is IMHO valuable information for
any GDB user who bumps into a bug.
In addition, PROBLEMS is much more accessible than the bug database,
as it is on the user's local disk.
> PROBLEMS should draw the users attention to late breaking and immediate
> issues that will hurt them (gdb doesn't build, this broke going from the
> previous release). A bug already present in the previous release
> _isn't_ new news.
You assume that GDB users download and build every release. This
isn't necessarily so: what about someone who is upgrading from
version 5.1.1 to v6.0?
> Listing every single long standing nit in the PROBLEMS file just adds
> unnecessary noise.
I don't agree that it's noise. If we put there only important
user-visible bugs, I think the signal to noise ratio would be high
enough to make the file useful.
WARNING: multiple messages have this Message-ID
From: "Eli Zaretskii" <eliz@elta.co.il>
To: Andrew Cagney <cagney@gnu.org>
Cc: mec.gnu@mindspring.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <6654-Thu18Mar2004185016+0200-eliz@elta.co.il> (raw)
Message-ID: <20040319000900.SjIB1brxsxIZbtA1pAfUmJYXaHWu0VbwNkw6ohv5UoQ@z> (raw)
In-Reply-To: <4059C8A6.1020504@gnu.org> (message from Andrew Cagney on Thu, 18 Mar 2004 11:04:54 -0500)
> Date: Thu, 18 Mar 2004 11:04:54 -0500
> From: Andrew Cagney <cagney@gnu.org>
>
> Er, we already have a repostory of known bugs, it's called the bug
> database. Why duplicate the content and tracking effort?
As Michael points out, and I concur, many, if not most, bugs stored
in the bug database are of no interest to users. They also don't
tell how to work around them. This is IMHO valuable information for
any GDB user who bumps into a bug.
In addition, PROBLEMS is much more accessible than the bug database,
as it is on the user's local disk.
> PROBLEMS should draw the users attention to late breaking and immediate
> issues that will hurt them (gdb doesn't build, this broke going from the
> previous release). A bug already present in the previous release
> _isn't_ new news.
You assume that GDB users download and build every release. This
isn't necessarily so: what about someone who is upgrading from
version 5.1.1 to v6.0?
> Listing every single long standing nit in the PROBLEMS file just adds
> unnecessary noise.
I don't agree that it's noise. If we put there only important
user-visible bugs, I think the signal to noise ratio would be high
enough to make the file useful.
next prev parent reply other threads:[~2004-03-18 16:52 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 22:54 Michael Elizabeth Chastain
2004-03-17 23:39 ` Andrew Cagney
2004-03-18 6:16 ` Eli Zaretskii
2004-03-18 16:05 ` Andrew Cagney
2004-03-18 16:52 ` Eli Zaretskii [this message]
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Eli Zaretskii
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Michael Elizabeth Chastain
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 19:30 ` Michael Elizabeth Chastain
2004-03-17 19:48 ` David Carlton
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 6:06 ` Eli Zaretskii
2004-03-19 0:09 ` David Carlton
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 20:15 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-18 16:23 ` Michael Elizabeth Chastain
2004-03-19 0:09 ` David Carlton
2004-03-18 16:45 ` David Carlton
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:27 ` Daniel Jacobowitz
2004-03-19 14:56 ` Eli Zaretskii
2004-03-19 15:03 ` Andrew Cagney
2004-03-19 15:33 ` Eli Zaretskii
2004-03-19 15:54 ` Andrew Cagney
2004-03-20 15:38 ` Eli Zaretskii
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 6:58 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 19:21 ` Michael Elizabeth Chastain
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-17 18:21 ` Michael Elizabeth Chastain
2004-03-17 22:11 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-17 18:55 Michael Elizabeth Chastain
2004-03-17 19:03 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-17 19:16 ` David Carlton
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-17 1:53 Michael Elizabeth Chastain
2004-03-17 16:13 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
2004-03-17 17:05 ` David Carlton
2004-03-19 0:09 ` David Carlton
2004-03-19 0:09 ` Eli Zaretskii
2004-03-17 6:16 ` Eli Zaretskii
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-19 0:09 ` David Carlton
2004-03-17 17:19 ` David Carlton
2004-03-19 0:09 ` Eli Zaretskii
2004-03-17 19:07 ` Eli Zaretskii
2004-03-19 0:09 ` David Carlton
2004-03-17 19:18 ` David Carlton
2004-03-19 0:09 ` Andrew Cagney
2004-03-17 22:11 ` Andrew Cagney
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 6:11 ` Eli Zaretskii
2004-03-18 16:36 ` Daniel Jacobowitz
2004-03-19 0:09 ` Eli Zaretskii
2004-03-18 16:55 ` Eli Zaretskii
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:25 ` Daniel Jacobowitz
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=6654-Thu18Mar2004185016+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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