Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 06:16:00 -0000	[thread overview]
Message-ID: <ullly7k5v.fsf@elta.co.il> (raw)
In-Reply-To: <4058E1C6.70605@gnu.org> (message from Andrew Cagney on Wed, 17 Mar 2004 18:39:50 -0500)

> Date: Wed, 17 Mar 2004 18:39:50 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> NEWS contains a history of GDB, PROBLEMS does not.
> 
> PROBLEMS is there to identify late breaking screwups and other issues in 
> just _this_ release.

Not necessarily.  It depends on what purpose we want PROBLEMS to
serve.

One way of looking at PROBLEMS is as a repository of bugs that the GDB
team already knows about, and that users therefore should not report
as new bugs.  PROBLEMS can also mention work-arounds, so that users
who bump into them can do whatever they need even though the bug isn't
fixed yet.

If viewed like that, it would make sense for PROBLEMS to include all
the bugs that are still not fixed, even if they date back to version
0.0.  Bugs that are solved should indeed be deleted from PROBLEMS.

(Btw, if GDB still has bugs known since v0.0, it would say something
quite unflattering about GDB maintenance, and that alone is IMHO a
reason good enough to keep old unsolved bugs on record.)


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: <ullly7k5v.fsf@elta.co.il> (raw)
Message-ID: <20040319000900.INd-uyaHxe6krNzmDClG2pA5FJG8gDAraEn-SBz17Ug@z> (raw)
In-Reply-To: <4058E1C6.70605@gnu.org> (message from Andrew Cagney on Wed, 17 Mar 2004 18:39:50 -0500)

> Date: Wed, 17 Mar 2004 18:39:50 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> NEWS contains a history of GDB, PROBLEMS does not.
> 
> PROBLEMS is there to identify late breaking screwups and other issues in 
> just _this_ release.

Not necessarily.  It depends on what purpose we want PROBLEMS to
serve.

One way of looking at PROBLEMS is as a repository of bugs that the GDB
team already knows about, and that users therefore should not report
as new bugs.  PROBLEMS can also mention work-arounds, so that users
who bump into them can do whatever they need even though the bug isn't
fixed yet.

If viewed like that, it would make sense for PROBLEMS to include all
the bugs that are still not fixed, even if they date back to version
0.0.  Bugs that are solved should indeed be deleted from PROBLEMS.

(Btw, if GDB still has bugs known since v0.0, it would say something
quite unflattering about GDB maintenance, and that alone is IMHO a
reason good enough to keep old unsolved bugs on record.)


  reply	other threads:[~2004-03-18  6:16 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 [this message]
2004-03-18 16:05     ` Andrew Cagney
2004-03-18 16:52       ` Eli Zaretskii
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: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-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 ` 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 ` David Carlton
2004-03-18 16:45   ` David Carlton
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17  6:58 ` Michael Elizabeth Chastain
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 ` 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
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-19  0:09 ` Eli Zaretskii
2004-03-17  6:16   ` Eli Zaretskii

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=ullly7k5v.fsf@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